Glad to hear you got it working.  :-)  Not sure why the port change was necessary - must have something to do with your service provider.

Thanks for letting me know,

Toby

+x

 

LogViewPlus Support - 24 Jul 2020

>> Hi
In fact we try all options (like shown below)
SSL checked
smtp.gmail.com
WITH ports 465 - error - then email was sent - but no mail
but.. hurray - now with 587 port it works !

sage?

The error message means the mail was not sent.

What settings are you using to connect to SendGrid?  What is the error message?

Hi Toby
Hmm. One sec. We do have the 'amail have been sent' but we have the error before, so thats ok ?

Hi Micha,

When you test your SMTP connection you should get a message back saying "A test notification email has been sent."  There is currently a bug in LogViewPlus where an error message may be displayed before this message.  

If you see an error message - the message was NOT sent and we need to address the error message.  If you do NOT see an error message, then LogViewPlus successfully sent the message.  From there, it is your provider's responsibility to deliver it.  

We have fixed this bug for the next release.  In the next release, if an error message is shown then the "success" message will not be shown.

As to why your provider is not delivering messages, it is difficult to say.  What I do know is that sending email is surprisingly "fuzzy" these days.  Spam has become such a problem that a lot of services actively try to stop receiving email from free accounts.  It might be worth contracting SendGrid or subscribing to a paid account.

Hope that helps,

Toby

Hi Toby
This is very strange
we try as well
we got the same error mesage with sendgrid than we got with gmail.
port 25 figures as not SSL, but we try all options
25 with and without
465 with and without
587 with and without
noone works. some get another error message (directly, nit after a few seconds)

Hi Micha,

I have had a chance to do some testing with SendGrid.  I am using the configuration "smtp.sendgrid.net" on port 25 with TLS enabled.



Everything works as expected.  However, I did notice that when I send an email to Hotmail - the mail does not get through (even as junk).  Mails get through fine on the other accounts I tested (although Gmail did flag the email as potentially dangerous).

The issues with sending mail to these accounts is with the SMTP provider and not LogViewPlus.  The mail accounts have built in spam filters that make deliver-ability an issue.  The email recipient must trust the email sender.

Hope that helps,

Toby

Hi Again
we try with sendgrid, no success same error message (btw, after the error message there is another message to check your emaio, but there is no mail in)
did anyone use gmail/sendgrid/any other email service to send emails and can share which/settings ?

A few more ideas from Google which might help.  Please review:
https://myaccount.google.com/u/0/security-checkup/4
https://myaccount.google.com/lesssecureapps

In reviewing these settings, is there anything you believe might be blocking your connection?

Also, it appears that Gmail does not support insecure connections - so please ignore that suggestion I made above.

Second, it may be worth upgrading to the latest LogViewPlus BETA release v2.4.41 available here:
https://www.logviewplus.com/download.html

This release upgrades LogViewPlus to use .Net 4.7.2.  The current version is 4.5.2.  There are a lot of "behind the scenes" security enhancements in this release and it is possible that the upgrade may help.

Hope that helps,

Toby

Hi Micha,

Again - I believe the problems you are having are with your Gmail account settings.  For example, it could be due to the authentication method used or the age of the account.  Is there another provider you could try - for example SendGrid?  

The "Secure Connection with SSL" flag is used to set the "EnableSSL" field on the .Net SmtpClient.  The documentation for this property states that only SSL over TLS is supported.  Direct SSL connections are not supported.  I can see where this is confusing and I will rename this field "Secure Connection with TLS" in the next release.  Apologies for the confusion this has caused.

It may also be worth testing with an insecure connection.  This may help to narrow down any problems with your configuration.

Hope that helps,

Toby