V.24 not happy with SMTP port 587
Posted: 17 Jan 2018, 10:55
Hi All - New to this board, first post. I have checked for duplicate posts, but have found none. Apologies if this has already been covered.
We have just updated 50 Accounts Essentials from v.23 to v.24. Our SAGE invoices have always been e-mailed via our own remote Postfix mail server using SSL over port 587, without any problem. This facility was last used yesterday morning before the update to v.24.
With v.24, we are no longer able to do so, receiving a 'the server and client cannot find a compatible protocol...' or similar error message (please excuse the vagueness of this - I am away from base, and have only just discovered this forum whilst on site). To overcome it, we have to 'dumb down' and use port 25, which is not ideal.
Actually - and this has just occurred to me now I write - we didn't explore the individual report options, only the email defaults, although from memory I think that this is the only area from which the port is configurable. Under v.23, at least. I shall check this upon my return, although I shouldn't think that it will be different under v.24, so shall carry on with this post.
We initially installed over the existing v.23, just to gain some local knowledge of how seamlessly the process runs, being new to SAGE in April 2017. The email issue was noticed at this point.
We then uninstalled, removed all legacy files, settings, registry keys etc, rebooted and installed v.24 afresh, as was always our intention. This time we had to add the email defaults again, naturally, with the same behavior, again as you'd expect.
Has anybody else noticed this? If so, have you found the solution yet?
Standalone SAGE 50 Accounts Essentials v.24, on Windows 10 64-bit running Sophos Anti-virus software. Postfix/Ubuntu 16.04.
Thank you to anybody who takes the time to consider this.
We have just updated 50 Accounts Essentials from v.23 to v.24. Our SAGE invoices have always been e-mailed via our own remote Postfix mail server using SSL over port 587, without any problem. This facility was last used yesterday morning before the update to v.24.
With v.24, we are no longer able to do so, receiving a 'the server and client cannot find a compatible protocol...' or similar error message (please excuse the vagueness of this - I am away from base, and have only just discovered this forum whilst on site). To overcome it, we have to 'dumb down' and use port 25, which is not ideal.
Actually - and this has just occurred to me now I write - we didn't explore the individual report options, only the email defaults, although from memory I think that this is the only area from which the port is configurable. Under v.23, at least. I shall check this upon my return, although I shouldn't think that it will be different under v.24, so shall carry on with this post.
We initially installed over the existing v.23, just to gain some local knowledge of how seamlessly the process runs, being new to SAGE in April 2017. The email issue was noticed at this point.
We then uninstalled, removed all legacy files, settings, registry keys etc, rebooted and installed v.24 afresh, as was always our intention. This time we had to add the email defaults again, naturally, with the same behavior, again as you'd expect.
Has anybody else noticed this? If so, have you found the solution yet?
Standalone SAGE 50 Accounts Essentials v.24, on Windows 10 64-bit running Sophos Anti-virus software. Postfix/Ubuntu 16.04.
Thank you to anybody who takes the time to consider this.