> I have postfix and virtual domains, how do I add a .forward file for a
> specific virtual user?

> I have

> virtual_mailbox_base = /srv/mail

> in main.cf. I tried creating a .forward file in /srv/mail/domain/user/ (where
> mail is delivered) and also /srv/mail/.forward+user@domain but it did not
> work.

> postconf -d|grep forward_path
> forward_path = $home/.forward${recipient_delimiter}${extension},
> $home/.forward

> > >>>>> I have postfix and virtual domains, how do I add a .forward file
> > >>>>> for a specific virtual user?

> > >>>>> I have

> > >>>>> virtual_mailbox_base = /srv/mail

> > >>>>> in main.cf. I tried creating a .forward file in
> > >>>>> /srv/mail/domain/user/ (where mail is delivered) and also
> > >>>>> /srv/mail/.forward+user@domain but it did not work.

> > >>>>> postconf -d|grep forward_path
> > >>>>> forward_path = $home/.forward${recipient_delimiter}${extension},
> > >>>>> $home/.forward

> > >>>> .forward processing is implemented in the local(8) delivery
> > >>>> agent, so that won't work with virtual mailbox users.

> > >>>> Instead add an entry for the user in virtual_alias_maps.

> > >>> I use sql lookups for my virtual domains:

> > >>> virtual_alias_maps =
> > >>>  mysql:/etc/postfix/mysql_virtual_alias_maps.cf,

> > >>> /etc/postfix/mysql_virtual_alias_maps.cf:
> > >>> ....
> > >>> query = SELECT goto FROM alias WHERE address='%s' and active = 1

> > >>> My goal is to be able to run maildrop for a specific user, I tried
> > >>> updating the `alias` table and setting goto to '| /path/to/maildrop '
> > >>> but postfix complains with:

> > >>>  unknown user: "'|/usr/bin/maildrop.mailfilter"

> > >> Ah.  In that case, add an entry to transport_maps for that user.

> > > OK, I tried :
> > > user@domain       '| /usr/bin/maildrop
> > > /srv/mail/user/domain/.mailfilter - '

> > > but i get:

> > > warning: connect to
> > > transport '| /usr/bin/maildrop /srv/mail/domain/user/.mailfilter - ':
> > > No such file or directory

> > > So, how to add a command as a transport?

> > check MAILDROP README. the transport entry should look like this:

> > user@domain      maildrop:

> > where maildrop is a transport defined in master.cf.

> Thanks, I already figured that part, but MAILDROP README does not mention
> how to make maildrop to work with virtual users. With teh default
> configuration of master.cf it is called as maildrop -d user@domain and that
> does not work. How to specify the transport in master.cf so that it works
> for virtual users.

> From what I read in `man pipe` there is no macro for the recipient domain
> so I cannot run  /usr/bin/maildrop
> /srv/mail/domain/${recipient}/.mailfilter in mastre.cf.

> to work, it needs a green card ;-p

> maildrop does work with virtual users, but there are so many different
> virtual setups. If you just say "it doesn't work", we can't help. if you
> explain your problem, you may get help.

> Note that if your maildrop is built with authlib support, it will try to
> ask authdaemon... etc.

> > How to specify the transport in master.cf so that it works for virtual
> > users.

> > From what I read in `man pipe` there is no macro for the recipient domain
> > so I cannot run  /usr/bin/maildrop
> > /srv/mail/domain/${recipient}/.mailfilter in mastre.cf.

> $(domain} is available in postfix 2.5, but you can use ${nexthop}. The
> second example in the MAILDROP README uses

>     -d ${user}@${nexthop}

> did you miss it?

> In the standart configuration, maildrop transport is defined as `maildrop -d
> ${recipeint}`, which doen not work (out of the box) with virtual users.

> #!/bin/bash
> echo "$@" >> /tmp/_debug

> and it turns out $nexthop resolves ti dummy. I have a 'user@domain
> maildrop:dummy' line in transport maps.