[courier-users] 456 plus 502 errors

2008-04-30 Thread Mark Constable
I need help with this one, if I try to send an email to anyone at @bigpond.net.au I get these 2 errors below but if I telnet to their MX hosts port 25 directly then a test message will go through okay so it seems to only be a problem when I send via my local courier-mta. Apr 30 16:09:27 mail

Re: [courier-users] 456 plus 502 errors

2008-04-30 Thread Sam Varshavchik
Mark Constable writes: I need help with this one, if I try to send an email to anyone at @bigpond.net.au I get these 2 errors below but if I telnet to their MX hosts port 25 directly then a test message will go through okay so it seems to only be a problem when I send via my local courier-mta.

Re: [courier-users] 456 plus 502 errors

2008-04-30 Thread Mark Constable
On 2008-04-30 21:02, Sam Varshavchik wrote: Apr 30 16:09:27 mail courieresmtpd: error,relay=:::xx.240.81.28, from=[EMAIL PROTECTED],to=[EMAIL PROTECTED]: 456 Address temporarily unavailable. Apr 30 16:09:27 mail courieresmtpd: error, relay=:::xx.240.81.28,msg=502 ESMTP

Re: [courier-users] 456 plus 502 errors

2008-04-30 Thread Bernd Wurst
Hi. On Wednesday 30 April 2008, Mark Constable wrote: I need help with this one, if I try to send an email to anyone at @bigpond.net.au I get these 2 errors below but if I telnet to their MX hosts port 25 directly then a test message will go through okay so it seems to only be a problem when

Re: [courier-users] 456 plus 502 errors

2008-04-30 Thread Sam Varshavchik
Mark Constable writes: Ah right, thanks Sam. Now I know what the signature of backscatter suppression looks like in the log files. However, I'm still unsure of why I can't clear this user. I've tested that a direct SMTP connection works okay so I assume it should be okay to clear the

Re: [courier-users] 456 plus 502 errors

2008-04-30 Thread Malcolm Weir
-Original Message- From: Sam Varshavchik Sent: Wednesday, April 30, 2008 3:26 PM Mark Constable writes: Ah right, thanks Sam. Now I know what the signature of backscatter suppression looks like in the log files. However, I'm still unsure of why I can't clear this