masqmail

annotate docs/FAQ @ 354:08932c629849

reworked the route concept; removed the idea of the localnet Renamed to reflect the actual meaning more clearly: s/online_routes/query_routes/g s/local_net_route/permanent_routes/g Removed local_nets, which are now represented by allowed_recipients in a permanent route. (See. examples/localnet.route) There is no more abiguity between `local' and `local net'. Run admin/config-transition on your config to learn how to update it.
author markus schnalke <meillo@marmaro.de>
date Sun, 04 Sep 2011 11:25:38 +0200
parents
children
rev   line source
meillo@215 1 Frequently Asked Questions
meillo@215 2 ==========================
meillo@215 3
meillo@215 4 Some of these questions were never asked, but I thought they will
meillo@215 5 be some time. Some were asked.
meillo@215 6
meillo@215 7
meillo@215 8 When do I need MasqMail?
meillo@215 9 ------------------------
meillo@215 10 You do not *need* it. But it makes sending mails via a dialup
meillo@215 11 connection a lot easier.
meillo@215 12
meillo@215 13 It is useful if you dial to the internet from time to time via a
meillo@215 14 modem and connect to different providers, each one with a
meillo@215 15 different configuration. Other MTAs are not flexible enough if you
meillo@215 16 have to send mails via different mail servers for each provider.
meillo@215 17 With MasqMail you can configure a different one for each provider
meillo@215 18 and even set your return addresses differently.
meillo@215 19
meillo@215 20 It is also useful if you have a LAN with a gateway which is
meillo@215 21 connected to the internet via a modem because you can rewrite your
meillo@215 22 address depending on whether the recipients are *inside* or
meillo@215 23 *outside* your LAN. So responses and delivery failures on your LAN
meillo@215 24 will be sent to you without leaving it, while those outside will
meillo@215 25 be delivered to your address outside. (But it does not yet send
meillo@215 26 delivery failures itself yet.)
meillo@215 27
meillo@215 28 MasqMail is also often used on notebooks.
meillo@215 29
meillo@215 30
meillo@215 31 When do I not need MasqMail?
meillo@215 32 ----------------------------
meillo@215 33 The use of MasqMail is *strongly* discouraged if you have a
meillo@215 34 permanent connection to the internet without a firewall. First
meillo@215 35 because it does not have the ability to block relaying (it relays
meillo@215 36 every mail) and second because there are no capabilities to
meillo@215 37 protect against SPAM. You will not take advantages of its features
meillo@215 38 anyway.
meillo@215 39
meillo@215 40
meillo@215 41 Is there a mailing list for MasqMail?
meillo@215 42 -------------------------------------
meillo@215 43 Yes, there is! See here.
meillo@215 44
meillo@215 45
meillo@215 46 After starting masmail, I get the following message: "could
meillo@215 47 not gain root privileges. Is the setuid bit set?"
meillo@215 48 -----------------------------------------------------------
meillo@215 49 Set the set-user-id-bit with chmod u+s /usr/sbin/masqmail.
meillo@215 50
meillo@215 51
meillo@215 52 After starting masmail, I get the following message: "bind:
meillo@215 53 (terminating): Address already in use"
meillo@215 54 -----------------------------------------------------------
meillo@215 55 This means that there is already a process listening on a port,
meillo@215 56 usually 25. You either have another MTA running in background
meillo@215 57 (sendmail, exim, etc...) or another instance of masqmail.
meillo@215 58
meillo@215 59 It may also mean that the ports you configured MM to listen to
meillo@215 60 (with 'listen_addresses') are on the same IP address, eg. you may
meillo@215 61 have set your hostname to 127.0.0.1 and try to listen on localhost
meillo@215 62 and your host name. In this case either set your hostname to
meillo@215 63 another IP address or delete one of the conflicting entries.
meillo@215 64
meillo@215 65
meillo@215 66 My friends told me that they do not see my full name in their
meillo@215 67 inbox, although it is configured in my mail client.
meillo@215 68 -------------------------------------------------------------
meillo@215 69 You probably used the map_h_from_addresses feature in the route
meillo@215 70 configuration and forgot to set your real name. The syntax is:
meillo@215 71
meillo@215 72 map_h_from_addresses = "charlie:Charlie Miller <cmiller@foo.com>";
meillo@215 73
meillo@215 74 Do not forget the Charlie Miller.
meillo@215 75
meillo@215 76
meillo@215 77 With connection method file, I get the following message in
meillo@215 78 the log file: "Could not open /tmp/connect_route: Permission
meillo@215 79 denied".
meillo@215 80 ------------------------------------------------------------
meillo@215 81 In your ip-up script, you have to set read permission to the user
meillo@215 82 masqmail runs as. After you write the file with the connection
meillo@215 83 name, set read permission to all with chmod ugo+r file.
meillo@215 84
meillo@215 85
meillo@215 86 With connection method file, I get the following message in
meillo@215 87 the log file: "route with name name not found.".
meillo@215 88 -----------------------------------------------------------
meillo@215 89 Check whether the name in the file is really identical to name you
meillo@215 90 gave to the route configuration (case sensitive!).
meillo@215 91
meillo@215 92
meillo@215 93 I found a bug.
meillo@215 94 --------------
meillo@215 95 Make sure you are using the newest version, in case of doubt
meillo@215 96 search it in freshmeat. If you do, tell me. See also the section
meillo@215 97 bugs on the main page.
meillo@215 98
meillo@215 99
meillo@215 100 I think I found a bug, but I am not sure whether I configured
meillo@215 101 MasqMail incorrectly.
meillo@215 102 -------------------------------------------------------------
meillo@215 103 Don't care. Tell me. Or write to the mailing list.
meillo@215 104
meillo@215 105
meillo@215 106
meillo@215 107 Written by Oliver Kurth
meillo@215 108 Last modified by him: Tue May 30 15:19:56 CEST 2000