diff options
| author | Katsumi Yamaoka | 2013-03-07 10:24:23 +0000 |
|---|---|---|
| committer | Katsumi Yamaoka | 2013-03-07 10:24:23 +0000 |
| commit | 3cd23a35e7c7319125303c5513c01bbc57b7f6dd (patch) | |
| tree | 680f97c23268099626e17d342382d1412b822548 /doc | |
| parent | 86c86abfecfd3e6f41dbacfd9b349011aee85ad1 (diff) | |
| download | emacs-3cd23a35e7c7319125303c5513c01bbc57b7f6dd.tar.gz emacs-3cd23a35e7c7319125303c5513c01bbc57b7f6dd.zip | |
doc/misc/gnus-faq.texi (FAQ 3-11): Now Gnus supports POP3 UIDL
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/misc/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/misc/gnus-faq.texi | 29 |
2 files changed, 7 insertions, 26 deletions
diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog index 3a3ed4623d1..12230bfb374 100644 --- a/doc/misc/ChangeLog +++ b/doc/misc/ChangeLog | |||
| @@ -1,3 +1,7 @@ | |||
| 1 | 2013-03-07 Katsumi Yamaoka <yamaoka@jpl.org> | ||
| 2 | |||
| 3 | * gnus-faq.texi (FAQ 3-11): Now Gnus supports POP3 UIDL. | ||
| 4 | |||
| 1 | 2013-03-06 Alan Mackenzie <acm@muc.de> | 5 | 2013-03-06 Alan Mackenzie <acm@muc.de> |
| 2 | 6 | ||
| 3 | * cc-mode.texi (Custom Line-Up): Clarify position of point on | 7 | * cc-mode.texi (Custom Line-Up): Clarify position of point on |
diff --git a/doc/misc/gnus-faq.texi b/doc/misc/gnus-faq.texi index ede957a5c35..cb900626670 100644 --- a/doc/misc/gnus-faq.texi +++ b/doc/misc/gnus-faq.texi | |||
| @@ -705,32 +705,9 @@ retrieves via POP3? | |||
| 705 | 705 | ||
| 706 | @subsubheading Answer | 706 | @subsubheading Answer |
| 707 | 707 | ||
| 708 | First of all, that's not the way POP3 is intended to work, | 708 | Yes, if the POP3 server supports the UIDL control (maybe almost servers |
| 709 | if you have the possibility, you should use the IMAP | 709 | do it nowadays). To do that, add a @code{:leave VALUE} pair to each |
| 710 | Protocol if you want your messages to stay on the | 710 | POP3 mail source. See @pxref{Mail Source Specifiers} for VALUE. |
| 711 | server. Nevertheless there might be situations where you | ||
| 712 | need the feature, but sadly Gnus itself has no predefined | ||
| 713 | functionality to do so. | ||
| 714 | |||
| 715 | However this is Gnus county so there are possibilities to | ||
| 716 | achieve what you want. The easiest way is to get an external | ||
| 717 | program which retrieves copies of the mail and stores them | ||
| 718 | on disk, so Gnus can read it from there. On Unix systems you | ||
| 719 | could use, e.g., fetchmail for this, on MS Windows you can use | ||
| 720 | Hamster, an excellent local news and mail server. | ||
| 721 | |||
| 722 | The other solution would be, to replace the method Gnus | ||
| 723 | uses to get mail from POP3 servers by one which is capable | ||
| 724 | of leaving the mail on the server. If you use XEmacs, get | ||
| 725 | the package mail-lib, it includes an enhanced pop3.el, | ||
| 726 | look in the file, there's documentation on how to tell | ||
| 727 | Gnus to use it and not to delete the retrieved mail. For | ||
| 728 | GNU Emacs look for the file epop3.el which can do the same | ||
| 729 | (If you know the home of this file, please send me an | ||
| 730 | e-mail). You can also tell Gnus to use an external program | ||
| 731 | (e.g., fetchmail) to fetch your mail, see the info node | ||
| 732 | "Mail Source Specifiers" in the Gnus manual on how to do | ||
| 733 | it. | ||
| 734 | 711 | ||
| 735 | @node FAQ 4 - Reading messages | 712 | @node FAQ 4 - Reading messages |
| 736 | @subsection Reading messages | 713 | @subsection Reading messages |