cancel
Showing results for 
Search instead for 
Did you mean: 

Outgoing server (SMTP) settings for Thunderbird, post Greenby

FIXED
Riverside
Grafter
Posts: 35
Thanks: 9
Registered: ‎11-10-2018

Outgoing server (SMTP) settings for Thunderbird, post Greenby

Hi, and apologies if a solution is hiding in any of the previous topics, but I had no luck using search to nail down my scenario.

MAAF legacy e-mail address - which has been working OK with Greenby for incoming mail - except I have just found out that I can not send any outgoing mail. I have sent outgoing mail before and post migration with no issues or settings changes, but it's currently not working.

It was initially failing with a prompt to to check the server settings, which I have updated to SSL/TLS connection security, but now it just times out.

Could someone please let me know what server settings I should now use for this please? This might be temporary, but curious if anyone else has had the same issue.

Thanks in advance.

4 REPLIES 4
PhilipHeyes
Seasoned Pro
Posts: 818
Thanks: 287
Fixes: 11
Registered: ‎10-11-2021

Re: Outgoing server (SMTP) settings for Thunderbird, post Greenby

Fix

Server :    mail.madasafish.com has IP Addresses:  212.159.9.238   &    212.159.8.238

This is still hosted by Plusnet.   Greenby hosted servers have IPs like : 91.x.x.x

For all ISP SMTP servers the Ports and Security are very standard.

For SMTP without encryption use Port 587

For STARTTLS also Port 587

For SMTPS i.e. SSL/TLS use Port 465

I prefer to see the Username as the email address & not the <account>+<name> or similar.


Riverside
Grafter
Posts: 35
Thanks: 9
Registered: ‎11-10-2018

Re: Outgoing server (SMTP) settings for Thunderbird, post Greenby

Thanks PhilipHeyes - that has worked.

The port was originally set to 25 so i've switched that to 465 and added the full e-mail address as the user name as suggested.

Test check e-mail has now delivered and been received so fingers crossed those settings remain stable.

It's always a bit unsettling when settings unexpectedly go awry!

Appreciate the help 👍

pvmb
All Star
Posts: 1,650
Thanks: 328
Fixes: 13
Registered: ‎12-02-2014

Re: Outgoing server (SMTP) settings for Thunderbird, post Greenby

@Riverside 

"The port was originally set to 25..."

And it was working on port 25? 😯

"It's always a bit unsettling when settings unexpectedly go awry!"

When did it stop working on port 25? Assuming it did...

------------------------------------

Email Client Settings (NB - From Greenby, for a straight Plusnet email account)

Incoming Server Address - imap.plus.net
Protocol - IMAP
IMAP Port - 993 (Encryption Enabled)
Outgoing Server Address - relay.plus.net (Needs changing as appropriate)
SMTP Port - 465 (Encryption Enabled)

If you prefer to use the POP protocol rather than IMAP then please use port 995 with Encryption turned on
-------------------------------------

Configure Mail Client Using Manual Settings

https://serioussem.com/knowledgebase/configure-mail-client-using-manual-settings/

Riverside
Grafter
Posts: 35
Thanks: 9
Registered: ‎11-10-2018

Re: Outgoing server (SMTP) settings for Thunderbird, post Greenby

@pvmb 

The last e-mail I sent was on 20th May and that was a confirmed delivery so it's happened after that date
That was using port 25 and the 'shortened' user name (so no @...co) but with no connection security.
Before today, I had not changed any mail server settings since the migration, but off the back of searching this forum about the marked increase in spam mail since the switch to Greenby I had hits for 'unable to send e-mail...' so I decided to run a test and immediately came up against the outgoing mail server issue that @PhilipHeyes kindly helped with.

Thanks for the configuration link. I will save that for future reference in case this happens again.

I'm ok with configurations getting changed. IT is its own beast, but it's just a little frustrating that we don't seem to get a heads-up and guidance re a quick fix when things like this throw a spanner in the works. Given the environment, that is probably a big ask though. It may be something limited to a fraction of the users rather than a global issue, which makes Community support like this an invaluable resource.