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