Hi Gordon
Then put the FQDN of your router in "me". Don't forget to run
"makealiases" after changing the "me" file.
Yes that was probably where the problem was. Our ISP has set
mail.trinity.asn.au in our DNS record, so I should have set the "me"
file to that rather than letting the internal name of the machine be used.
We
have been running Courier-MTA for 2 and a half years without any
apparent connection problems, certainly nothing visibly associated
with DNS resolution.
Do you read all of your "postmaster" mail?
Indeed I do. That's why I was surprised to discover that we had a
misconfiguration. I thought that Courier was running flawlessly.
Certainly no-one has missed any emails and the only DSN problems we see
are occasional "User Unknown" where Courier sends a vacation reply in
response to spam.
Is it that Courier is sending DSNs with the full machine hostname that
is causing this?
It's related. Courier uses the hostname of the machine on which it runs
for certain operations, and the dialback module of pythonfilter does, too.
I was wrong about the DSN bit, though. Courier actually uses no return
address when sending DSNs. You can do that in dialback, too, if your
python isn't super old. Just modify the dialback.py file and set:
postmasterAddr = ''
You might run in to a minor problem: some sites don't accept mail from
null senders. Those sites are in violation of RFC requirements, so you
can decide for yourself whether or not you want to accept mail from them.
Thanks for all this. Dialback seems to be OK for now but I'll monitor it
for a while. We appreciate the work you have done on pythonfilter. The
greylisting neatly killed almost all our spam so I could remove a heap
of dubious custom rules in spamassassin.
cheers, Ken
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Dialback in Pytho...
