Micah Anderson wrote:
On Sat, 08 Dec 2007 20:18:11 +0100, mouss wrote:
Micah Anderson wrote:
I've found that sending mail to micah+te...@riseup.net results in the
message getting sent to maildrop, but then it silently disappears,
without a trace. Postfix sends the message to the maildrop service, but
it doesn't appear to be delivered and no logger messages from my
maildrop are triggered on it.
Dec 6 11:25:37 cormorant postfix/pipe[20262]: CD32B6036C7: to=<micah
+te...@riseup.net>, relay=maildrop, delay=0.22, delays=0.04/0.12/0/0.07,
dsn=2.0.0, status=sent (delivered via maildrop service)
can you show the maildrop section in your master.cf?
maildrop unix - n n - - pipe
flags=DRhu user=mail argv=/usr/local/bin/maildrop_wrapper -w 90 -d
${recipient}
but how would maildrop find micah+te...@riseup.net ?
you should use ${user}@${nexthop} instead of ${recipient}.
Also make sure you have:
maildrop_destination_recipient_limit = 1
so that maildrop is called for each recipient.
The maildrop_wrapper has the following:
#!/bin/sh
/usr/bin/maildrop $1 $2 $3 $4 $5
when passing arguments to the shell, always quote them.
if [[ "$?" == "77" || "$?" == "75" ]]; then
exit 100
fi
please test without the wrapper.
also, add a logger line at the beginning of maildroprc to confirm that
it (/etc/maildroprc) is being used.
I did that and messages that are sent with a + aren't logged, as if they
aren't making it that far.
Let me guess: maildrop can't find "micah+te...@riseup.net", returns an
error, but you don't catch it.
test with
# maildrop -V 4 -d micah+te...@riseup.net < /dev/null
you probably want to change the arguments you use in postfix and replace
${recipient} with ${user}@${nexthop} (if you need the extension, add a
parameter: ${extension})
9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Mail with + getting s...
