lør, 11.06.2005 kl. 02.02 skrev Jean Théry:
i'm using :
- postfix-2.2.3_1,1
- maildrop-1.8.0_3
- courier-imap-4.0.3,1
- courier-authlib-base-0.56
- courier-authlib-mysql-0.56
(all from FreeBSD ports)
(without routing to maildrop transport postfix exec normal operations)
i've made a transport and routed mails in it in master.cf :
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d
${user}@${nexthop} ${extension} ${recipient} ${user} ${nexthop}
${sender} -w 90
This looks horrible to me - mind you, I don't use a transport for
maildrop, all my users are on the MTA machine. What are you trying to
do?
when i send mail i get this in maillog:
Jun 11 01:04:42 ao postfix/pipe[96040]: 50B7A896: to=<us...@domain.tld>,
relay=maildrop, delay=0, status=bounced (user unknown. Command output:
Invalid user specified. )
Turn on verbose for this service in master.cf (put -v at the end of the
line) better to see what is happening.
but if i execute a "cat mail | maildrop -d $user" in a shell (su vmail)
it work
Well, that's not the same, is it?
how postfix emulate shell environment to make these differences ?
i'm not a coder but it seem other user have the same problem
Did you read the Postfix maildrop HOWTO (it's pretty lousy, but still
...) and the maildrop README.postfix?
--Tonni
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] postfix & maildrop
