7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] dot-courier: "non...
FromSent OnAttachments
Sam VarshavchikSep 5, 2002 6:52 am 
Alexei Batyr'Sep 6, 2002 3:33 am 
Roland SchneiderSep 6, 2002 4:03 am 
Sam VarshavchikSep 6, 2002 6:03 am 
Alexei Batyr'Sep 6, 2002 6:46 am 
Sam VarshavchikSep 6, 2002 7:53 am 
Nerijus BaliunasSep 8, 2002 1:30 pm 
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:Re: [courier-users] dot-courier: "non-DSN" exit codeActions...
From:Roland Schneider (list@serv.ch)
Date:Sep 6, 2002 4:03:40 am
List:net.sourceforge.lists.courier-users

--Alexei Batyr' wrote on 06.09.2002 14:32 +0400:

I remember that some time ago there was two types of "bad" exit codes in .courier file - some of them caused sending DSNs and some others not. Now any of the listed in dot-corier manpage codes (64, 65, 67, 68, 69, 70, 76, 77, 78, or 112) generate DSN. What's changed? Is there now a possibility to set up .courier (or .mailfilter) exit code so that courier reply only with SMTP error without DSN? E.g. "catchall" .courier-default file just reply with "550 User unknown" when receiving mail for non-existent local users?

messages processed by .courier-dotfiles (or .mailfilter) have already been received and accepted by the server.

messages will be only accepted for 'existing' users, dont define a .courier-default if you dont want to accept mail for any possible localpart.

beside bofh's spamtrap courier offers two solutions to reject mail for existing users: the daemonized courierfilter (with perlfilter) and maildropfilter from the whitelist-api, which also could run perl instead of maildrop.

Roland