diff options
Diffstat (limited to 'fetchmail.man')
| -rw-r--r-- | fetchmail.man | 40 |
1 files changed, 18 insertions, 22 deletions
diff --git a/fetchmail.man b/fetchmail.man index c7017595..7c9f35e2 100644 --- a/fetchmail.man +++ b/fetchmail.man @@ -416,7 +416,7 @@ the mailserver user name in the entry. A single local name can be used to support redirecting your mail when your username on the client machine is different from your name on the mailserver. When there is only a single local name, mail is forwarded -to that username regardless of the message's To, Cc, and Bcc headers. +to that local username regardless of the message's To, Cc, and Bcc headers. .PP When there is more than one local name (or name mapping) the \fIfetchmail\fR code does look at the To, Cc, and Bcc headers of @@ -579,6 +579,17 @@ server user names `golux', `hurkle', and `snark'. It further specifies that `golux' and `snark' have the same name on the client as on the server, but mail for server user `hurkle' should be delivered to client user `happy'. +.PP +Local names can also be used to administer a mailing list from the +client side of a \fIfetchmail\fR collection. Suppose your name is +\&`esr', and you want to both pick up your own mail and maintain a mailing +list called (say) "fetchmail-friends", and you want to keep the alias +list on your client machine. On your server, you can alias +\&`fetchmail-friends' to `esr'; then, in your \fI.fetchmailrc\fR, declare +\&`to esr fetchmail-friends here'. Then, when mail including `fetchmail' +in any of its recipient lines line gets fetched, the alias will be +appended to the list of recipients your SMTP listener sees. Therefore +it will undergo alias expansion locally. .SH EXIT CODES To facilitate the use of .I fetchmail @@ -625,19 +636,6 @@ When .I fetchmail queries more than one host, the returned status is that of the last host queried. -.SH NOTE -Multiple local names can be used to support forwarding from a -"multi-drop" mailbox accumulating mail on the server for several -client-machine users. Local names can also be used to administer a -mailing list from the client side of a \fIfetchmail\fR collection. -Suppose your name is `esr', and you maintain a mailing list called -(say) "fetchmail-friends", and you want to keep the alias list on your -client machine. On your server, you can alias fetchmail-friends to -esr; then, in your \fI.fetchmailrc\fR, declare `to esr -fetchmail-friends here'. Then, when mail including that alias in any -of its recpient lines line gets fetched, the alias will be appended to -the list of recipients your SMTP listener sees. Therefore it will -undergo alias expansion locally. .SH AUTHORS .I fetchmail was originated (under the name `popclient') by Carl Harris at Virginia @@ -683,14 +681,12 @@ might be snaffled with a packet sniffer or more sophisticated monitoring software. .PP Retrieval and forwarding from multi-drop server mailboxes is at most -as reliable as your mail server host's DNS service. Each host -address part in each message of a multi-drop mailbox is checked -with -.BR gethostbyname (2) -to see if it's an alias of the mail server. If it is, but the -lookup fails due to network congestion or a crashed server, forwarding -will not get done correctly. Note: this check will \fInot\fR catch -equivalences created by MX records! +as reliable as your mail server host's DNS service. Each host address +part in each message of a multi-drop mailbox is looked up through DNS +to see if it's an alias of the mail server. If it is, but the lookup +fails due to network congestion or a crashed server, forwarding will +not get done correctly. Yes, this check \fIwill\fR catch equivalences +created by MX records! .PP The multi-drop mailbox code was hard to test thoroughly and may have obscure failure modes, especially in the presence of DNS flakiness. |