Sunil Shetye <shetye(_at_)bombay(_dot_)retortsoft(_dot_)com> writes:
Aliases (which are MTA specific) may not be understood by an MDA. So,
a mapping like:
group(_at_)bombay(_dot_)retortsoft(_dot_)com -> user1,user2,user3
would be required.
An MDA cannot do this. You need an MTA for alias /expansion/. That's why
I suggested to have two separate options, named "mda" and "mta". We may
want to give them names that give the less experienced users a clue,
such as (mda) "mailbox_program" and (mta) "mailserver_inject_program" or
something.
That's correct, but I think that fetchmail already does this, with the
"is remote1=local1 remote2=local2 here" mapping syntax in multidrop
mode.
Not always. From the man page,
The `localdomains' option allows you to declare a list of
domains which fetchmail should consider local. When fetchmail
is parsing address lines in multidrop modes, and a trailing
segment of a host name matches a declared local domain, that
address is passed through to the listener or MDA unaltered
(local-name mappings are not applied).
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
So, when `localdomains' is used, the full email address is being
passed to the MDA now.
You can use "aka" if you want to keep the mapping (I did not test this
though.), or you can inject into an MTA and use its virtual users
mapping.
--
Matthias Andree