Truong Tan Son wrote:
Dear mouss,
Your guidance is right.
Postfix automatically separates each recipient in header by
"maildrop_destination_recipient_limit" option.
Because my Postfix can not authenticate the sender when sender is an alias, so I
change to use maildropfilter to fordward
message at backend.
I don't understand what is your problem and what you are trying to do.
what authentication are you talking about?
Please teach me if you have better solution to solve this problem.
**My scenario:
group@ .. = {user1@ .., user2@.., user3@..}; group@, user@.. are virtual
users.
If sender = group@.. , request authenticated username&password to allow sending.
else If recipient = group@.., then delivers message to user list {user1@..,
user2@.., user3@..}
#cat $HOME/group/Maildir/.forward
user1@.. user2@.. user3@...
#cat /etc/maildroprc
`test -f $HOME/$USER/Maildir/.forward`
if ($RETURNCODE == 0)
{
str=`head -1 $HOME/$USER/Maildir/.forward`
to "!$str"
}
else
{
to "$HOME/$USER/Maildir/"
}
By using exclamation mark with "!" before list of user, I can deliver message to
all users in file.
But this solution is suitable for any users, it can't solve if list contains
more user.
10 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] How to extract $USER ...
