masqmail

changeset 215:08b32edca1d5

added the contents of the old FAQ page it surely needs an update
author meillo@marmaro.de
date Mon, 19 Jul 2010 14:10:14 +0200
parents ecd8d737d78e
children 84bf7a6b6ccd
files docs/FAQ
diffstat 1 files changed, 108 insertions(+), 0 deletions(-) [+]
line diff
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/docs/FAQ	Mon Jul 19 14:10:14 2010 +0200
     1.3 @@ -0,0 +1,108 @@
     1.4 +Frequently Asked Questions
     1.5 +==========================
     1.6 +
     1.7 +Some of these questions were never asked, but I thought they will
     1.8 +be some time. Some were asked.
     1.9 +
    1.10 +
    1.11 +When do I need MasqMail?
    1.12 +------------------------
    1.13 +You do not *need* it. But it makes sending mails via a dialup
    1.14 +connection a lot easier.
    1.15 +
    1.16 +It is useful if you dial to the internet from time to time via a
    1.17 +modem and connect to different providers, each one with a
    1.18 +different configuration. Other MTAs are not flexible enough if you
    1.19 +have to send mails via different mail servers for each provider.
    1.20 +With MasqMail you can configure a different one for each provider
    1.21 +and even set your return addresses differently.
    1.22 +
    1.23 +It is also useful if you have a LAN with a gateway which is
    1.24 +connected to the internet via a modem because you can rewrite your
    1.25 +address depending on whether the recipients are *inside* or
    1.26 +*outside* your LAN. So responses and delivery failures on your LAN
    1.27 +will be sent to you without leaving it, while those outside will
    1.28 +be delivered to your address outside. (But it does not yet send
    1.29 +delivery failures itself yet.)
    1.30 +
    1.31 +MasqMail is also often used on notebooks.
    1.32 +
    1.33 +
    1.34 +When do I not need MasqMail?
    1.35 +----------------------------
    1.36 +The use of MasqMail is *strongly* discouraged if you have a
    1.37 +permanent connection to the internet without a firewall. First
    1.38 +because it does not have the ability to block relaying (it relays
    1.39 +every mail) and second because there are no capabilities to
    1.40 +protect against SPAM. You will not take advantages of its features
    1.41 +anyway.
    1.42 +
    1.43 +
    1.44 +Is there a mailing list for MasqMail?
    1.45 +-------------------------------------
    1.46 +Yes, there is! See here.
    1.47 +
    1.48 +
    1.49 +After starting masmail, I get the following message: "could
    1.50 +not gain root privileges. Is the setuid bit set?"
    1.51 +-----------------------------------------------------------
    1.52 +Set the set-user-id-bit with chmod u+s /usr/sbin/masqmail.
    1.53 +
    1.54 +
    1.55 +After starting masmail, I get the following message: "bind:
    1.56 +(terminating): Address already in use"
    1.57 +-----------------------------------------------------------
    1.58 +This means that there is already a process listening on a port,
    1.59 +usually 25. You either have another MTA running in background
    1.60 +(sendmail, exim, etc...) or another instance of masqmail.
    1.61 +
    1.62 +It may also mean that the ports you configured MM to listen to
    1.63 +(with 'listen_addresses') are on the same IP address, eg. you may
    1.64 +have set your hostname to 127.0.0.1 and try to listen on localhost
    1.65 +and your host name. In this case either set your hostname to
    1.66 +another IP address or delete one of the conflicting entries.
    1.67 +
    1.68 +
    1.69 +My friends told me that they do not see my full name in their
    1.70 +inbox, although it is configured in my mail client.
    1.71 +-------------------------------------------------------------
    1.72 +You probably used the map_h_from_addresses feature in the route
    1.73 +configuration and forgot to set your real name. The syntax is:
    1.74 +
    1.75 +map_h_from_addresses = "charlie:Charlie Miller <cmiller@foo.com>";
    1.76 +
    1.77 +Do not forget the Charlie Miller.
    1.78 +
    1.79 +
    1.80 +With connection method file, I get the following message in
    1.81 +the log file: "Could not open /tmp/connect_route: Permission
    1.82 +denied".
    1.83 +------------------------------------------------------------
    1.84 +In your ip-up script, you have to set read permission to the user
    1.85 +masqmail runs as. After you write the file with the connection
    1.86 +name, set read permission to all with chmod ugo+r file.
    1.87 +
    1.88 +
    1.89 +With connection method file, I get the following message in
    1.90 +the log file: "route with name name not found.".
    1.91 +-----------------------------------------------------------
    1.92 +Check whether the name in the file is really identical to name you
    1.93 +gave to the route configuration (case sensitive!).
    1.94 +
    1.95 +
    1.96 +I found a bug.
    1.97 +--------------
    1.98 +Make sure you are using the newest version, in case of doubt
    1.99 +search it in freshmeat. If you do, tell me. See also the section
   1.100 +bugs on the main page.
   1.101 +
   1.102 +
   1.103 +I think I found a bug, but I am not sure whether I configured
   1.104 +MasqMail incorrectly.
   1.105 +-------------------------------------------------------------
   1.106 +Don't care. Tell me. Or write to the mailing list.
   1.107 +
   1.108 +
   1.109 +
   1.110 +Written by Oliver Kurth
   1.111 +Last modified by him: Tue May 30 15:19:56 CEST 2000