Changes between Version 1 and Version 2 of MuttGuide/Headers


Ignore:
Timestamp:
Oct 27, 2013 6:28:15 PM (4 years ago)
Author:
MichaelRay
Comment:

RFC 2606 "example.org" for live domain examples(not as fun though), preserving fun subdomains , minor wikiml fixes

Legend:

Unmodified
Added
Removed
Modified
  • MuttGuide/Headers

    v1 v2  
    11=== Setting the envelope sender for outgoing messages ===
    22
    3 Before transmitting the message to the server the client has to
    4 specify the sender and the recipient of the message, respectively with
     3Before transmitting the message to the server, the client has to
     4specify the sender and the recipient of the message with
    55the "FROM" and "RCPT" SMTP commands. In order to avoid horrible
    66confusion, you need to bear in mind that the value used during the
     
    1717the server (transmitted to another mail server). This address has to
    1818be meaningful (e.g. it has to be well-formed and its domain has to
    19 corresponds to that of an existant DNS domain) otherwise the message
     19correspond to an existing domain) otherwise the message
    2020could be filtered out as spam (as many spam messages don't have a
    2121valid return path). The return path is also, as the name suggests, the
     
    2424
    2525It could be set to the address of the postmaster of a site
    26 (e.g. <tt>postmaster@cool-enterprise.org</tt>), or it could be set (in the
     26(e.g. '''postmaster@example.com'''), or it could be set (in the
    2727case of a satellite system) to the address provided by the mail
    28 account provider (e.g. <tt>john.doe@cool-mail-provider.com</tt>) when the
     28account provider (e.g. '''john.doe@example.com''') when the
    2929message is relayed to an external mail server.
    3030
    3131By default most SMTP client agents will set the return path to the
    3232local address of the process which spawns them, mutt in our case, so
    33 if the user <tt>alice</tt> in the <tt>rabbit-house.wonderland.org</tt> system will
     33if the user '''alice''' in the '''rabbit-house.example.org''' system will
    3434compose and send a message with mutt, the SMTP client to which the
    3535message is piped in will use as return path the address
    36 <tt>alice@rabbit-house.wonderland.org</tt> (it depends on the mailer
     36'''alice@rabbit-house.example.org''' (it depends on the mailer
    3737configuration).
    3838
     
    4141
    4242 set use_envelope_from # a boolean value, you can deselect it with set nouse_envelope_from
    43  set envelope_from_address= "alice@beyond-the-mirror.org"
     43 set envelope_from_address= "alice@beyond-the-mirror.example.org"
    4444
    4545The manual says about use_envelope_from:
    4646
    47 <i>
     47{{{
    4848When set, mutt will use ``$envelope_from_address''
    4949as the envelope sender if that is set, otherwise it will attempt to
     
    5353yourself, or if the sendmail on your machine doesn't support that
    5454command line switch.
    55 </i>
     55}}}
    5656
    5757Fortunately most SMTP mailers (postfix, exim) mimic the sendmail
    5858command line interface, so this will work with those mailers too.
    5959
    60 You may also want to dynamically set the <tt>use_envelope_from</tt> and
    61 <tt>envelope_from_address</tt> variables using the usual mutt macro/hook
    62 tricks (see ConfigTricks). A simple way to set it dinamically could be
    63 to set <tt>use_envelope_from</tt> and then let mutt use the (eventually
    64 dinamically generated) "From: " header address (set with <tt>my_hdr</tt> or
    65 with the <tt>from</tt> variable).
     60You may also want to dynamically set the '''use_envelope_from''' and
     61'''envelope_from_address''' variables using the usual mutt macro/hook
     62tricks (see ConfigTricks). A simple way to set it dynamically would be
     63to set '''use_envelope_from''' and then let mutt use the (eventually
     64dynamically generated) "From: " header address (set with '''my_hdr''' or
     65with the '''from''' variable).
    6666
    6767Note that in order to be able to perform this operation you may need
    6868special permission: e.g. with exim if your username isn't in the
    69 <tt>untrusted_set_sender</tt> list it need either to be in the <tt>trusted_users</tt> or
    70 in the <tt>trusted_groups</tt> list to let you set the return path.
     69'''untrusted_set_sender''' list it need either to be in the '''trusted_users''' or
     70in the '''trusted_groups''' list to let you set the return path.
    7171
    7272Finally the local server may rewrite the return path (eventually overriding