meillo@3: Especially the map commands need a closer look. These lines
meillo@3: map local parts of the given address towards a full RFC 822 compliant
meillo@3: email address. map_return_path_addresses does this for the
meillo@3: passed Return address, map_h_from_addresses for the given
meillo@3: From part.
meillo@3:
meillo@3: But, pay attention! As you can see the strange name gmx_foo in
meillo@3: front of both items has never been seen until now. And in
meillo@3: allowed_mail_locals you see the same item. What about this?
meillo@3:
meillo@3: An E-Mail will be passed towards the E-Mail provider giving a so
meillo@3: called envelope. This construction envelopes the real E-Mail
meillo@3: and passes important things like the address of the sender and the
meillo@3: address of the receiver to the E-Mail provider. These envelope date
meillo@3: will never be seen again on the receiver's site, because the MTA
meillo@3: running on receiver's host will delete them. But only the envelope is
meillo@3: valid for any MTA distinguishing the route towards the receiver. So,
meillo@3: it must be a valid address.
meillo@3:
meillo@3: Per default MasqMail uses the current user-name as
meillo@3: Envelope-From:. If we want to use different E-Mail accounts
meillo@3: with mapping of addresses via the above shown map_return_path_addresses and
meillo@3: map_h_from_addresses we have to to mutilate the envelope
meillo@3: data! That could be done very easily within mutt.
meillo@3:
meillo@3:
meillo@3: Next:masqmail/web_foo.route
meillo@3: Up:Receiving and sending mails
meillo@3: Previous:masqmail.conf
meillo@3:
meillo@3:
meillo@3: Georg Lohrer
meillo@3: 2001-03-23
meillo@3:
meillo@3:
meillo@3:
meillo@3: