You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
(24) |
Nov
(14) |
Dec
|
|
From: Lars T. <ls...@gm...> - 2006-05-15 18:46:27
|
Hello Matthias, Matthias Andree wrote: > Lars Tewes <ls...@gm...> writes: > >> Using fetchmail successfully with polling by interval for several months >> I just tried to use the IMAP idle-extension to get my mails delivered >> immediately. >> >> Unfortunately only one message gets fetched - after that, fetchmail >> recognizes the arrival of a new one, but instead of downloading the >> message, it just triggers another idle. > > Does the attached patch help? > Index: imap.c > =================================================================== > --- imap.c (Revision 4840) > +++ imap.c (Arbeitskopie) > @@ -679,7 +679,7 @@ I'm quite impressed by this quick solution - it works! Well, mostly. Working transfer: --------------------------------------------------------------------- lsr@lsr# /usr/bin/fetchmail -v -v fetchmail: 6.3.4 querying imap.strato.de (protocol IMAP) at Mon 15 May 2006 06:28:17 PM CEST: poll started fetchmail: IMAP< * OK IMAP server ready fetchmail: IMAP> A0001 CAPABILITY fetchmail: IMAP< * CAPABILITY IDLE IMAP4rev1 AUTH=CRAM-MD5 SORT QUOTA NAMESPACE fetchmail: IMAP< A0001 OK CAPABILITY completed fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: will idle after poll fetchmail: IMAP> A0002 AUTHENTICATE CRAM-MD5 fetchmail: IMAP< + PDQ3NzYuMjI1NDUuMTE0NzcxMDQ5NUBwb3N0LndlYm1haWxlci5kZT4= fetchmail: decoded as <477...@po...> fetchmail: IMAP> bHNyQHZpZXctc291cmNlLmRlIDEwZmJjOGY4ZmMzYjJiNDQ3N2I4YjUzYzE1NzYzZmJi fetchmail: IMAP< A0002 OK LOGIN completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0003 SELECT "INBOX" fetchmail: IMAP< * 0 EXISTS fetchmail: IMAP< * 0 RECENT fetchmail: IMAP< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded) fetchmail: IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded)] Permanent flags fetchmail: IMAP< * OK [UIDVALIDITY 1116049368] UIDVALIDITY value fetchmail: IMAP< * OK [UIDNEXT 3273] may be the next UID value fetchmail: IMAP< A0003 OK [READ-WRITE] SELECT completed fetchmail: 0 messages waiting after first poll fetchmail: IMAP> A0004 IDLE fetchmail: IMAP< + will notify you of all changes [sending first mail now...] fetchmail: IMAP< * 1 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0004 OK IDLE completed fetchmail: 1 message waiting after re-poll fetchmail: IMAP> A0005 SEARCH UNSEEN NOT DELETED fetchmail: IMAP< * SEARCH 1 fetchmail: 1 is unseen fetchmail: IMAP< A0005 OK SEARCH completed fetchmail: 1 is first unseen 1 message for ls...@vi... at imap.strato.de. fetchmail: IMAP> A0006 FETCH 1 RFC822.SIZE fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 900) fetchmail: IMAP< A0006 OK Fetch complete fetchmail: IMAP> A0007 FETCH 1 RFC822.HEADER fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {895} reading message ls...@vi...@imap.rzone.de:1 of 1 (895 header octets) About to rewrite From: Lars Tewes <ls...@gm...> Rewritten version is From: Lars Tewes <ls...@gm...> About to rewrite To: Lars Tewes <ls...@vi...> Rewritten version is To: Lars Tewes <ls...@vi...> fetchmail: about to deliver with: /usr/bin/procmail -d 'lsr' # fetchmail: IMAP< ) fetchmail: IMAP< A0007 OK Fetch complete fetchmail: IMAP> A0008 FETCH 1 BODY.PEEK[TEXT] fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {5} (5 body octets) * fetchmail: IMAP< ) fetchmail: IMAP< A0008 OK Fetch complete flushed fetchmail: IMAP> A0009 STORE 1 +FLAGS (\Seen \Deleted) fetchmail: IMAP< * 1 FETCH (FLAGS (\Deleted \Seen \Recent)) fetchmail: IMAP< A0009 OK STORE completed fetchmail: IMAP> A0010 EXPUNGE fetchmail: IMAP< * 1 EXPUNGE fetchmail: IMAP< A0010 OK EXPUNGE completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0011 IDLE fetchmail: IMAP< + will notify you of all changes [sending second mail now...] fetchmail: IMAP< * 1 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0011 OK IDLE completed fetchmail: 1 message waiting after re-poll fetchmail: IMAP> A0012 SEARCH UNSEEN NOT DELETED fetchmail: IMAP< * SEARCH 1 fetchmail: 1 is unseen fetchmail: IMAP< A0012 OK SEARCH completed fetchmail: 1 is first unseen 1 message for ls...@vi... at imap.strato.de. fetchmail: IMAP> A0013 FETCH 1 RFC822.SIZE fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 896) fetchmail: IMAP< A0013 OK Fetch complete fetchmail: IMAP> A0014 FETCH 1 RFC822.HEADER fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {896} reading message ls...@vi...@imap.rzone.de:1 of 1 (896 header octets) About to rewrite From: Lars Tewes <ls...@gm...> Rewritten version is From: Lars Tewes <ls...@gm...> About to rewrite To: Lars Tewes <ls...@vi...> Rewritten version is To: Lars Tewes <ls...@vi...> fetchmail: about to deliver with: /usr/bin/procmail -d 'lsr' # fetchmail: IMAP< ) fetchmail: IMAP< A0014 OK Fetch complete fetchmail: IMAP> A0015 FETCH 1 BODY.PEEK[TEXT] fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {0} (0 body octets) fetchmail: IMAP< ) fetchmail: IMAP< A0015 OK Fetch complete flushed fetchmail: IMAP> A0016 STORE 1 +FLAGS (\Seen \Deleted) fetchmail: IMAP< * 1 FETCH (FLAGS (\Deleted \Seen \Recent)) fetchmail: IMAP< A0016 OK STORE completed fetchmail: IMAP> A0017 EXPUNGE fetchmail: IMAP< * 1 EXPUNGE fetchmail: IMAP< A0017 OK EXPUNGE completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0018 IDLE fetchmail: IMAP< + will notify you of all changes [works!] --------------------------------------------------------------------- But if I try to not to expunge the messages on the server after the transfer (using "keep" configuration option), fetchmail immediately terminates after fetching the first message. Don't know if this is intended behaviour? --------------------------------------------------------------------- Logfile with "keep" option set: lsr@lsr# /usr/bin/fetchmail -v -v fetchmail: 6.3.4 querying imap.strato.de (protocol IMAP) at Mon 15 May 2006 06:35:00 PM CEST: poll started fetchmail: IMAP< * OK IMAP server ready fetchmail: IMAP> A0001 CAPABILITY fetchmail: IMAP< * CAPABILITY IDLE IMAP4rev1 AUTH=CRAM-MD5 SORT QUOTA NAMESPACE fetchmail: IMAP< A0001 OK CAPABILITY completed fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: will idle after poll fetchmail: IMAP> A0002 AUTHENTICATE CRAM-MD5 fetchmail: IMAP< + PDQ4MDIuMjI1NjkuMTE0NzcxMDg5OUBwb3N0LndlYm1haWxlci5kZT4= fetchmail: decoded as <480...@po...> fetchmail: IMAP> bHNyQHZpZXctc291cmNlLmRlIGQxMGM5ZjMzMDQwNjYxNTRmOTY0OTkxNTk2Nzk3NzJi fetchmail: IMAP< A0002 OK LOGIN completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0003 SELECT "INBOX" fetchmail: IMAP< * 0 EXISTS fetchmail: IMAP< * 0 RECENT fetchmail: IMAP< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded) fetchmail: IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded)] Permanent flags fetchmail: IMAP< * OK [UIDVALIDITY 1116049368] UIDVALIDITY value fetchmail: IMAP< * OK [UIDNEXT 3276] may be the next UID value fetchmail: IMAP< A0003 OK [READ-WRITE] SELECT completed fetchmail: 0 messages waiting after first poll fetchmail: IMAP> A0004 IDLE fetchmail: IMAP< + will notify you of all changes [sending first mail now...] fetchmail: IMAP< * 1 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0004 OK IDLE completed fetchmail: 1 message waiting after re-poll fetchmail: IMAP> A0005 SEARCH UNSEEN NOT DELETED fetchmail: IMAP< * SEARCH 1 fetchmail: 1 is unseen fetchmail: IMAP< A0005 OK SEARCH completed fetchmail: 1 is first unseen 1 message for ls...@vi... at imap.strato.de. fetchmail: IMAP> A0006 FETCH 1 RFC822.SIZE fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 709) fetchmail: IMAP< A0006 OK Fetch complete fetchmail: IMAP> A0007 FETCH 1 RFC822.HEADER fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {704} reading message ls...@vi...@imap.rzone.de:1 of 1 (704 header octets) About to rewrite From: Lars Tewes <ls...@gm...> Rewritten version is From: Lars Tewes <ls...@gm...> About to rewrite To: Lars Tewes <ls...@vi...> Rewritten version is To: Lars Tewes <ls...@vi...> fetchmail: about to deliver with: /usr/bin/procmail -d 'lsr' # fetchmail: IMAP< ) fetchmail: IMAP< A0007 OK Fetch complete fetchmail: IMAP> A0008 FETCH 1 BODY.PEEK[TEXT] fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {5} (5 body octets) * fetchmail: IMAP< ) fetchmail: IMAP< A0008 OK Fetch complete not flushed fetchmail: IMAP> A0009 STORE 1 +FLAGS (\Seen) fetchmail: IMAP< * 1 FETCH (FLAGS (\Seen \Recent)) fetchmail: IMAP< A0009 OK STORE completed fetchmail: IMAP> A0010 LOGOUT fetchmail: IMAP< * BYE fetchmail: IMAP< A0010 OK LOGOUT completed fetchmail: 6.3.4 querying imap.strato.de (protocol IMAP) at Mon 15 May 2006 06:35:28 PM CEST: poll completed fetchmail: not swapping UID lists, no UIDs seen this query fetchmail: Writing fetchids file. fetchmail: normal termination, status 0 fetchmail: Writing fetchids file. --------------------------------------------------------------------- Thanks a lot for the patch! Best, Lars |
|
From: Matthias A. <mat...@gm...> - 2006-05-15 18:06:59
|
Lars Tewes <ls...@gm...> writes: > Using fetchmail successfully with polling by interval for several months > I just tried to use the IMAP idle-extension to get my mails delivered > immediately. > > Unfortunately only one message gets fetched - after that, fetchmail > recognizes the arrival of a new one, but instead of downloading the > message, it just triggers another idle. Does the attached patch help? -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2006-05-15 16:33:35
|
Lars Tewes <ls...@gm...> writes: > Unfortunately only one message gets fetched - after that, fetchmail > recognizes the arrival of a new one, but instead of downloading the > message, it just triggers another idle. Looks like an incompatibility with fetchmail's IDLE code: when the server doesn't send "* n RECENT" during idle, fetchmail doesn't actually detect the new message, but just re-issues the IDLE command. I'll see how the code works and see to a fix. -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2006-05-12 17:57:17
|
"Balaji Krishnamoorthy" <ba...@ti...> writes: > I have fetchmail setup running to pull messages from the IMAP server > using procmail as the mda. I use mozilla as the mail client and use > procmail+fetchmail to run some scripts. I wish fetchmail should not mark > the messages as "read" after downloading them as my mozilla email client > doesn't recognize the new messages as unread. > > Is there a option to specify in .fetchmailrc to mark the messages > "unread" in the server as I can view them as usual in the mozilla. Unfortunately not yet, because fetchmail cannot use IMAP's UID feature yet (it knows POP3's UIDL however). So if you can pull with POP3, that might be a workaround. -- Matthias Andree |
|
From: Rob M. <rob...@gm...> - 2006-05-12 17:36:43
|
On 5/12/06, Balaji Krishnamoorthy <ba...@ti...> wrote:
>
> I have fetchmail setup running to pull messages from the IMAP server
> using procmail as the mda. I use mozilla as the mail client and use
> procmail+fetchmail to run some scripts. I wish fetchmail should not mark
> the messages as "read" after downloading them as my mozilla email client
> doesn't recognize the new messages as unread.
>
> Is there a option to specify in .fetchmailrc to mark the messages
> "unread" in the server as I can view them as usual in the mozilla.
In short, no. Fetchmail was written with the assumption that it would
be the only program accessing a mailbox.
You *might* find that if your ISP uses POP3 that you can use that
interface (ensuring you configure fetchmail with the "keep" and "uidl"
options) to achieve what you want.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Balaji K. <ba...@ti...> - 2006-05-12 16:23:26
|
Hi I have fetchmail setup running to pull messages from the IMAP server using procmail as the mda. I use mozilla as the mail client and use procmail+fetchmail to run some scripts. I wish fetchmail should not mark the messages as "read" after downloading them as my mozilla email client doesn't recognize the new messages as unread. Is there a option to specify in .fetchmailrc to mark the messages "unread" in the server as I can view them as usual in the mozilla. Thanks in advance Balaji.k |
|
From: Lars T. <ls...@gm...> - 2006-05-10 12:56:37
|
Hello! Using fetchmail successfully with polling by interval for several months I just tried to use the IMAP idle-extension to get my mails delivered immediately. Unfortunately only one message gets fetched - after that, fetchmail recognizes the arrival of a new one, but instead of downloading the message, it just triggers another idle. --------------------------------------------------------------------- lsr@lsr:# fetchmail -v -v fetchmail: 6.3.4 querying imap.strato.de (protocol IMAP) at Wed 10 May 2006 12:05:46 PM CEST: poll started fetchmail: IMAP< * OK IMAP server ready fetchmail: IMAP> A0001 CAPABILITY fetchmail: IMAP< * CAPABILITY IDLE IMAP4rev1 AUTH=CRAM-MD5 SORT QUOTA NAMESPACE fetchmail: IMAP< A0001 OK CAPABILITY completed fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: will idle after poll fetchmail: IMAP> A0002 AUTHENTICATE CRAM-MD5 fetchmail: IMAP< + PDQ3NzgwMi4yMTY1Ni4xMTQ3MjU1NTMzQHBvc3Qud2VibWFpbGVyLmRlPg== fetchmail: decoded as <477...@po...> fetchmail: IMAP> bHNyQHZpZXctc291cmNlLmRlIGQ4Nzg1YzVjMzAxZjI4NTBjZTg4ZDA0ZWMxMmU2Y2E5 fetchmail: IMAP< A0002 OK LOGIN completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0003 SELECT "INBOX" fetchmail: IMAP< * 0 EXISTS fetchmail: IMAP< * 0 RECENT fetchmail: IMAP< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded) fetchmail: IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \Forwarded)] Permanent flags fetchmail: IMAP< * OK [UIDVALIDITY 1116049368] UIDVALIDITY value fetchmail: IMAP< * OK [UIDNEXT 3216] may be the next UID value fetchmail: IMAP< A0003 OK [READ-WRITE] SELECT completed fetchmail: 0 messages waiting after first poll fetchmail: IMAP> A0004 IDLE fetchmail: IMAP< + will notify you of all changes > so far, so good: mailbox is empty. > sending first mail to this account now! fetchmail: IMAP< * 1 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0004 OK IDLE completed fetchmail: 1 message waiting after re-poll fetchmail: IMAP> A0005 SEARCH UNSEEN NOT DELETED fetchmail: IMAP< * SEARCH 1 fetchmail: 1 is unseen fetchmail: IMAP< A0005 OK SEARCH completed fetchmail: 1 is first unseen fetchmail: 1 message for ls...@vi... at imap.strato.de. fetchmail: IMAP> A0006 FETCH 1 RFC822.SIZE fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 906) fetchmail: IMAP< A0006 OK Fetch complete fetchmail: IMAP> A0007 FETCH 1 RFC822.HEADER fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {898} fetchmail: reading message ls...@vi...@imap.rzone.de:1 of 1 (898 header octets) fetchmail: About to rewrite From: Lars Tewes <ls...@gm...> Rewritten version is From: Lars Tewes <ls...@gm...> fetchmail: About to rewrite To: Lars Tewes <ls...@vi...> Rewritten version is To: Lars Tewes <ls...@vi...> fetchmail: about to deliver with: /usr/bin/procmail -d 'lsr' fetchmail: IMAP< ) fetchmail: IMAP< A0007 OK Fetch complete fetchmail: IMAP> A0008 FETCH 1 BODY.PEEK[TEXT] fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {8} fetchmail: (8 body octets) fetchmail: IMAP< ) fetchmail: IMAP< A0008 OK Fetch complete fetchmail: flushed fetchmail: IMAP> A0009 STORE 1 +FLAGS (\Seen \Deleted) fetchmail: IMAP< * 1 FETCH (FLAGS (\Deleted \Seen \Recent)) fetchmail: IMAP< A0009 OK STORE completed fetchmail: IMAP> A0010 EXPUNGE fetchmail: IMAP< * 1 EXPUNGE fetchmail: IMAP< A0010 OK EXPUNGE completed fetchmail: selecting or re-polling default folder fetchmail: IMAP> A0011 IDLE fetchmail: IMAP< + will notify you of all changes > well done, fetchmail gets notified, stops "imap idle" and sends "A0005 SEARCH UNSEEN NOT DELETED", then downloads the message and negotiates idle again > sending second mail to this account now... fetchmail: IMAP< * 1 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0011 OK IDLE completed fetchmail: IMAP> A0012 IDLE fetchmail: IMAP< + will notify you of all changes > hmmm, idle is interuppted by fetchmail as before, but instead of polling the new message, it just sends anonther "idle". > sending third mail to this account now... fetchmail: IMAP< * 2 EXISTS fetchmail: IMAP> DONE fetchmail: IMAP< A0012 OK IDLE completed fetchmail: IMAP> A0013 IDLE fetchmail: IMAP< + will notify you of all changes etc. etc. --------------------------------------------------------------------- Who's to blame? My config, a stupid server or a bug in fetchmail? --------------------------------------------------------------------- .fetchmailrc: poll imap.strato.de protocol imap username "ls...@vi..." password "xxxxxxxx" mda "/usr/bin/procmail -d %s" idle --------------------------------------------------------------------- lsr@lsr:# fetchmail -V This is fetchmail release 6.3.4+RPA+NTLM+SDPS+SSL+NLS. Copyright (C) 2002, 2003 Eric S. Raymond Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham Wilson Copyright (C) 2005-2006 Matthias Andree, Sunil Shetye Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For details, please see the file COPYING in the source or documentation directory. Fallback MDA: (none) Linux lsr 2.6.15.6 #4 PREEMPT Mon Apr 24 10:54:39 CEST 2006 i686 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux Taking options from command line and /home/lsr/.fetchmailrc Idfile is /home/lsr/.fetchids Fetchmail will show progress dots even in logfiles. Fetchmail will forward misaddressed multidrop messages to lsr. Options for retrieving from ls...@vi...@imap.strato.de: True name of server is imap.strato.de. Protocol is IMAP. All available authentication methods will be tried. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. Only new messages will be retrieved (--all off). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Oversized messages will not be flushed before message retrieval (--limitflush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is enabled (stripcr on). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is enabled (idle on). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4). Messages will be delivered with "/usr/bin/procmail -d %s". Single-drop mode: 1 local name recognized. No UIDs saved from this host. --------------------------------------------------------------------- Regards Lars |
|
From: Catalin R. <cat...@gm...> - 2006-05-10 11:41:45
|
Found the culprit: SELinux. When disabled, the problem disappears. I should have guessed it... Cata On 5/9/06, Rob MacGregor <rob...@gm...> wrote: > On 5/9/06, Catalin Rotaru <cat...@gm...> wrote: > > > > Tried. Sadly, that didn't fix it. I will try starting from the source > > and compiling. Is there any way to view and compare the "boot" and > > "regular" environments and libraries? > > Not easily. My usual trick is to stick something like "env > > /tmp/fetchmail-boot-env" in the startup script before fetchmail is > called. The other option is to change the start line to include "-x" > to see what it does (caution, makes the boot screen messy - you'll > need to have some way of scrolling the console). > > -- > Please keep list traffic on the list. > > Rob MacGregor > Whoever fights monsters should see to it that in the process he > doesn't become a monster. Friedrich Nietzsche > _______________________________________________ > fetchmail-users mailing list > fet...@li... > http://lists.berlios.de/mailman/listinfo/fetchmail-users > -- Catalin Rotaru http://www.rotaru.com |
|
From: Rob M. <rob...@gm...> - 2006-05-09 17:45:44
|
On 5/9/06, Catalin Rotaru <cat...@gm...> wrote:
>
> Tried. Sadly, that didn't fix it. I will try starting from the source
> and compiling. Is there any way to view and compare the "boot" and
> "regular" environments and libraries?
Not easily. My usual trick is to stick something like "env >
/tmp/fetchmail-boot-env" in the startup script before fetchmail is
called. The other option is to change the start line to include "-x"
to see what it does (caution, makes the boot screen messy - you'll
need to have some way of scrolling the console).
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Frederic M. <fre...@wo...> - 2006-05-09 12:59:24
|
Matthias Andree wrote: > Frederic Marchal <fre...@wo...> writes: > > >> Hello, >> > Even if the code behaves better than the documentation suggests, > describing the "--flush" option in a scary way looks correct to me. > Ok, I can understand that. > Does this patch help your problem (without your adding --flush, that is)? > I tested it on the test server and it worked as expected. Now, it is in production but I may have to wait until next Monday for the flood of mails from the week-end to know if it is ok (and hope the connection drops :-) ). BTW, isn't it another way of doing the flush you said was a scary thing ? > It is against fetchmail 6.3.4 but may also work against 6.3.2: > It does. Thank you. Frederic |
|
From: Catalin R. <cat...@gm...> - 2006-05-09 12:23:54
|
On 5/8/06, Rob MacGregor <rob...@gm...> wrote: > On 5/8/06, Catalin Rotaru <cat...@gm...> wrote: > > > > Oops, sorry about that. I just hit "Reply" without checking. My bad. I > > notice now that the list doesn't have a "Reply-To" header. Maybe one > > could be added? I am pretty sure MailMan supports it. Just an idea. > > This has been discussed before a number of times. There are as many > arguments for as against. It seems to be generally least harmful to > not set the Reply-to header - or at least setting it annoys the > developers :-) Got it. > > Aaah, I was afraid you'd say that. I am no Linux (and especially > > Fedora) expert and my preferred way of installing software is "yum > > install". I am afraid of breaking even more stuff I don't understand > > if I try to install from source on my own. > > Try re-installing via yum then. I've a suspicion your problem is > related to library version mismatches. It could be that once you've > logged in interactively enough environment is set so that it finds the > right libraries. > Tried. Sadly, that didn't fix it. I will try starting from the source and compiling. Is there any way to view and compare the "boot" and "regular" environments and libraries? > > Any pointers to where I can learn more about > > installing/removing/reinstalling fetchmail on Fedora? With all > > RedHat's idiosyncrasies and stuff? > > For that you'll have to look to the RH/Fedora lists/forums. I'll have > to admit to having only very limited experience of using RPMs etc. > Done - but now answers yet... Cata |
|
From: Rob M. <rob...@gm...> - 2006-05-08 18:55:41
|
On 5/8/06, Catalin Rotaru <cat...@gm...> wrote:
>
> Oops, sorry about that. I just hit "Reply" without checking. My bad. I
> notice now that the list doesn't have a "Reply-To" header. Maybe one
> could be added? I am pretty sure MailMan supports it. Just an idea.
This has been discussed before a number of times. There are as many
arguments for as against. It seems to be generally least harmful to
not set the Reply-to header - or at least setting it annoys the
developers :-)
> Aaah, I was afraid you'd say that. I am no Linux (and especially
> Fedora) expert and my preferred way of installing software is "yum
> install". I am afraid of breaking even more stuff I don't understand
> if I try to install from source on my own.
Try re-installing via yum then. I've a suspicion your problem is
related to library version mismatches. It could be that once you've
logged in interactively enough environment is set so that it finds the
right libraries.
> Any pointers to where I can learn more about
> installing/removing/reinstalling fetchmail on Fedora? With all
> RedHat's idiosyncrasies and stuff?
For that you'll have to look to the RH/Fedora lists/forums. I'll have
to admit to having only very limited experience of using RPMs etc.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Rob M. <rob...@gm...> - 2006-05-08 18:48:35
|
On 5/8/06, Shukla Vipul <vip...@gm...> wrote:
> HI,
>
> I am using fetchmail for downloading mails from server, but fetchmail
> is very slow i got my mail after 12hours i want to get it fast.
There are only 2 things that can cause fetchmail to run slow (assuming
you're not trying to run it on a 386 or older):
1) Slow network link
2) Slow MTA for delivery
What we really need to see are:
1) Contents of .fetchmailrc (masking passwords etc)
2) Output of "fetchmail -v -v --nosyslog"
3) Contents of your mail log (probably /var/log/maillog or similar)
for the same run as (2)
To help you identify where your problem lies.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Matthias A. <mat...@gm...> - 2006-05-08 16:00:46
|
"Catalin Rotaru" <cat...@gm...> writes: >> > What else can I try? >> >> You can start by keeping traffic on the list, rather than emailing me >> directly - as it says in my .sig. > > Oops, sorry about that. I just hit "Reply" without checking. My bad. I > notice now that the list doesn't have a "Reply-To" header. Maybe one > could be added? I am pretty sure MailMan supports it. Just an idea. No way - as I said earlier, should the list set a Reply-To: header, I'm outta here. Some mailers don't allow users to override Reply-To, but all allow to include all To: and Cc: addresses in the reply. Hit "List Reply" or "Reply to List" or "Group Reply" or "Reply to All". See <http://www.unicom.com/pw/reply-to-harmful.html> for more information. > Aaah, I was afraid you'd say that. I am no Linux (and especially > Fedora) expert and my preferred way of installing software is "yum > install". I am afraid of breaking even more stuff I don't understand > if I try to install from source on my own. Well, I am inclined to think Miloslav Trmac and other packagers were careful enough or would chime in here if it was related to their packaging. With support respective to the Fedora boot issues, you may have to check the Fedore Support options (probably also mailing list, forums or newsgroups as well) as well. -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2006-05-08 15:56:57
|
"Shukla Vipul" <vip...@gm...> writes: > I am using fetchmail for downloading mails from server, but fetchmail is very slow i got my mail after > 12hours i want to get it fast. as per i have searched ther is two parameter which i have to set that is > fetchlimit and fetchsizelimit. but i dont know where i have to use these parameter i have checked ~ > /.fetchmailrc file also, i am not able to undestand how to modify it. You need to check the manual page, type man fetchmail to get the documentation. If you still need support then, you'll have to show ~/.fetchmailrc (MASK YOUR PASSWORDS!). Also, be sure to use a recent fetchmail version, one of the later 6.3.X versions is a good idea. HTH, -- Matthias Andree |
|
From: Frederic M. <fre...@wo...> - 2006-05-08 15:55:23
|
Shukla Vipul wrote: > HI, > > I am using fetchmail for downloading mails from server, but > fetchmail is very slow i got my mail after 12hours i want to get it > fast. as per i have searched ther is two parameter which i have to set > that is fetchlimit and fetchsizelimit. but i dont know where i have to > use these parameter i have checked ~/.fetchmailrc file also, i am > not able to undestand how to modify it. What do you mean when you say your mails arrived after 12 hours ? - does it take 12 hours to download the actual data of your mails (i.e the connection is slow); - does it try to download the mails for 12 hours until it succeeds (a lot of connection failures); - does it sit around and eventually fetch your mails (the poll delay is too long) ? The first two cases, may not be related to fetchmail or its configuration file but some settings may help. The latter is the poll delay set by parameter "set daemon" in your fetchmailrc file. Mine looks like this (only the relevant lines shown): # The default for this option is 300, which polls the server every 5 # minutes. # set daemon 300 Regarding your second question, the parameters should be defined in your fetchmailrc either in a default section like this: defaults: uidl batchlimit 100 fetchlimit 100 flush or in the poll command in fetchmailrc or on the command line (sorry, I have no example here :-). Note: you must insert these commands in the fetchmailrc fetchmail is looking at (obvious, but I got caught there) ! It is ~/.fetchmailrc unless the -f option is given on the command line. Frederic |
|
From: Matthias A. <mat...@gm...> - 2006-05-08 15:54:37
|
Frederic Marchal <fre...@wo...> writes:
> Hello,
>
> I quote the man page of version 6.3.2:
>
> -F | --flush
> POP3/IMAP only. Delete old (previously retrieved) messages
> from the mailserver before retrieving new mes-
> sages. This option does not work with ETRN or ODMR.
> Warning: if your local MTA hangs and fetchmail is
> aborted, the next time you run fetchmail, it will delete
> mail that was never delivered to you. What you
> probably want is the default setting: if you don't
> specify `-k', then fetchmail will automatically delete
> messages after successful delivery.
>
> Is it still true that a mail is lost if the MTA hangs ? It sounds like
> a known bug and may have been fixed in the code but not in the man page.
Even if the code behaves better than the documentation suggests,
describing the "--flush" option in a scary way looks correct to me.
> I explain my situation: if the connection with the pop3 server drops,
> all the DELE commands are forgotten (as required by the pop3 protocol if
> I understand it right) and the mails reappear on the next poll. But
> since fetchmail knows about those messages, it ignores them and doesn't
> delete them either.
Well, that's an interesting scenario and fetchmail should probably be
fixed instead of fixing the potential workarounds. Only I need to think
how to handle servers that recycle UIDs (unfortunately, these are only
unique while the message is on the server, so fetchmail needs to know if
the server deletes the message or now).
Does this patch help your problem (without your adding --flush, that is)?
It is against fetchmail 6.3.4 but may also work against 6.3.2:
Index: driver.c
===================================================================
--- driver.c (Revision 4818)
+++ driver.c (Arbeitskopie)
@@ -781,7 +781,7 @@
else if (ctl->server.base_protocol->delete_msg
&& !suppress_delete
&& ((msgcode >= 0 && !ctl->keep)
- || (msgcode == MSGLEN_OLD && ctl->flush)
+ || (msgcode == MSGLEN_OLD && (ctl->flush || !ctl->keep))
|| (msgcode == MSGLEN_TOOLARGE && ctl->limitflush)))
{
(*deletions)++;
--
Matthias Andree
|
|
From: Catalin R. <cat...@gm...> - 2006-05-08 15:37:14
|
> > What else can I try? > > You can start by keeping traffic on the list, rather than emailing me > directly - as it says in my .sig. Oops, sorry about that. I just hit "Reply" without checking. My bad. I notice now that the list doesn't have a "Reply-To" header. Maybe one could be added? I am pretty sure MailMan supports it. Just an idea. > > Try installing a fresh copy of fetchmail. It's likly that your > upgrade, as isn't uncommon, broke something. Ideally install from > source (if you later want to replace it with one from an RPM that's > your choice). Aaah, I was afraid you'd say that. I am no Linux (and especially Fedora) expert and my preferred way of installing software is "yum install". I am afraid of breaking even more stuff I don't understand if I try to install from source on my own. Any pointers to where I can learn more about installing/removing/reinstalling fetchmail on Fedora? With all RedHat's idiosyncrasies and stuff? Thanks, Cata |
|
From: Shukla V. <vip...@gm...> - 2006-05-08 14:51:06
|
HI,
I am using fetchmail for downloading mails from server, but fetchmail is
very slow i got my mail after 12hours i want to get it fast. as per i have
searched ther is two parameter which i have to set that is fetchlimit and
fetchsizelimit. but i dont know where i have to use these parameter i have
checked ~/.fetchmailrc file also, i am not able to undestand how to modify
it.
Thanks
Vipul
|
|
From: Rob M. <rob...@gm...> - 2006-05-08 13:06:34
|
(And on that note, all future unedited digest subjects should be caught by the spam filter and rejected by the admins) On 5/8/06, Admin Att <att...@gm...> wrote: > If i understood correctly aka is for servers that use your ISP, but one is > from ISP and other is senders server which is always diffrent (at least much > times) so how can i use aka except for putting ISP's server name. > > > fetchmail: line accepted, MyISPname is an alias of the mailserver > fetchmail: no Received address found > fetchmail: analyzing Received line: > Received: from testpc1 by mycompany.com > (MDaemon.PRO.v8.1.5.R) > with ESMTP id md50000169342.msg > for <te...@be...>; Wed, 26 Apr 2006 13:49:03 +0200 > fetchmail: line rejected, mycompany.com is not an alias of the mailserver > > i inserted one AKA as i said for ISP name..another aka would be in this case > mycompany.com > but what if mail is from gmail, or yahoo or whatever...?:) Any vaguely competent ISP will provide a Delivered-to type header. The problem only occurs when your ISP is lacking in the clue department. The solution is simple, stop flogging the dead horse - multidrop will *NEVER* reliably work when the ISP doesn't provide the required headers. Either switch ISP or stop trying to use multidrop with them. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
|
From: Rob M. <rob...@gm...> - 2006-05-08 12:58:41
|
On 5/8/06, Catalin Rotaru <cat...@gm...> wrote:
> Done. The output file *gets* created on boot but it completely empty
> (0 bytes)... The strangest thing is that if I start fetchmail
> afterwards manually, it outputs the warning:
> "fetchmail: WARNING: Running as root is discouraged."
>
> What else can I try?
You can start by keeping traffic on the list, rather than emailing me
directly - as it says in my .sig.
Try installing a fresh copy of fetchmail. It's likly that your
upgrade, as isn't uncommon, broke something. Ideally install from
source (if you later want to replace it with one from an RPM that's
your choice).
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Frederic M. <fre...@wo...> - 2006-05-08 12:48:04
|
Hello,
I quote the man page of version 6.3.2:
-F | --flush
POP3/IMAP only. Delete old (previously retrieved)
messages from the mailserver before retrieving new mes-
sages. This option does not work with ETRN or ODMR.
Warning: if your local MTA hangs and fetchmail is
aborted, the next time you run fetchmail, it will delete
mail that was never delivered to you. What you
probably want is the default setting: if you don't
specify `-k', then fetchmail will automatically delete
messages after successful delivery.
Is it still true that a mail is lost if the MTA hangs ? It sounds like
a known bug and may have been fixed in the code but not in the man page.
I explain my situation: if the connection with the pop3 server drops,
all the DELE commands are forgotten (as required by the pop3 protocol if
I understand it right) and the mails reappear on the next poll. But
since fetchmail knows about those messages, it ignores them and doesn't
delete them either. They keep showing up in the UIDL at every poll and
remain on the server until I delete them manually. The -F option solves
this problem but I don't want to loose any mail.
Frederic
|
|
From: Admin A. <att...@gm...> - 2006-05-08 12:40:34
|
If i understood correctly aka is for servers that use your ISP, but one is from ISP and other is senders server which is always diffrent (at least much times) so how can i use aka except for putting ISP's server name. fetchmail: line accepted, MyISPname is an alias of the mailserver fetchmail: no Received address found fetchmail: analyzing Received line: Received: from testpc1 by mycompany.com (MDaemon.PRO.v8.1.5.R) with ESMTP id md50000169342.msg for <te...@be...>; Wed, 26 Apr 2006 13:49:03 +0200 fetchmail: line rejected, mycompany.com is not an alias of the mailserver i inserted one AKA as i said for ISP name..another aka would be in this case mycompany.com but what if mail is from gmail, or yahoo or whatever...?:) Regards > I didin't understand you correctly what you mean by : "Do you have details > > in anything other than the Received headers?" > > i copy/pasted my complete log with all what is happening with this conf > file > > and variations of him. > > > > btw, i think biggets problem is that my isp is not adding anything they > dont > > get from original sender so no additional field i can not get from them > > except fields that are included from original sender and that is usually > > Received line > > See the email from Matthias - you may find that the aka option works > for you. However if it doesn't then you're out of luck. Your ISP > isn't providing enough information in the headers for multidrop to > reliably work. > > -- > Please keep list traffic on the list. > Rob MacGregor > Whoever fights monsters should see to it that in the process he > doesn't become a monster. Friedrich Nietzsche > > > --__--__-- > > _______________________________________________ > fetchmail-users mailing list > fet...@li... > http://lists.berlios.de/mailman/listinfo/fetchmail-users > > > End of fetchmail-users Digest > |
|
From: Rob M. <rob...@gm...> - 2006-05-07 18:24:35
|
On 5/7/06, Catalin Rotaru <cat...@gm...> wrote:
> The problem: right after booting, fetchmail doesn't do anything,
> although ps shows it as running. It doesn't fetch and it doesn't
> output *any* log.
>
> This started to happen after upgrading to Fedora Core 5 from FC4.
The lack of any log output suggests something very broken. Can you
switch the "/dev/null" in the startup script to, say,
"/tmp/fetchmaillog" and reboot? The OS is probably reporting
something that you're never seeing as it's being dropped in the bit
bucket.
The odds are that you're seeing it work on the command line because
your environment isn't the same as the boot environment. Quite
possibly the settings regarding the library paths.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Catalin R. <cat...@gm...> - 2006-05-07 15:41:13
|
The problem: right after booting, fetchmail doesn't do anything, although ps shows it as running. It doesn't fetch and it doesn't output *any* log. This started to happen after upgrading to Fedora Core 5 from FC4. A simple restart (service fetchmail restart) gets it going, with logging and fetching and all... fetchmail --version fetchmail: WARNING: Running as root is discouraged. This is fetchmail release 6.3.4+IMAP-GSS+RPA+NTLM+SDPS+SSL+HESIOD+NLS. uname -a Linux foo.bar.net 2.6.16-1.2111_FC5 #1 Thu May 4 21:16:58 EDT 2006 i686 athlon i386 GNU/Linux more /etc/fetchmailrc #set daemon 100 poll foo.bar.com proto imap localdomains bar.net user "user" pass "pass" is "user" here ... more /etc/init.d/fetchmail ... FETCHMAIL=/usr/bin/fetchmail FRC=/etc/fetchmailrc TIME=100 start() { $FETCHMAIL -f $FRC -L /var/log/fetchmail -d $TIME >/dev/null 2>&1 } ... Any clues? Thanks! Cata |