[fetchmail]fetchmail only skipping seen messages when there are
no unseen ones on imap
Christian Uebber
briefkasten@uebber.de
Sat, 05 Mar 2005 19:25:37 +0100
This is a multi-part message in MIME format.
--------------010609060002030404010100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Rob MacGregor schrieb:
>On Sat, 05 Mar 2005 19:02:44 +0100, Christian Uebber
><briefkasten@uebber.de> wrote:
>
>
>>UIDL shoudn't be needed for imap, since imap implements server side
>>tracking of seen states.
>>
>>
>
>Should have remembered that.
>
>However, that probably means that the problem is with 1&1 having a
>broken IMAP server (which doesn't surprise me, given how badly broken
>their envelope-to headers are).
>
>
Using Mulberry and Pine, the most comprehensive IMAP client-side
implementations I know of, I can't find any flaws; seen flagging works fine.
>I'm using the UIDL support against a POP3 box in a similar situation
>and have had no problems with it in the last 2 years. Maybe it's
>worth seeing if moving to POP3 solves your problem?
>
>
>
Yes, POP3 does indeed work. I'm wondering myself, too. I've never had
any trouble using fetchmail. I now prefer IMAP over POP3 since 1&1
supports IDLE. Using IDLE you don't need polling anymore, the IMAP
server informs one of new mail via a halted connection. I left this out
of my posting because the problem occurs with and without toggling IDLE
in fetchmailrc
I'm going to give the Berlios list a try...
--------------010609060002030404010100
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rob MacGregor schrieb:
<blockquote cite="mid43ea8d07050305101163e710f2@mail.gmail.com"
type="cite">
<pre wrap="">On Sat, 05 Mar 2005 19:02:44 +0100, Christian Uebber
<a class="moz-txt-link-rfc2396E" href="mailto:briefkasten@uebber.de"><briefkasten@uebber.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">UIDL shoudn't be needed for imap, since imap implements server side
tracking of seen states.
</pre>
</blockquote>
<pre wrap=""><!---->
Should have remembered that.
However, that probably means that the problem is with 1&1 having a
broken IMAP server (which doesn't surprise me, given how badly broken
their envelope-to headers are).
</pre>
</blockquote>
Using Mulberry and Pine, the most comprehensive IMAP client-side
implementations I know of, I can't find any flaws; seen flagging works
fine.<br>
<blockquote cite="mid43ea8d07050305101163e710f2@mail.gmail.com"
type="cite">
<pre wrap="">
I'm using the UIDL support against a POP3 box in a similar situation
and have had no problems with it in the last 2 years. Maybe it's
worth seeing if moving to POP3 solves your problem?
</pre>
</blockquote>
Yes, POP3 does indeed work. I'm wondering myself, too. I've never had
any trouble using fetchmail. I now prefer IMAP over POP3 since 1&1
supports IDLE. Using IDLE you don't need polling anymore, the IMAP
server informs one of new mail via a halted connection. I left this out
of my posting because the problem occurs with and without toggling IDLE
in fetchmailrc<br>
<br>
I'm going to give the Berlios list a try...<br>
</body>
</html>
--------------010609060002030404010100--