5 messages in net.sourceforge.lists.courier-users[courier-users] Dialback in Pythonfil...
FromSent OnAttachments
Ken SarkiesJan 24, 2007 4:16 pm 
Gordon MessmerJan 24, 2007 4:39 pm 
Ken SarkiesJan 25, 2007 8:59 pm 
Gordon MessmerJan 26, 2007 10:16 am 
Ken SarkiesJan 28, 2007 1:59 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Dialback in Pythonfilter 0.18 rejecting good addressesActions...
From:Ken Sarkies (ksar@internode.on.net)
Date:Jan 24, 2007 4:16:29 pm
List:net.sourceforge.lists.courier-users

Hi All

I just now installed version 0.18 of Courier Pythonfilter to see if there was a change from the 0.17 version in the behaviour of dialback. I noticed that Gordon Messmer had made some changes to dialback, however I am still experiencing rejection of good email addresses by certain servers. It looks to be a useful module so I'm interested to track down what these servers are doing if it can be helpful. At present I need to turn off the module.

The best I can offer at the moment, not having any expertise in the topic, is to provide the responses logged by the dialback module. One of the servers observed is bigpond, which is probably our biggest ISP in Oz. The log messages are:

Jan 25 09:31:02 hta21 courieresmtpd: error,relay=::ffff:203.57.193.26,from=<xx@agl.com.au>: 421 mail2.agl.com.au rejected the MAIL FROM command

(this one is a genuine email address) and

Jan 24 20:36:42 hta21 courieresmtpd: error,relay=::ffff:144.140.82.183,from=<yyy@bigpond.net.au>: 421 extmail.bpbb.bigpond.com rejected the MAIL FROM command

There are others also from a number of different but valid email addresses.

Let me know if I can provide any more useful info.

cheers, Ken