David Somers wrote:
I would not characterize delivery that way.  "local" domains differ from
"hosted" domains in very few ways.  Hosted domains have a backend that
can contain a few items which aren't available for local users.  If you
specify them, Courier's behavior will change.  If you do not specify
anything for hosted users that wouldn't be available for a local user,
delivery will be handled the same way.

At the moment my local and hosted users are being treated differently... maildrop’s maildroprc is happening for localusers and not for hosted users.

Like I said: If you specify something for hosted users which would not be available for local users, behavior will change. If you do not specify anything for hosted users that local users don't have, behavior will be the same.


You specified the "mail" attribute, which is something that the system password file does not have, so it's not available for local users. Doing so changes delivery behavior for hosted users. The "mail" attribute is a delivery instruction. If you specify a delivery instruction for a user, DEFAULTDELIVERY will not be used. DEFAULTDELIVERY will only be used if no other delivery instructions are available.

All I want to do is configure it to run some filter against all incoming
mail and bounce/process according to a bunch of rules.

I really recommend that you not try to bounce mail after accepting it from SMTP. No good comes of it.

Perhaps bounce was the wrong word... reject would be better... ideally when somebody tries to send some mail that I’m not happy to accept (for example, like trying to send .exe attachments), courier will just reject it. If somebody could tell me how to do this I’d be really grateful...

Don't do this with maildrop. When maildrop runs, you've already accepted mail via SMTP, and there is no longer any real garantee that the return address on it is valid. Bouncing the message in maildrop (or procmail, or any other local delivery agent) will both fill up your mail queue with undeliverable bounces, and bounce junk mail to users who didn't send it.


If you want to reject mail based on attachments, you should use a courierfilter.

One option would be to use the Perl based Courier::Filter with the Parts module:
http://search.cpan.org/~jmehnle/Courier-Filter-0.15/lib/Courier/Filter/Module/Parts.pm


Another option would be to use pythonfilter, which I wrote:
http://phantom.dragonsdawn.net/~gordon/courier-patches/courier-pythonfilter/courier-pythonfilter-0.8.tar.gz
with the attachment filter (which is not yet included in the main package):
http://robert.private.outertech.com/courierfilter/attachment.py

I had hope
that getting a MTA up on my new Linux box would be a fairly simple processs,
but its sadly more long winded and complicated than I expected :(

Welcome to the internet. :)


------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to