masqmail

annotate docs/old-manual/faq.html @ 75:257a9e6d1a8e

find changesets by author, revision, files, or words in the commit message
fixed correct processing of mails with data lines longer 4096 chars Mail messages with lines longer than 4096 chars were already read correctly, i.e. the spool files were correct. This commit fixes the reading of spool files with long lines. The old behavior was that the message body was truncated right before the first line longer 4096 chars. The number comes from MAX_DATALINE.
author meillo@marmaro.de
date Wed, 16 Jun 2010 19:06:34 +0200
parents
children
rev   line source
meillo@56 1 <HTML>
meillo@56 2 <HEAD>
meillo@56 3 <TITLE>MasqMail - Manual
meillo@56 4 </TITLE>
meillo@56 5 </HEAD>
meillo@56 6 <BODY TEXT="#000000" LINK="#0000ff" BGCOLOR="#ffffff">
meillo@56 7
meillo@56 8 <center>
meillo@56 9 <table width="80%">
meillo@56 10 <tr><td>
meillo@56 11 <table width="100%" bgcolor="#0000aa" cellspacing=0 cellpadding=0>
meillo@56 12 <tr>
meillo@56 13 <td>
meillo@56 14 <a href="manual.html">
meillo@56 15 <img width="20" src = "../images/u_arrow.gif" alt = "manual">
meillo@56 16 </a>
meillo@56 17 </td>
meillo@56 18 <td align=center width="100%"><font size="6" color = "#ffffff">Frequently Asked Questions</font></td>
meillo@56 19 <td>
meillo@56 20 <a href="./config.html">
meillo@56 21 <img width="20" src = "../images/l_arrow.gif" alt = "Configuration">
meillo@56 22 </a>
meillo@56 23 </td>
meillo@56 24 </tr>
meillo@56 25 </table>
meillo@56 26
meillo@56 27
meillo@56 28 Some of these questions were never asked, but I thought they will be
meillo@56 29 some time. Some <em>were</em> asked.
meillo@56 30
meillo@56 31 <h4>General Questions</h4>
meillo@56 32 <ul>
meillo@56 33 <li><a href="#1_0">1.0: When do I need MasqMail?</a></li>
meillo@56 34 <li><a href="#1_1">1.1: When do I <em>not</em> need MasqMail?</a></li>
meillo@56 35 <li><a href="#1_2">1.2: Can I retrieve mail with MasqMail?</a></li>
meillo@56 36 <li><a href="#1_3">1.3: Is there a mailing list for MasqMail?</a></li>
meillo@56 37 </ul>
meillo@56 38
meillo@56 39 <h4>Setup</h4>
meillo@56 40 <ul>
meillo@56 41 <li><a href="#2_0">2.0: After starting masmail, I get the following
meillo@56 42 message: "could not gain root privileges. Is the setuid bit set?"</a></li>
meillo@56 43 <li><a href="#2_1">2.1: After starting masmail, I get the following
meillo@56 44 message: "bind: (terminating): Address already in use"</a></li>
meillo@56 45 </ul>
meillo@56 46
meillo@56 47 <h4>Header Rewriting</h4>
meillo@56 48 <ul>
meillo@56 49 <li><a href="#3_0">3.0: My friends told me that they do not see my
meillo@56 50 full name in their inbox, although it is configured in my mail
meillo@56 51 client.</a></li>
meillo@56 52 </ul>
meillo@56 53
meillo@56 54 <h4>Delivering Online</h4>
meillo@56 55 <ul>
meillo@56 56 <li><a href="#4_0">4.0: With connection methed <em>file</em>, I get the following message in the log file: "Could not open /tmp/connect_route: Permission denied".</a></li>
meillo@56 57 <li><a href="#4_1">4.1: With connection methed <em>file</em>, I get the following message in the log file: "route with name <em>name</em> not found.".</a></li>
meillo@56 58 </ul>
meillo@56 59
meillo@56 60 <h4>Bugs</h4>
meillo@56 61 <ul>
meillo@56 62 <li><a href="#5_0">5.0: I found a bug.</a></li>
meillo@56 63 <li><a href="#5_1">5.1: I think I found a bug, but I am not sure whether I configured MasqMail incorrectly.</a></li>
meillo@56 64 </ul>
meillo@56 65
meillo@56 66 <a name="1_0"> <h4>1.0: When do I need MasqMail?</h4></a>
meillo@56 67
meillo@56 68 <p> You do not <em>need</em> it. But it makes sending mails via a
meillo@56 69 dialup connection a lot easier.</p>
meillo@56 70
meillo@56 71 <p>It is useful if you dial to the internet from time to time via a
meillo@56 72 modem and connect to different providers, each one with a different
meillo@56 73 configuration. Other MTAs are not flexible enough if you have to send
meillo@56 74 mails via different mail servers for each provider. With MasqMail you
meillo@56 75 can configure a different one for each provider and even set your
meillo@56 76 return addresses differently.</p>
meillo@56 77
meillo@56 78 <p>It is also useful if you have a LAN with a gateway which is
meillo@56 79 connected to the internet via a modem because you can rewrite your
meillo@56 80 address depending on whether the recipients are <em>inside</em> or
meillo@56 81 <em>outside</em> your LAN. So responses and delivery failures on your
meillo@56 82 LAN will be sent to you without leaving it, while those outside will
meillo@56 83 be delivered to your address outside. (But it does not yet send
meillo@56 84 delivery failures itself yet.)</p>
meillo@56 85
meillo@56 86 <p>MasqMail is also often used on notebooks.</p>
meillo@56 87
meillo@56 88 <a name="1_1"><h4>1.1: When do I <em>not</em> need MasqMail?</h4></a>
meillo@56 89
meillo@56 90 <p>The use of MasqMail is <em>strongly</em> discouraged if you have a
meillo@56 91 permanent connection to the internet without a firewall. First because
meillo@56 92 it does not have the ability to block relaying (it relays every mail)
meillo@56 93 and second because there are no capabilities to protect against
meillo@56 94 SPAM. You will not take advantages of its features anyway.</p>
meillo@56 95
meillo@56 96 <a name="1_2"><h4>1.2: Can I retrieve mail with MasqMail?</h4></a>
meillo@56 97
meillo@56 98 <p>Yes, for version >= 0.1.0 you can retrieve mail via the POP3 and
meillo@56 99 APOP protocol from single drop mailboxes (in case you do not know
meillo@56 100 about single/mutidrop, you probaby use single drop mailboxes).</p>
meillo@56 101
meillo@56 102 <p>You can also use fetchmail or other pop/imap clients to feed
meillo@56 103 it.</p>
meillo@56 104
meillo@56 105 <a name="1_3"><h4>1.3: Is there a mailing list for MasqMail?</h4></a>
meillo@56 106
meillo@56 107 <p>Yes, there is! See <a href="http://www.innominate.org/mailman/listinfo/masqmail">here</a>.</p>
meillo@56 108
meillo@56 109 <a name="2_0"><h4>2.0: After starting masmail, I get the following
meillo@56 110 message: "could not gain root privileges. Is the setuid bit set?"</h4></a>
meillo@56 111
meillo@56 112 <p>Set the set-user-id-bit with chmod u+s /usr/sbin/masqmail.</p>
meillo@56 113
meillo@56 114 <a name="2_1"><h4>2.1: After starting masmail, I get the following
meillo@56 115 message: "bind: (terminating): Address already in use"</h4></a>
meillo@56 116
meillo@56 117 <p>This means that there is already a process listening on a port,
meillo@56 118 usually 25. You either have another MTA running in background
meillo@56 119 (sendmail, exim, etc...) or another instance of masqmail.</p>
meillo@56 120
meillo@56 121 <p>It may also mean that the ports you configured MM to listen to
meillo@56 122 (with 'listen_addresses') are on the same IP address, eg. you may have
meillo@56 123 set your hostname to 127.0.0.1 and try to listen on localhost and your
meillo@56 124 host name. In this case either set your hostname to another IP address
meillo@56 125 or delete one of the conflicting entries.</p>
meillo@56 126
meillo@56 127 <a name="3_0"><h4>3.0: My friends told me that they do not see my full
meillo@56 128 name in their inbox, although it is configured in my mail
meillo@56 129 client.</h4></a>
meillo@56 130
meillo@56 131 <p>You probably used the <b>map_h_from_addresses</b> feature in the
meillo@56 132 route configuration and forgot to set your real name. The syntax
meillo@56 133 is:</p>
meillo@56 134
meillo@56 135 <pre>
meillo@56 136 map_h_from_addresses = "charlie:Charlie Miller &lt;cmiller@foo.com&gt";
meillo@56 137 </pre>
meillo@56 138
meillo@56 139 <p>Do not forget the <em>Charlie Miller</em>.</p>
meillo@56 140
meillo@56 141 <a name="4_0"><h4>4.0: With connection method <em>file</em>, I get the
meillo@56 142 following message in the log file: "Could not open /tmp/connect_route:
meillo@56 143 Permission denied".</h4></a>
meillo@56 144
meillo@56 145 <p>In your ip-up script, you have to set read permission to the user
meillo@56 146 masqmail runs as. After you write the file with the connection name,
meillo@56 147 set read permission to all with chmod ugo+r <em>file</em>.
meillo@56 148
meillo@56 149 <a name="4_1"><h4>4.1: With connection methed <em>file</em>, I get the
meillo@56 150 following message in the log file: "route with name <em>name</em> not
meillo@56 151 found.".</h4></a>
meillo@56 152
meillo@56 153 <p>Check whether the name in the file is really identical to name you
meillo@56 154 gave to the route configuration (case sensitive!). Maybe there is a
meillo@56 155 linefeed after the name in the file. Write it with echo -n.</p>
meillo@56 156
meillo@56 157 <a name="5_0"><h4>5.0: I found a bug.</h4></a>
meillo@56 158
meillo@56 159 <p>Make sure you are using the newest version, in case of doubt search
meillo@56 160 it in <a href="http://www.freshmeat.net">freshmeat</a>. If you do, tell
meillo@56 161 <a href = "mailto:Oliver Kurth <kurth@innominate.de>">me</a>. See
meillo@56 162 also the section <a href="index.html#bugs">bugs</a> on the <a
meillo@56 163 href="index.html">main</a> page.</p>
meillo@56 164
meillo@56 165 <a name="5_1"><h4>5.1: I think I found a bug, but I am not sure
meillo@56 166 whether I configured MasqMail incorrectly.</h4></a>
meillo@56 167
meillo@56 168 <p>Don't care. Tell <a href = "mailto:Oliver Kurth
meillo@56 169 <kurth@innominate.de>">me</a>. Or write to the <a
meillo@56 170 href="http://www.innominate.org/mailman/listinfo/masqmail">mailing
meillo@56 171 list</a>.</p>
meillo@56 172
meillo@56 173 </td></tr>
meillo@56 174
meillo@56 175 <tr><td>
meillo@56 176 <p>
meillo@56 177 <hr>
meillo@56 178 <address><a href = "mailto:kurth@innominate.de">Oliver Kurth</a></address>
meillo@56 179 Last modified: Tue May 30 15:19:56 CEST 2000
meillo@56 180 <br>
meillo@56 181 This page was created using <a href="http://www.freddyfrog.com/hacks/genpage/">Genpage</a> - Version: 1.0.6
meillo@56 182 </p>
meillo@56 183
meillo@56 184 </table>
meillo@56 185 </center>
meillo@56 186
meillo@56 187 </BODY>
meillo@56 188 </HEAD>
meillo@56 189