[7.400] My Astaro pop3 proxy ate an email

barkas · #1 (**permalink**) 03-18-2009, 02:48 PM

I use the pop3 proxy and fetch through fetchmail to another linux machine (of which the below is the mail log).

Code:

Mar 18 11:47:19 [postfix/smtpd] connect from localhost[127.0.0.1]
Mar 18 11:47:19 [postfix/smtpd] 627D327007: client=localhost[127.0.0.1]
Mar 18 11:47:19 [postfix/cleanup] 627D327007: message-id=<EXCHANGEHzNkJwBMMkk000a709f@exchange.ds1.interview-nss.com>
Mar 18 11:52:19 [fetchmail] reading message whoever@pop.1und1.de:1 of 39 (8457 octets) (log message incomplete)
Mar 18 11:52:19 [fetchmail] timeout after 300 seconds._
Mar 18 11:52:19 [postfix/smtpd] lost connection after DATA (8706 bytes) from localhost[127.0.0.1]
Mar 18 11:52:19 [postfix/smtpd] disconnect from localhost[127.0.0.1]
Mar 18 11:52:19 [fetchmail] socket error while fetching from whoever@pop.1und1.de_

I had to delete the mail by hand from the mail spool directory so I can receive mail again.

Now it works again, but I get this one:

Code:

Warning: Mail 0/27283-1-1237198645 not local, but no cluster configured

Unfortunately I deleted the email in question.

frickler · #2 (**permalink**) 03-18-2009, 03:38 PM

Deleting mail from spool doesn't work this way, because it's still referenced in the database. There is no need to do that anyway, because fetchmail will retrieve the mail next time it connects.
I've sent you an PM how to correct your database.

barkas · #3 (**permalink**) 03-18-2009, 03:49 PM

Quote:

Originally Posted by frickler

Deleting mail from spool doesn't work this way, because it's still referenced in the database. There is no need to do that anyway, because fetchmail will retrieve the mail next time it connects.
I've sent you an PM how to correct your database.

That's what I tried to tell you: fetchmail could not fetch the mail, and could not delete it either. The pop3proxy just froze the connection at that point, it seems.

My fetchmail tried to fetch that mail for 2 days.

frickler · #4 (**permalink**) 03-18-2009, 03:56 PM

Did the connection freeze before or after you've deleted the spoolfile? If the proxy can't read a spoolfile it sends "-ERR Can't read mail" and prints the warning message to the logfile.

barkas · #5 (**permalink**) 03-18-2009, 04:17 PM

Quote:

Originally Posted by frickler

Did the connection freeze before or after you've deleted the spoolfile? If the proxy can't read a spoolfile it sends "-ERR Can't read mail" and prints the warning message to the logfile.

Before that, without my help.

Deleting the spoolfile was the fix.

There must have been something inside that mail which the pop3proxy did not like. Alas, I deleted it.

barkas · #6 (**permalink**) 03-19-2009, 12:42 AM

It not only ate this mail (which was btw a customer survey from Microsoft), it did not delete it from the source pop3 server, so it instantly fetched it again after I deleted it, thereby blocking my mail system again.

On the positive side, I now have the mail and could open a support case.

frickler · #7 (**permalink**) 03-19-2009, 08:13 AM

Thats the intended behaviour of fetchmail to not delete mail which it can't fetch. Otherwise one really would have data loss if the pop3 server temporarily can't deliver the mail.
Can you please send me the mail as attachment to astaro (at) codefrickler (dot) de (this address is non-filtered)?

barkas · #8 (**permalink**) 03-19-2009, 10:38 AM

As home user, they don't allow me to open a case.

Even if it is basically a bug report.

You may be right, I don't think my fetchmail is set to delete if it can't fetch, but then the astaro did not even delete it from the target pop3 server, even though it prefetched normally and deleted the rest of the mails.

quite strange.

I sent you an email, but I'm not absolutely sure that the email I attached is the whole email, I took that one from the astaro mail spool, it could be, that it did not fetch the whole mail due to some error.