Simeon Ott:
> On 30.09.2011, at 19:25, Simeon Ott wrote:
>
> > hello,
> >
> > i recently configured gnarwl autoresponder on my mailserver. the
> autoresponder works great as long as the sender doesn't use BATV.
> otherwise the autoresponded message is not delivered to the origin
> sender. is there a possibility to pipe another attribute then
> ${sender} in the master.cf?
> >
> > here are the relevant configuration parts:
> > master.cf:
> > gnarwl unix - n n - - pipe flags=F
> > user=vmail argv=/usr/bin/gnarwl -a ${user} -s ${sender}
...
> Sep 30 09:22:35 ares postfix/qmgr[23383]: B00CF2C649F:
> from=<prvs=1254408a08=send...@senderdomain.com>, size=3407, nrcpt=3 (queue
> active)
> Sep 30 09:22:36 ares postfix/pipe[23817]: B00CF2C649F:
> to=<rc...@rcvdomain.com,rc...@rcvdomain.com@autoreply.example.com>,
> relay=gnarwl, delay=0.3, delays=0.09/0.04/0/0.17, dsn=2.0.0, status=sent
> (delivered via gnarwl service)
The above shows that you provide gnarwl with the BATV-ed envelope
sender address.
You also mention that gnarwl replies to some different address but
provide no concrete evidence.
If the sender really looks like
<rc...@rcvdomain.com,rc...@rcvdomain.com@autoreply.example.com>
then that is badly malformed and that should be fixed first.
To debug gnarwl, take an email message and invoke gnarwl by hand:
$ gnarwl -a rcpt1@whatever -s prvs=whatever@whatever < email-message-file
Then, observe what happens. If it does not reply to the sender
that you specify, then gnarwl is mis-configured or broken.
Wietse
