Menu
▾
▴
fetchmail-users
|
From: Chris <cpo...@ea...> - 2007-03-21 01:59:03
|
I reported this back on the 11th of March, since then I've upgraded to what I understand is the latest version. Looking at the required information for a problem in the FAQ I'll try to provide it: 1. Your operating system Mandrake Linux 10.1 (Official) kernel 2.6.8.1-12mdk 2. Your compiler version, if you built from source; otherwise, the name and origin of the RPM or other binary package you installed. gcc (GCC) 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk) (hopfully this is whats being asked for, this came from my config.log) 3. A copy of your POP or IMAP server's greeting line. 220-elasmtp-masked.atl.sa.earthlink.net ESMTP Exim 4.34 #1 Tue, 20 Mar 2007 20:22:57 -0400.. 220-NO UCE. EarthLink does not authorize the use of its computers or network.. 220 equipment to accept, transmit, or distribute unsolicited e-mail.. (I hope the above is whats wanted) . 4. The name and version of the SMTP listener or MDA you are forwarding to. Procmail 3.22 5. Any command-line options you used. I usually just use $fetchmail -m procmail 6. The output of fetchmail -V called with whatever other command-line options you used. (I've added in the -v -v -v yesterday evening) [chris@cpollock ~]$ fetchmail -V -v -v -v -m procmail This is fetchmail release 6.3.7+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 Sunil Shetye Copyright (C) 2005-2007 Matthias Andree 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 cpollock 2.6.8.1-12mdk #1 Fri Oct 1 12:53:41 CEST 2004 i686 AMD Sempron(tm) Processor 2800+ unknown GNU/Linux Taking options from command line and /home/chris/.fetchmailrc Poll interval is 120 seconds Idfile is /home/chris/.fetchids Progress messages will be logged via syslog Fetchmail will forward misaddressed multidrop messages to cpollock. Fetchmail will direct error mail to the postmaster. Options for retrieving from cpo...@po...: True name of server is pop.earthlink.net. This host will be queried when no host is specified. Password = "*********". Protocol is POP3 (using default port). All available authentication methods will be tried. Server nonresponse timeout is 180 seconds. 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 disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) No received-message limit (--fetchlimit 0). Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4). No SMTP message batch limit (--batchlimit 0). No forced expunges (--expunge 0). Messages will be delivered with "procmail". Spam-blocking disabled No pre-connection command. No post-connection command. Single-drop mode: 1 local name recognized. cpollock No interface requirement specified. No monitor interface specified. No plugin command specified. No plugout command specified. No UIDs saved from this host. No poll trace information will be added to the Received header. The below headers are for the message that was downloaded over 50 times yesterday without being deleted from earthlinks server, I had to manually delete it. Return-Path: <tod...@lo...> Received: from pop00.earthlink.net [209.86.93.201] by localhost.localdomain with POP3 (fetchmail-6.3.7) for <cpollock@localhost> (single-drop); Mon, 19 Mar 2007 15:07:01 -0500 (CDT) Received: from noehlo.host ([127.0.0.1]) by mx-mcdonald.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP id 1hto6T1sB3Nl36F0; Mon, 19 Mar 2007 16:05:39 -0400 (EDT) Received: from localhost ([62.97.195.108]) by mx-mcdonald.atl.sa.earthlink.net (EarthLink SMTP Server) with SMTP id 1hto6QAx3Nl36F0 for <cpo...@ea...>; Mon, 19 Mar 2007 16:05:39 -0400 (EDT) Message-ID: <000001c76a61$9820b200$0100007f@localhost> From: "Arthur Davis" <tod...@lo...> To: <cpo...@ea...> Subject: Photoshop, Windows, Office Date: Mon, 19 Mar 2007 21:08:30 +0100 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2520 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.0000 X-ELNK-Info: sbv=0; sbrc=.0; sbf=00; sbw=000; X-SenderIP: 62.97.195.108 X-ASN: ASN-8542 X-CIDR: 62.97.192.0/18 One other thing of note, Mar 19 15:07:17 localhost spamd[22069]: dkim: lookup failed: DNS query timeout for _policy._domainkey.localwebshopping.com Mar 19 15:11:25 localhost spamd[22069]: dkim: lookup failed: DNS query timeout for _policy._domainkey.localwebshopping.com The above was logged every time fetchmail poll'd the server. I doubt whether its a fetchmail problem but maybe someone can give me a clue as to what may be the cause. The happens very seldom but when it does the bad message blocks all other message downloads except itself. Thanks, and I hope I provided the correct information above. If I didn't someone please let me know what I should have included. Chris -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-21 08:06:35
|
On 3/21/07, Chris <cpo...@ea...> wrote:
> I reported this back on the 11th of March, since then I've upgraded to what I
> understand is the latest version. Looking at the required information for a
> problem in the FAQ I'll try to provide it:
Thanks for all that. Typically there was still one thing that the FAQ
doesn't ask for that would have helped :) Can you provide the output
of "fetchmail -v -v -v -m procmail" for the problem email (that
should, hopefully, show what's happening).
You may find that enabling UIDL support helps as it moves to problem
of tracking seen emails from the server to fetchmail.
It may be that the problem will go away if you don't use "-m procmail"
but deliver directly to your SMTP server, but that's just a guess.
--
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 <cpo...@ea...> - 2007-03-21 23:51:49
|
On Wednesday 21 March 2007 2:04 am, Rob MacGregor wrote: > On 3/21/07, Chris <cpo...@ea...> wrote: > > I reported this back on the 11th of March, since then I've upgraded to > > what I understand is the latest version. Looking at the required > > information for a problem in the FAQ I'll try to provide it: > > Thanks for all that. Typically there was still one thing that the FAQ > doesn't ask for that would have helped :) Can you provide the output > of "fetchmail -v -v -v -m procmail" for the problem email (that > should, hopefully, show what's happening). > > You may find that enabling UIDL support helps as it moves to problem > of tracking seen emails from the server to fetchmail. > > It may be that the problem will go away if you don't use "-m procmail" > but deliver directly to your SMTP server, but that's just a guess. Robb, I tried replying to this last night, when I got home from work today I had this: The message's content type was not explicitly allowed Along with the signed message I'd sent encapsulated. I guess signed messages are no longer allowed? Anyway, here is what I sent: Thanks Rob, I'll have to wait until another message gets stuck on the server at earthlink to send the output. I did change logging from syslog to a seperate fetchmaillog file, that should make things easier when it happens again. I've also enabled uidl. One probably dumb question though, when you say "don't use "-m procmail" but deliver directly to your SMTP server" what do you mean? Chris -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-21 23:56:31
|
On 3/21/07, Chris <cpo...@ea...> wrote:
>
> Robb, I tried replying to this last night, when I got home from work today I
> had this:
>
> The message's content type was not explicitly allowed
>
> Along with the signed message I'd sent encapsulated. I guess signed messages
> are no longer allowed?
There's been a problem of people sending HTML only emails to the list
lately, resulting in the allowed types being clamped down on. If you
can did out the MIME type for the signed email I'll see about adding
it to the list of allowed types.
> Anyway, here is what I sent:
>
> Thanks Rob, I'll have to wait until another message gets stuck on the server
> at earthlink to send the output. I did change logging from syslog to a
> seperate fetchmaillog file, that should make things easier when it happens
> again. I've also enabled uidl. One probably dumb question though, when you
> say "don't use "-m procmail" but deliver directly to your SMTP server" what
> do you mean?
Well, by default fetchmail will try to connect to an SMTP on loopback.
If you're running an SMTP server
(sendmail/postfix/exim/qmail/whatever) then you can have fetchmail
just pass the email on to it.
(If that's equally as clear as mud let me know - it's getting a late here :>)
--
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 <cpo...@ea...> - 2007-03-22 02:39:19
|
On Wednesday 21 March 2007 5:54 pm, Rob MacGregor wrote: > On 3/21/07, Chris <cpo...@ea...> wrote: > > Robb, I tried replying to this last night, when I got home from work > > today I had this: > > > > The message's content type was not explicitly allowed > > > > Along with the signed message I'd sent encapsulated. I guess signed > > messages are no longer allowed? > > There's been a problem of people sending HTML only emails to the list > lately, resulting in the allowed types being clamped down on. If you > can did out the MIME type for the signed email I'll see about adding > it to the list of allowed types. I'll have to see if I can figure it out. This is probably not it but according to Kmail its OpenPGP/MIME. > > > Anyway, here is what I sent: > > > > Thanks Rob, I'll have to wait until another message gets stuck on the > > server at earthlink to send the output. I did change logging from syslog > > to a seperate fetchmaillog file, that should make things easier when it > > happens again. I've also enabled uidl. One probably dumb question though, > > when you say "don't use "-m procmail" but deliver directly to your SMTP > > server" what do you mean? > > Well, by default fetchmail will try to connect to an SMTP on loopback. > If you're running an SMTP server > (sendmail/postfix/exim/qmail/whatever) then you can have fetchmail > just pass the email on to it. > > (If that's equally as clear as mud let me know - it's getting a late here > :>) I have courier-imap running and have Kmail setup using an IMAP account. Procmail tosses into the maildir folders I have setup. -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-22 08:01:46
|
On 3/22/07, Chris <cpo...@ea...> wrote:
> I think though that the key may be the "socket error while fetching from
> cpo...@po...". It appears to my untrained eye that the
> connection was dropped while fetching this particular message?
Yes, and if it (the dropping of the connection upon issuing the DEL
command) happens each time with the same email then I'd suspect that
their POP server is badly broken.
> I also see, I
> think, how UIDL comes into play. Each message is assigned a unique ID. For
> instance, the 'bad' message above has an UIDL of 1huc3u2DT3Nl36v1, and
> looking at the .fetchids file I see cpo...@po...
> 1huc3u2DT3Nl36v1. Once I delete that message from the server the .fetchids
> file is removed since all messages have been downloaded. Makes sense.
Glad it's all working for you.
--
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 <cpo...@ea...> - 2007-03-22 11:55:50
|
On Thursday 22 March 2007 2:00 am, Rob MacGregor wrote: > On 3/22/07, Chris <cpo...@ea...> wrote: > > I think though that the key may be the "socket error while fetching from > > cpo...@po...". It appears to my untrained eye that the > > connection was dropped while fetching this particular message? > > Yes, and if it (the dropping of the connection upon issuing the DEL > command) happens each time with the same email then I'd suspect that > their POP server is badly broken. Everything at Earthlink is badly broken, mail, usenet, techsupport and so forth. > > > I also see, I > > think, how UIDL comes into play. Each message is assigned a unique ID. > > For instance, the 'bad' message above has an UIDL of 1huc3u2DT3Nl36v1, > > and looking at the .fetchids file I see cpo...@po... > > 1huc3u2DT3Nl36v1. Once I delete that message from the server the > > .fetchids file is removed since all messages have been downloaded. Makes > > sense. > > Glad it's all working for you. Me too Rob, and thanks very much for your help. I've the FAQ bookmarked now and if/when I have another problem thats the very *first* place I'll check for a solution. -- Chris KeyID 0xE372A7DA98E6705C |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X