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. The error says "RETR" command failed. If the user logs into the webmail (Squirrelmail) on the mail server and cleans out his inbox by deleting all existing mail, T-Bird starts operating again. This error has repeated itself without a pattern i can identify dozens of time over the last few weeks. No other email client displays errors. T-Bird = 2.0.0.16 on XP or Vista OS UT = 5.3.0~svn20080624r1690release5.3-1sarge Dovecot = Version : 1.0.15, Release : 10.fc9 Postfix = Version : 2.5.1, Release : 2.fc9 Dovecot tail -f maillog | grep 'username' Aug 6 13:37:06 mailserver1 dovecot: pop3-login: Login: user=<username>, method=PLAIN, rip=::ffff:128.1.1.5, lip=::ffff:128.1.1.10 Aug 6 13:37:07 mailserver1 dovecot: POP3(username): Disconnected top=0/0, retr=1/2287, del=0/1, size=2270 Has anyone else seen this issue with T-Bird ? Cal G
Update My mailog post was from an older box, probbaly the same info anyways, but here's a new one. Aug 26 13:58:41 mailserver dovecot: pop3-login: Login: user=<username>, method=PLAIN, rip=::ffff:128.1.1.5, lip=::ffff:128.1.1.10 Aug 26 13:58:41 mailserver dovecot: POP3(username): Connection closed top=0/0, retr=1/6987, del=0/1, size=6970 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. > > The error says "RETR" command failed. If the user logs into the > webmail (Squirrelmail) on the mail server and cleans out his inbox by > deleting all existing mail, T-Bird starts operating again. This error > has repeated itself without a pattern i can identify dozens of time > over the last few weeks. > > No other email client displays errors. > > T-Bird = 2.0.0.16 on XP or Vista OS > UT = 5.3.0~svn20080624r1690release5.3-1sarge > Dovecot = Version : 1.0.15, Release : 10.fc9 > Postfix = Version : 2.5.1, Release : 2.fc9 > > Dovecot > tail -f maillog | grep 'username' > > Aug 6 13:37:06 mailserver1 dovecot: pop3-login: Login: > user=<username>, method=PLAIN, rip=::ffff:128.1.1.5, > lip=::ffff:128.1.1.10 > Aug 6 13:37:07 mailserver1 dovecot: POP3(username): Disconnected > top=0/0, retr=1/2287, del=0/1, size=2270 > > Has anyone else seen this issue with T-Bird ? > > > > > Cal G >
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=6970Dovecot 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20080827/8ea792ea/attachment-0002.bin>
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 total 3.1M -rw------- 1 username users 35K 2008-08-27 13:57 1219867052.V811I47642dM988688.mailserver.company.com:2,S -rw------- 1 username users 821 2008-08-27 14:17 1219868229.V811I476525M88463.mailserver.company.com:2, -rw------- 1 username users 20K 2008-08-27 19:01 1219885307.V811I476533M802748.mailserver.company.com:2, -rw------- 1 username users 50K 2008-08-27 19:05 1219885504.V811I47654eM965583.mailserver.company.com:2, -rw------- 1 username users 3.0K 2008-08-27 21:42 1219894942.V811I47655aM486415.mailserver.company.com:2, 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 1219867052.V811I47642dM988688.mailserver.company.com:2\,S 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 [198.102.112.80]) 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 [144.111.34.44]) 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 Microsoft SMTPSVC; Cal G 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. > >