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
|
Nov
|
Dec
|
From: Matthias A. <mat...@gm...> - 2006-11-02 00:16:12
|
"Rob MacGregor" <rob...@gm...> writes: > On 11/1/06, Net Cerebrum <net...@gm...> wrote: >> Is there any script available which will check for the presence of >> .fetchmailrc in all the user home directories (around 100) and then run >> fetchmail for multiple users simultaneoulsy to retrieve their mail from the >> remote server and deliver it to the local MTA. > > I've a vague memory somebody posted something to the list a while > back. If there isn't anything I could probably knock something out > over the weekend - it's not terribly complicated. Check the start script Simon Barner wrote for the FreeBSD port - it relies on FreeBSD's rcNG (rc_subr) though. -- Matthias Andree |
From: Rob M. <rob...@gm...> - 2006-11-01 17:57:55
|
On 11/1/06, Net Cerebrum <net...@gm...> wrote: > Is there any script available which will check for the presence of > .fetchmailrc in all the user home directories (around 100) and then run > fetchmail for multiple users simultaneoulsy to retrieve their mail from the > remote server and deliver it to the local MTA. I've a vague memory somebody posted something to the list a while back. If there isn't anything I could probably knock something out over the weekend - it's not terribly complicated. -- 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: Net C. <net...@gm...> - 2006-11-01 16:51:42
|
Is there any script available which will check for the presence of .fetchmailrc in all the user home directories (around 100) and then run fetchmail for multiple users simultaneoulsy to retrieve their mail from the remote server and deliver it to the local MTA. Thanks, |
From: Rob M. <rob...@gm...> - 2006-10-28 18:29:58
|
On 10/28/06, Hasan Shatty <hs...@ya...> wrote: > Dear Rob, > > I'm using oracle email server. It returns errors such as : 5.6.0: NULs not > allowed or 5.5.1: unrecognized command, before it drops the connection, but > fetchmail doesn't catch the error codes. > I've added the antispam option as: antispam 560,551 > Is that correct.? It should be providing other messages and codes - for example your "5.5.1" should be accompanied by a 500 error. See RFC 2821: http://www.faqs.org/rfcs/rfc2821.html If you can't get Oracle email server (which by the looks of things Oracle don't develop any more) to behave correctly then you're out of luck. You either need to abandon trying to get fetchmail to work with such a broken server, or move to a working one. -- 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: Hasan S. <hs...@ya...> - 2006-10-28 16:53:00
|
Dear Rob, I'm using oracle email server. It returns errors such as : 5.6.0: NULs not allowed or 5.5.1: unrecognized command, before it drops the connection, but fetchmail doesn't catch the error codes. I've added the antispam option as: antispam 560,551 Is that correct.? Rob MacGregor <rob...@gm...> wrote: On 10/28/06, Hasan Shatty wrote: > I have added the antispam option, but it didn't help. Still fetchmail gives > one of the errors: > > fetchmail: MDA error while fetching from us...@do... > fetchmail: Query status=6 (IOERR) > > or > > : SIGPIPE thrown from an MDA or a stream socket error > fetchmail: socket error while fetching from us...@do... and delivering > to SMTP host localhost > fetchmail: Query status=2 (SOCKET) Please go and re-read my original email in this thread. You *MUST* configure the MTA to provide an error code - simply dropping the connection is the wrong behaviour. If you want any more help you'll need to provide details of your MTA, otherwise you're on your own. -- 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... https://lists.berlios.de/mailman/listinfo/fetchmail-users --------------------------------- Everyone is raving about the all-new Yahoo! Mail. |
From: Rob M. <rob...@gm...> - 2006-10-28 16:06:14
|
On 10/28/06, Hasan Shatty <hs...@ya...> wrote: > I have added the antispam option, but it didn't help. Still fetchmail gives > one of the errors: > > fetchmail: MDA error while fetching from us...@do... > fetchmail: Query status=6 (IOERR) > > or > > : SIGPIPE thrown from an MDA or a stream socket error > fetchmail: socket error while fetching from us...@do... and delivering > to SMTP host localhost > fetchmail: Query status=2 (SOCKET) Please go and re-read my original email in this thread. You *MUST* configure the MTA to provide an error code - simply dropping the connection is the wrong behaviour. If you want any more help you'll need to provide details of your MTA, otherwise you're on your own. -- 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: Hasan S. <hs...@ya...> - 2006-10-28 15:01:31
|
I have added the antispam option, but it didn't help. Still fetchmail gives one of the errors: fetchmail: MDA error while fetching from us...@do... fetchmail: Query status=6 (IOERR) or : SIGPIPE thrown from an MDA or a stream socket error fetchmail: socket error while fetching from us...@do... and delivering to SMTP host localhost fetchmail: Query status=2 (SOCKET) Thanks, Rob MacGregor <rob...@gm...> wrote: On 10/27/06, Hasan Shatty wrote: > > > Thanks Rob, > > Is this the only possible solution, because I doubt, I can do such > configuration in my MTA. Any half decent MTA will support this - which one are you using? -- 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... https://lists.berlios.de/mailman/listinfo/fetchmail-users --------------------------------- Everyone is raving about the all-new Yahoo! Mail. |
From: Rob M. <rob...@gm...> - 2006-10-27 18:48:47
|
On 10/27/06, Chris Cera <ce...@cs...> wrote: > Thanks for the response Rob. > > It appears this is not a fetchmail problem so I apologize for > posting to this forum. Sometimes it's hard to tell at first, no problem. > It doesn't appear to be a problem with the client either since I > just confirmed that it does the same thing on another account > that I have (with postfix and no procmail, no fetchmail, etc.). > My mail client is basically just 'cat'ing /var/mail/chris. > > I can't explain why gmail has no problem with it though ... so I > will continue my search elsewhere. Thank you! I would say it's down to the support for format=flowed. A very quick explanation, take the following: >One long wrapped >line is here. > >And another long >wrapped paragraph >here. With format=flowed and support in the mail client you'd see: >One long wrapped line is here. > >And another long wrapped paragraph here. With either a client that doesn't support it, or just text/plain you'd see it as the first example. Google will give you many more detailed (and more accurate) explanations. -- 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-10-27 18:40:35
|
On 10/27/06, Hasan Shatty <hs...@ya...> wrote: > > > Thanks Rob, > > Is this the only possible solution, because I doubt, I can do such > configuration in my MTA. Any half decent MTA will support this - which one are you using? -- 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: Chris C. <ce...@cs...> - 2006-10-27 15:30:38
|
Thanks for the response Rob. It appears this is not a fetchmail problem so I apologize for posting to this forum. It doesn't appear to be a problem with the client either since I just confirmed that it does the same thing on another account that I have (with postfix and no procmail, no fetchmail, etc.). My mail client is basically just 'cat'ing /var/mail/chris. I can't explain why gmail has no problem with it though ... so I will continue my search elsewhere. Thank you! * Rob MacGregor <rob...@gm...> [061027 02:54]: > On 10/27/06, Rob MacGregor <rob...@gm...> wrote: > > > > No. How your mail client treats the mail is beyond fetchmail's control. > > > > I'd suggest you confirm that it's a bug with Apple Mail by pointing it > > directly at your ISP and downloading a test email with a long URL. > > This should give you enough to allow you to file a bug report with > > Apple. > > I should have said that the problem is that (it appears that) Apple > Mail isn't honouring format=flowed. You'll almost certainly find that > the original email has the lines wrapped at 72 characters, hence why > Apple Mail displays the URLs wrapped at 72 characters. > > You still can't fix this with fetchmail :) > > -- > 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... > https://lists.berlios.de/mailman/listinfo/fetchmail-users -- Chris Cera http://cera.us |
From: Hasan S. <hs...@ya...> - 2006-10-27 11:51:02
|
Thanks Rob, Is this the only possible solution, because I doubt, I can do such configuration in my MTA. Rob MacGregor <rob...@gm...> wrote: On 10/26/06, Hasan Shatty wrote: > I have setup fetchmail to fetch from a multidrop pop account and deliver to > a local MTA. > > Some messages (mostly spam or corrupted) cause the MTA to close the socket > and not accept the message. In this case fetchmail will retry to deliver the > same message again and mails will get accumulated until I delete the > problematic messge from the queue. > > Is there a way to avoid this issue and let fetchmail simply delete the > message or ignore it or deliver it to a local spool. Correctly configure the MTA to provide an appropriate error code - see the section titled "Spam Filtering" in the fetchmail man page. -- 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... https://lists.berlios.de/mailman/listinfo/fetchmail-users --------------------------------- How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates. --------------------------------- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. |
From: Hasan S. <hs...@ya...> - 2006-10-27 11:50:59
|
Thanks Rob, Is this the only possible solution, because I doubt, I can do such configuration in my MTA. Rob MacGregor <rob...@gm...> wrote: On 10/26/06, Hasan Shatty wrote: > I have setup fetchmail to fetch from a multidrop pop account and deliver to > a local MTA. > > Some messages (mostly spam or corrupted) cause the MTA to close the socket > and not accept the message. In this case fetchmail will retry to deliver the > same message again and mails will get accumulated until I delete the > problematic messge from the queue. > > Is there a way to avoid this issue and let fetchmail simply delete the > message or ignore it or deliver it to a local spool. Correctly configure the MTA to provide an appropriate error code - see the section titled "Spam Filtering" in the fetchmail man page. -- 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... https://lists.berlios.de/mailman/listinfo/fetchmail-users --------------------------------- How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates. --------------------------------- Stay in the know. Pulse on the new Yahoo.com. Check it out. |
From: Rob M. <rob...@gm...> - 2006-10-27 08:55:24
|
On 10/27/06, Rob MacGregor <rob...@gm...> wrote: > > No. How your mail client treats the mail is beyond fetchmail's control. > > I'd suggest you confirm that it's a bug with Apple Mail by pointing it > directly at your ISP and downloading a test email with a long URL. > This should give you enough to allow you to file a bug report with > Apple. I should have said that the problem is that (it appears that) Apple Mail isn't honouring format=flowed. You'll almost certainly find that the original email has the lines wrapped at 72 characters, hence why Apple Mail displays the URLs wrapped at 72 characters. You still can't fix this with fetchmail :) -- 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-10-27 08:13:07
|
On 10/27/06, Chris Cera <ce...@cs...> wrote: > All my coworkers that send me URLs using Apple Mail have links > over 72 characters wrapped. I have a feeling that the > Content-Type line is the problem, particularly the format=flowed > portion of the header. Are there any options I can set in > fetchmail to prevent this from happening? No. How your mail client treats the mail is beyond fetchmail's control. I'd suggest you confirm that it's a bug with Apple Mail by pointing it directly at your ISP and downloading a test email with a long URL. This should give you enough to allow you to file a bug report with Apple. -- 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: Chris C. <ce...@cs...> - 2006-10-27 01:22:06
|
All my coworkers that send me URLs using Apple Mail have links over 72 characters wrapped. I have a feeling that the Content-Type line is the problem, particularly the format=flowed portion of the header. Are there any options I can set in fetchmail to prevent this from happening? It appears as though the source email, before I download it via fetchmail, is fine when I use the web-based client. The email they send is in plain-text format. The headers are below. Any help is greatly appreciated. Thank you! Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <EB8...@dr...> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Chris Cera <te...@te...> From: Test Person <te...@te...> Subject: long link... Date: Thu, 26 Oct 2006 18:48:42 -0400 X-Mailer: Apple Mail (2.752.2) X-Identified-User: {1262:box101.test.com:drakonta:drakontas.com} {sentby:bopbeforesmtp 71.242.246.42 authed with drakontas.com} X-IMAPbase: 1161902931 1 Status: RO X-Status: X-Keywords: X-UID: 1 -- Chris Cera http://cera.us |
From: Rob M. <rob...@gm...> - 2006-10-26 17:43:11
|
On 10/26/06, Hasan Shatty <hs...@ya...> wrote: > I have setup fetchmail to fetch from a multidrop pop account and deliver to > a local MTA. > > Some messages (mostly spam or corrupted) cause the MTA to close the socket > and not accept the message. In this case fetchmail will retry to deliver the > same message again and mails will get accumulated until I delete the > problematic messge from the queue. > > Is there a way to avoid this issue and let fetchmail simply delete the > message or ignore it or deliver it to a local spool. Correctly configure the MTA to provide an appropriate error code - see the section titled "Spam Filtering" in the fetchmail man page. -- 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: Hasan S. <hs...@ya...> - 2006-10-26 14:48:49
|
I have setup fetchmail to fetch from a multidrop pop account and deliver to a local MTA. Some messages (mostly spam or corrupted) cause the MTA to close the socket and not accept the message. In this case fetchmail will retry to deliver the same message again and mails will get accumulated until I delete the problematic messge from the queue. Is there a way to avoid this issue and let fetchmail simply delete the message or ignore it or deliver it to a local spool. My .fetchmailrc file as follows: set daemon 120 set logfile "/var/log/fetchmail" set postmaster pos...@do... set no bouncemail poll mailserver.domain.com proto pop3 localdomains domain.com envelope 1 Delivered-To: qvirtual '17-' no dns user "popuser" pass "password" to * here fetchall no keep Thanks --------------------------------- All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. |
From: Rob M. <rob...@gm...> - 2006-10-25 07:56:49
|
On 10/25/06, wa...@wa... <wa...@wa...> wrote: > 10242006 1901 GMT-6 > > I'm on ubuntu 6.06LTS. > I'm setting up fetchmail for the first time. > I have a few questions on the settings. > > I have been reading the documentation but as this is all new to me, I > want to make sure I'm getting this right. > > I used fetchmailconf to get started. It created this: > > set syslog > set postmaster "wadesmart" > set no bouncemail > set no spambounce > set properties "" > set daemon 120 > > poll mail.wadesmart.com > user 'wa...@wa...' there with password 'password' is > 'wadesmart' here That looks fine. > That is all that it put down. So I'm reading the documentation and I see > that there is supposed to be something else. I added: > > poll mail.wadesmart.com > uidl protocol pop3 auth password > user 'wa...@wa...' there with password 'password' is > 'wadesmart' here > nokeep UIDL is worth having, the other changes you shouldn't need. > I read in the documentation that postmaster is usually 'root' so I > wonder about this being 'wadesmart'. That's the way I do it and it works fine. -- 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: <wa...@wa...> - 2006-10-25 02:31:46
|
10242006 1901 GMT-6 I'm on ubuntu 6.06LTS. I'm setting up fetchmail for the first time. I have a few questions on the settings. I have been reading the documentation but as this is all new to me, I want to make sure I'm getting this right. I used fetchmailconf to get started. It created this: set syslog set postmaster "wadesmart" set no bouncemail set no spambounce set properties "" set daemon 120 poll mail.wadesmart.com user 'wa...@wa...' there with password 'password' is 'wadesmart' here That is all that it put down. So I'm reading the documentation and I see that there is supposed to be something else. I added: poll mail.wadesmart.com uidl protocol pop3 auth password user 'wa...@wa...' there with password 'password' is 'wadesmart' here nokeep I read in the documentation that postmaster is usually 'root' so I wonder about this being 'wadesmart'. Thanks for the help. wade smart |
From: Matthias A. <mat...@gm...> - 2006-10-25 01:54:54
|
Uli Zappe <ul...@ri...> writes: > Hi, > > I have not been able to download fetchmail-6.3.5.tar.bz2 from the > BerliOS server. > > Loading > > http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2 > > always results in the message > > "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2" > > The number of downloads has remained at 4880 all the time. > > I was able to download fm635-daemon-logfile.patch and > fetchmail-6.3.5.tar.bz2.asc without any problem, so it's not a > general networking issue. Gee, someone apparently trashed the file. I've filed a support request and am uploading 00-fetchmail-6.3.5.tar.bz2 just now. If that doesn't work: http://home.pages.de/~mandree/fetchmail/ Please report future file corruption to me directly (Cc: is fine) so I can see the report much sooner. Thank you. -- Matthias Andree |
From: Rob M. <rob...@gm...> - 2006-10-22 11:08:03
|
On 10/22/06, Uli Zappe <ul...@ri...> wrote: > Hi, > > I have not been able to download fetchmail-6.3.5.tar.bz2 from the > BerliOS server. > > Loading > > http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2 > > always results in the message > > "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2" > > The number of downloads has remained at 4880 all the time. I can confirm this - looks like something broken at berlios :( -- 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: Uli Z. <ul...@ri...> - 2006-10-22 03:55:43
|
Hi, I have not been able to download fetchmail-6.3.5.tar.bz2 from the BerliOS server. Loading http://download(2).berlios.de/fetchmail/fetchmail-6.3.5.tar.bz2 always results in the message "Too many clients for /fetchmail/fetchmail-6.3.5.tar.bz2" The number of downloads has remained at 4880 all the time. I was able to download fm635-daemon-logfile.patch and fetchmail-6.3.5.tar.bz2.asc without any problem, so it's not a general networking issue. Bye Uli ________________________________________________________ Uli Zappe, Solmsstraße 5, D-65189 Wiesbaden, Germany http://www.ritual.org Fon: +49-700-ULIZAPPE Fax: +49-700-ZAPPEFAX ________________________________________________________ |
From: Matthias A. <mat...@gm...> - 2006-10-17 01:37:39
|
longbow <lo...@gm...> writes: > i think i solved the problem on my own: i used the '-a' option in my > local fetchmail command: > /bin/su wolfgang -c '/usr/bin/fetchmail -a -f > /home/wolfgang/.fetchmailrc -d 300 -L /home/wolfgang/fetchmail.log 2>&1' -a (= fetchall) and keep don't mix... > and i think this confused the "keep" option in my .fetchmailrc. i tested > a few mailsendings and everything seems to run fine. i also do not get > the message > fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed) > Both fetchall and keep on in daemon mode is a mistake! ...and fetchmail complains here. So you have been warned about the mistake... -- Matthias Andree |
From: longbow <lo...@gm...> - 2006-10-13 09:27:49
|
Rob MacGregor wrote: > On 10/12/06, longbow <lo...@gm...> wrote: > >> here it is: >> poll MAILSERVER1 protocol IMAP user "MAILBOXUSER1" password "PWD1" >> is LOCALUSER keep >> poll MAILSERVER2 protocol POP3 user "MAILBOXUSER2" password "PWD2" ssl >> is LOCALUSER > > Looks fine. > >> fetchmail --nosyslog -v -v > > Should have been more explicit - can you provide that for a run > showing a mail being downloaded. That way we can confirm fetchmail's > actions. > >> fetchmail --configdump > > Thanks, that shows your config is basically ok. > >> hope you can help me with this. > > Should be able to - the log showing a mail being downloaded from the > IMAP server will tell me. > hi! i think i solved the problem on my own: i used the '-a' option in my local fetchmail command: /bin/su wolfgang -c '/usr/bin/fetchmail -a -f /home/wolfgang/.fetchmailrc -d 300 -L /home/wolfgang/fetchmail.log 2>&1' and i think this confused the "keep" option in my .fetchmailrc. i tested a few mailsendings and everything seems to run fine. i also do not get the message fetchmail: restarting fetchmail (/home/USER/.fetchmailrc changed) Both fetchall and keep on in daemon mode is a mistake! fetchmail: starting fetchmail 6.3.4 daemon the messages remain on the server and only unseen messages are beeing fetched!! thx a lot for the help! greets snIP3r |
From: Rob M. <rob...@gm...> - 2006-10-12 18:27:29
|
On 10/12/06, longbow <lo...@gm...> wrote: > here it is: > poll MAILSERVER1 protocol IMAP user "MAILBOXUSER1" password "PWD1" > is LOCALUSER keep > poll MAILSERVER2 protocol POP3 user "MAILBOXUSER2" password "PWD2" ssl > is LOCALUSER Looks fine. > fetchmail --nosyslog -v -v Should have been more explicit - can you provide that for a run showing a mail being downloaded. That way we can confirm fetchmail's actions. > fetchmail --configdump Thanks, that shows your config is basically ok. > hope you can help me with this. Should be able to - the log showing a mail being downloaded from the IMAP server will tell me. -- 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 |