Topic: Wanted: Reliable smtp server to use for smeserver email sending

[brianr]

Hi

I am unable to get a fixed IP address, so I have to use a 3rd party smtp server to send email. I am finding that my ISP email server is not very
well looked after and for certain email addresses it is rejected by the receiving server.

Anyone got any suggestions as to who I could use?  I was considering trying to use the gmail server (i have a gmail account as well). 

All suggestions gratefully received.

[NoTo]

I had the same a couple of years ago. I signed-up a Gmail account and now relay through that. We use the gmail email address as a 'disposable' one for web sign-ins for random things that you use only once or twice, and provides a useful 'off-site' email address to use for testing that mail is working etc.

[brianr]

I had the same a couple of years ago. I signed-up a Gmail account and now relay through that. We use the gmail email address as a 'disposable' one for web sign-ins for random things that you use only once or twice, and provides a useful 'off-site' email address to use for testing that mail is working etc.

aha -  that sounds like a good idea.  Do you manage to access gmail on port 465?  If so, how?

[NoTo]

Ah, you have highlighted a future problem for me. I've not rolled-out SME8 as a mailserver yet, we're still using the old system at the moment. I'm probably going to be int he same boat as you in the new year 

[chris burnat]

Moved to General Discussions.

[CharlieBrady]

Do you manage to access gmail on port 465?  If so, how?

If you have a problem accessing gmail on port 465, then you should open a bug report/NFR.

[brianr]

If you have a problem accessing gmail on port 465, then you should open a bug report/NFR.

Is there a way of specifying port 465 to be used? - Should specifying

smtp.googlemail.com:465

in the "Address of Internet provider's mail server" work? It needs SSL/TLS apparently.

[wellsi]

I have been using authsmtp http://www.authsmtp.com/ for the last few years, seems to work well.

Although they appear to have an auth problem with Digest-MD5 but that is easily configured.

[brianr]

I have been using authsmtp http://www.authsmtp.com/ for the last few years, seems to work well.

Although they appear to have an auth problem with Digest-MD5 but that is easily configured.

I've got a trial account - but it does not work out of the box (just dropping the URL of the mail server and name and password into the Server-Manager/Email/Email Delivery boxes).

Can you give me some more details of the changes you needed?

[brianr]

Tried using the gmail SMTP server: smtp@googlemail.com.

It works if you add the Port 465 to the db:

config setprop smtp-auth-proxy PeerPort 465

However all email are sent "from" the gmail user that you use to login to the server.  So not a lot of use.

I'll write this up for the wiki once I've finished this little investigation.

[stephdl]

Tried using the gmail SMTP server: smtp@googlemail.com.

It works if you add the Port 465 to the db:

config setprop smtp-auth-proxy PeerPort 465

However all email are sent "from" the gmail user that you use to login to the server.  So not a lot of use.

I'll write this up for the wiki once I've finished this little investigation.

are you sure that you need to change the port in the db, it seems to me that you can do by telling which port you need
smtp.gmail.com:465
but indeed the mail is sent with the name of the gmail account

[brianr]

My interpretation of

/usr/local/sbin/smtp-auth-proxy.pl

is that SSL is only turned on if PeerPort=465, so appending 465 to the URL will not make that happen. Which I guess is why when I tried it it would not send (but no errors where logged).

My Perl is pretty basic, so I could be wrong though.

[wellsi]

I've got a trial account - but it does not work out of the box (just dropping the URL of the mail server and name and password into the Server-Manager/Email/Email Delivery boxes).

Can you give me some more details of the changes you needed?

Here is my SME 9 test server setup - I'm debugging Bug 8060 at the moment and needed to set it up there.

Until Bug 8060 is released you need this line
config setprop smtp-auth-proxy Blacklist DIGEST-MD5

Here is my setup (not sure why I have the IP address and not the name, but it works)

Address of Internet provider's mail server  62.13.128.189
SMTP Authentication for Internet provider   Enabled
Mail server user id                         username-from-authsmtp
Mail server password                        password-from-authsmtp

And if you check from the shell

smtp-auth-proxy=service
    Blacklist=DIGEST-MD5
    Debug=enabled <-- not needed
    Passwd=password-from-authsmtp
    Userid=username-from-authsmtp
    status=enabled

[wellsi]

My interpretation of

/usr/local/sbin/smtp-auth-proxy.pl

is that SSL is only turned on if PeerPort=465, so appending 465 to the URL will not make that happen. Which I guess is why when I tried it it would not send (but no errors where logged).

My Perl is pretty basic, so I could be wrong though.

In SME9 I get SSL to authsmtp by default without any peerport setting

[brianr]

Until Bug 8060 is released you need this line
config setprop smtp-auth-proxy Blacklist DIGEST-MD5

Yes, that works - thanks.

[brianr]

In SME9 I get SSL to authsmtp by default without any peerport setting

Yes, same here, I guess setting port 465 forces SSL, but it is taken if offered anyway.