1 message in net.sourceforge.lists.courier-maildrop[maildropl] Questions when converting...
FromSent OnAttachments
Jost KriegerJan 23, 2003 10:47 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:[maildropl] Questions when converting from a pure .qmail setupActions...
From:Jost Krieger (Jost@ruhr-uni-bochum.de)
Date:Jan 23, 2003 10:47:41 am
List:net.sourceforge.lists.courier-maildrop

Currently, I am working with 289 .qmail-xxx Files :-)

Most of them look like |block ./Maildir-xxx/

(block is a spam-control script)

Some of them have no block (mailinglists about spam etc.), some go to plain mbox files.

I' like to convert most of these to a central .mailfilter file and am now looking for suggestions. I plan to use a central .qmail-default file and "import EXT".

Should I a) use a huge if cascade (naaah) b) include a conf file for each list c) use a few separate files and pattern matching, or d) do something completely different.

I also came upon a few difficulties: This list seems to suggest I just put "|maildrop" in my .qmail-default. Problem: 1. I don't get the correct envelope sender (qmail-local leaves it in $SENDER) 2. Even if I got it, maildrop doesn't seem to generate a Return-Path: header, as mandated by RFC 2821.

Currently I use "|preline -f maildrop".

Next problem is, how does maildrop handle the envelope sender in forwarding situations? It seems, without preline, I get "list" semantics (errors go to me), with preline, I get forward semantics (thanks to qmail-inject), errors go to the original sender. Is there any way to control this?

Thanks for any help Jost