From: Reiner Steib <reinersteib+gmane@imap.cc>
To: emacs-devel@gnu.org, ding@gnus.org
Subject: POP3 UIDL - pop3-leave-mail-on-server (was: [PATCH] GnuTLS support on Woe32)
Date: Thu, 10 Mar 2011 09:54:39 +0100 [thread overview]
Message-ID: <87lj0ne4og.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3hbbcm128.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 09 Mar 2011 22:33:19 +0100")
On Wed, Mar 09 2011, Lars Magne Ingebrigtsen wrote:
> claudio.bley@gmail.com (Claudio Bley) writes:
[...]
>> It retrieves unique message IDs and is pretty vital in implementing
>> leave-messages-on-server support for POP3 (which I require).
>
> I didn't know that was actually possible. Do many people use that?
It has been requested quite often. See the comments around
`pop3-leave-mail-on-server'...
,----[ gnus/lisp/pop3.el ]
| (defcustom pop3-leave-mail-on-server nil
| "*Non-nil if the mail is to be left on the POP server after fetching.
|
| If `pop3-leave-mail-on-server' is non-nil the mail is to be left
| on the POP server after fetching. Note that POP servers maintain
| no state information between sessions, so what the client
| believes is there and what is actually there may not match up.
| If they do not, then you may get duplicate mails or the whole
| thing can fall apart and leave you with a corrupt mailbox."
| ;; We can't use the UILD support from XEmacs mail-lib or cvs.m17n.org:
| ;; http://thread.gmane.org/v9lld8fml4.fsf@marauder.physik.uni-ulm.de
| ;; http://thread.gmane.org/b9yy8hzy9ej.fsf@jpl.org
| ;; Any volunteer to re-implement this?
| :version "22.1" ;; Oort Gnus
| :type 'boolean
| :group 'pop3)
`----
BTW, I don't know why you removed the corresponding warnings from
`pop3-movemail' with this commit:
,----[ git log - gnus/lisp/pop3.el ]
| commit 119a867afc587c9261730362a6478fc3801df1b5
| Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
| Date: Thu Sep 9 16:06:38 2010 +0200
|
| Remove pop3-movemail and rename pop3-streaming-movemail to pop3-movemail.
`----
> And why not just use IMAP instead?
Some mail providers don't offer IMAP (for free).
> If it's a popular way to read email, I can certainly have a peek at
> implementing an nnpop backend for Gnus...
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2011-03-10 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ipvwl1nx.wl%claudio.bley@gmail.com>
[not found] ` <m3fwqyanyn.fsf@quimbies.gnus.org>
[not found] ` <87hbbewr7o.wl%claudio.bley@gmail.com>
[not found] ` <m3mxl6otuo.fsf@quimbies.gnus.org>
[not found] ` <87ei6g0yph.wl%claudio.bley@gmail.com>
[not found] ` <m3hbbcm128.fsf@quimbies.gnus.org>
2011-03-10 8:54 ` Reiner Steib [this message]
2011-03-15 16:08 ` POP3 UIDL - pop3-leave-mail-on-server Lars Magne Ingebrigtsen
2011-03-15 17:49 ` chad
2011-03-15 20:54 ` Eric S Fraga
2011-03-15 21:16 ` Lars Magne Ingebrigtsen
2011-03-16 14:30 ` Eric S Fraga
2011-03-16 17:29 ` Lars Magne Ingebrigtsen
2011-03-16 18:51 ` Eric S Fraga
2012-10-01 11:36 ` Katsumi Yamaoka
2012-10-05 9:38 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lj0ne4og.fsf_-_@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).