On 05/08/14 11:19:41, Mark Rogers wrote:
On 5 August 2014 10:45, Barry Samuels bjsamuels@beenthere-donethat.org.uk wrote:
As far as I know spamfiltering.com is used only for incoming mail (it is United Hosting's spam trap (see reply to Laurie) and outgoing mail is not directed to that.
In both the error messages you posted, you had the text: "host mx1.spamfiltering.com[x.x.x.x] said:" ... where x.x.x.x was one of the two IP addresses that mx1.spamfiltering.com resolves to:
$ dig mx1.spamfiltering.com ...;; ANSWER SECTION: mx1.spamfiltering.com. 437 IN A 72.249.150.158 mx1.spamfiltering.com. 437 IN A 212.113.130.124
That doesn't mean it's being spam filtered on exit though, just that the server they're using for relaying has one of those addresses.
The whole of the Postfix directory was copied so I don't think that anything was left out.
It's been a while since I set up Postfix but let's say for example that the SASL configuration was broken because something wasn't properly installed. The configuration might be telling Postfix to use it, but if it's not there (or otherwise broken) it can't. It may well then be that Postfix drops back to a different option (much as it might if the "other end" didn't support SASL), and that different option is triggering the errors that you're not seeing on your other box. Ie same config, but different results.
I've checked sasl packages on both machines and the only difference is that there is libgsasl7 installed on the new machine but not on the old.
I did try re-doing postmap sasl_passwd but that made no difference.
I can't see any clues in /var/mail.log but then I don't know really what I'm looking for.
Best option is to send test emails from each box to the same recipient (one that fails) and compare the logs for the same event on both boxes. Anything that is different is likely a clue.
BTInternet are our ISP but our email does not go through them.
That does appear to be the case here, but it was more a note to be aware that BT doesn't always do what you think it does. It is quite possible that you (try to) make a connection to your mail server on port 25, and BT proxies (redirects) that connection to their own mail servers. You can test this using telnet: $telnet <my remote SMTP server> 25 .. and see what response you get; if it comes from BT then BT are silently redirecting your connection.
The response comes from my email server at United Hosting so no redirecting there.
But again just to stress this: nothing indicates that is happening here because the responses you are getting aren't coming from BT.
Mark
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) @ 13 Clarke Rd, Milton Keynes, MK1 1LG
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
As a matter of interest I have changed outgoing mail to use mail.btinternet.com and it all seems to work perfectly now.
That, to me, implies a problem with United Hosting's servers although it doesn't explain why it still works perfectly on my old machine. I am in touch with United Hosting about this but they haven't yet come up with anything useful.