3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop+Postfix
FromSent OnAttachments
Alberto BenatiApr 25, 2002 7:50 am 
Matthias AndreeApr 26, 2002 1:15 pm 
Alberto BenatiApr 30, 2002 7:08 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:Re: [maildropl] Maildrop+PostfixActions...
From:Matthias Andree (ma@dt.e-technik.uni-dortmund.de)
Date:Apr 26, 2002 1:15:40 pm
List:net.sourceforge.lists.courier-maildrop

Alberto Benati <ben@economia.unibo.it> writes:

Now, I think a mail filtering. I take maildrop-1.3.8.20020418.tar.gz and read a FAQ: http://www-dt.e-technik.uni-dortmund.de/~ma/postfix/HOWTO-maildrop.html

<shrug>

Looks like the README.postfix that ships with maildrop is better for your approach. However, ...

In master.cf, i try: 1) maildrop unix - n n - - pipe flags=uR user=vscan argv=/usr/bin/maildrop -d {recipient}

2) maildrop unix - n n - - pipe flags=uR user=vscan argv=/usr/bin/maildrop -d {user}

3) maildrop unix - n n - - pipe flags=uR user=vscan argv=/usr/bin/maildrop -d user

All these three are wrong. Instead, use ${recipient} in 1, ${user} in 2.

4) maildrop unix - n n - - pipe flags=uR user=vscan argv=/usr/bin/maildrop -d /usr/bin/maildrop -d "$USER" -f
"$SENDER" "$EXTENSION"

Check man maildrop: -d /usr/bin/maildrop cannot work either, because the user you want to deliver to is not "/usr/bin/maildrop".

but i have always:

Apr 25 15:40:45 pcalby maildrop[14781]: Invalid user specified.

Apr 25 15:40:45 pcalby postfix/pipe[14780]: E3C7E169CF: to=<ben@prova.it>, relay=maildrop, delay=1, status=bounced (user unknown. Command output: /usr/bin/maildrop: Invalid user specified. )

Obviously.

-- Matthias Andree