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 |