masqmail

view examples/example.route @ 246:4cff8638dd9b

SMTP client: tries EHLO now always first Changed the behavior of the SMTP client. Now always an EHLO greeting is sent, no matter what kind of greeting text the server had sent. If the EHLO failed, an HELO greeting is tried as fall back. This is the behavior RFC 2821 requires (section 3.2). This change will fix setups that were not possible to sent to a server because that requires AUTH but hadn't said ``ESMTP'' in its greeting message. See also: Debian bug #349211 Thanks to Steffen (inne)
author markus schnalke <meillo@marmaro.de>
date Thu, 28 Oct 2010 16:40:02 -0300
parents 08114f7dcc23
children 55b7bde95d37
line source
1 # Example route file for masqmail
2 # see also: man 5 masqmail.route
4 #
5 # mail properties tested for:
6 #
8 # users that can send mail over this connection:
9 # this is a list of the local parts of the original return addresses, as they are
10 # configured with your mail client. If not set, anybody may send.
12 allowed_mail_locals = "okurth"
14 # local_hosts and local_nets will be checked before this.
15 # cpwright.com uses the dialup up list of dul.maps.vix.com,
16 # so I cannot send any mail over this connection to that domain.
17 # There are probably many others... :-( (No, this is okay. Nobody
18 # wants his mailbox stuffed to the ceiling with spam...)
19 #
20 # You will find this necessary only if you send mail directly
21 # (if mail_host is not set below)
23 not_allowed_rcpt_domains = "cpwright.com"
25 #
26 # settings:
27 #
29 # the mail server which relays mail for you:
30 # if this is not set, mail will be sent directly.
31 # If your ISP gives has a mail server, it is wiser to use it:
33 mail_host = "mail.isp.com"
35 # Make picky servers happy:
36 # If set, we look up our own name as seen from the network
37 # and send this in our HELO/EHLO message. Otherwise we send our host name,
38 # which is probably different for dialup conections and may be unknown outside.
39 # Some servers complain,
40 # which is really crazy, since it is senseless to lie about it...
41 # Unfortunately, some ISPs do not give you a name, just an ip address. In this case,
42 # we have a delay until the DNS lookup fails.
44 do_correct_helo = true
46 # 'forge' headers:
48 # return path and From: address are TWO different things:
49 #
50 # the return path is address where delivery failure messages will go
51 # to, and this address will be checked by many MTAs in the outside
52 # world, so it should be valid. It canNOT contain a real name:
53 # 'miller@foo.com' is a valid return path, but 'Charlie Miller <miller@foo.com>' is NOT.
54 #
55 # The From: address is the address the recipient sees, and where
56 # replies will go to (if you do not set a Reply-to header). In most
57 # cases it corresponds to the return path, but this is not
58 # required. It CAN have a real name, both examples for Charlie above
59 # are correct, and it is more pretty to include a real name.
60 #
61 # The return path:
62 # if we send the mail directly, we can set any valid address here,
63 # use the one you prefer to get error messages to:
64 # Use EITHER set_return_path_domain OR map_return_path_addresses
65 #
66 # this sets the return path kurth@anywhere.org to kurth@innominate.de
67 #set_return_path_domain = "innominate.de"
68 # this sets okurth@somewhere.else.org to kurth@innominate.de, and
69 # leaves all other addresses untouched:
70 map_return_path_addresses = "okurth: kurth@innominate.de"
72 # 'From:' header:
73 # Use EITHER set_h_from_domain OR map_h_from_addresses
74 #set_h_from_domain = "uni-sw.gwdg.de"
75 map_h_from_addresses = "okurth: Oliver Kurth <kurth@innominate.de>"
77 # if your mail server outside uses the AUTH machanism, set the following.
78 # You need to compile masqmail with AUTH support (--enable-auth option for ./configure):
79 # for auth_name, only 'cram-md5' and 'login' are supported.
80 # see also: man 5 masqmail.route
82 #auth_name="cram-md5"
83 #auth_login="yourname"
84 #auth_secret="dontTellAnyBody"