[Dovecot] Dovecot - T-Bird - RETR command failed
calvin.gordon at sasktel.net
Thu Aug 28 19:06:26 EEST 2008
This morning during another RETR command error in T-Bird i got the
following info from the use/maildir/cur directory
[root at mailserver cur]# ls -lh
-rw------- 1 username users 35K 2008-08-27 13:57
-rw------- 1 username users 821 2008-08-27 14:17
-rw------- 1 username users 20K 2008-08-27 19:01
-rw------- 1 username users 50K 2008-08-27 19:05
-rw------- 1 username users 3.0K 2008-08-27 21:42
What is the "'S" behind the offending file name ?
What is the ",S" behind the offending filenane ?
I also did a head on the offending file (edited to protect the confused)
[root at mailserver cur]# head
Return-Path: <aprimo.americas.bounces at autodeskcommunications.com>
X-Original-To: firstname.lastname at company.com
Delivered-To: firstname.lastname at company.com
Received: from aprimo-relay2.autodesk.com (aprimo-relay2.autodesk.com
by mailserver.company.com (Postfix) with ESMTP id 0B52C2D844B
for <firstname.lastname at company.com>; Wed, 27 Aug 2008 13:57:24 -0600 (CST)
Received: from APRPRDAPP04.ads.autodesk.com (aprprdapp04.autodesk.com
by aprimo-relay2.autodesk.com (8.13.0/8.12.6) with ESMTP id m7RJvNvN006344
for <firstname.lastname at company.com>; Wed, 27 Aug 2008 12:57:24 -0700 (PDT)
Received: from mail pickup service by APRPRDAPP04.ads.autodesk.com with
Timo Sirainen wrote:
> On Tue, 2008-08-26 at 13:42 -0600, Calvin Gordon wrote:
>> I have recently installed new untangle firewalls ( untangle.com) in
>> Bridge mode at two office locations. Both offices collect mail from a
>> Fedora 9, postfix,dovecot server at location #1. Since the install of
>> the untangles i have been plagued by Thunderbird Errors while trying to
>> POP email.
> That strongly implies the problem is with the new firewalls.
>> Aug 26 13:58:41 mailserver dovecot: POP3(username): Connection closed
>> top=0/0, retr=1/6987, del=0/1, size=6970
> Dovecot sees that the connection gets closed unexpectedly. Most likely
> by the firewall that was inspecting the POP3 traffic and found something
> it didn't like (or caused it to hit a bug or something).
> The problem probably goes away if you enable SSL. Or maybe you could
> configure the firewalls not to look inside the POP3 traffic.
More information about the dovecot