[Dovecot] retr errors
My ISP uses Dovecot and I have had an ongoing problem for a while using several email clients.
Sometimes the response to a retr request is mal-formed. The expected response "+OK nnn octets" is not returned. The response looks like it started somewhere in the message headers.
Sometimes a retry can clear the problem but I usually need to delete the first message via a putty session.
The problem, when present, is always on the first message. Never seen it in the middle of a series of messages. This problem has been seen on different machines, different versions of Windows, at home and on the road.
I have wireshark traces showing good and bad sessions....
stat +OK 93 1000437 retr 1 +OK 6946 octets Return-path: .....
retr 1 of blahblah@blah.com designates 2607:f8b0:4001:c03::235 as permitted sender) smtp.mail=blahblah@blah.com; dkim=pass header.i=@blah.com Reply-To: android-developers@googlegroups.com Precedence: list Mailing-list: ......
My ISP has been non-helpful. Any ideas how I can track down the problem?
Thanks Bill
Hi Bill
You should send the wireshark traces to your ISP and ask him to fix it.
At least one would require the doveconf -n output and the version of dovecot. Probably a bug in an older dovecot version?
Regards Daniel
Hi Bill,
any intercepting virus scanner or personal firewall software between your mail client and the dovecot server?
Regards Daniel
On 10/6/2013 5:58 PM, Daniel Parthey wrote:
Hi Bill,
any intercepting virus scanner or personal firewall software between your mail client and the dovecot server?
Regards Daniel McAfee....
and the ISP wasn't interested in the wireshark traces.
I know, I should change the ISP and see if the problem goes away. :-)
Thanks
On 07/10/2013 11:19, Bill Morgan wrote:
On 10/6/2013 5:58 PM, Daniel Parthey wrote:
Hi Bill,
any intercepting virus scanner or personal firewall software between your mail client and the dovecot server?
Regards Daniel McAfee....
As I'm sure Daniel was implying, did you also test without these? Also, do they provide webmail? next time you get a stuck message, login to webmail and see if its OK there, try using only webmail for a week or two, if you have this trouble every day, you'll soon reproduce it, or rule out the ISP end.
and the ISP wasn't interested in the wireshark traces.
Baring in mind, that ISP tech support, is exactly that, "ISP, Tech Support" not Microsoft support, or apple support or whatever, the ISP can only support its services, not your local client software, if they can prove, and your ISP should have by process of elimination, for instance, webmail, you have no trouble, then they have ruled out an ISP related cause, and they are very within their rights to say "not our problem".
Also remember, engineers tend to act/get-involved when complaints are en-mass, its to their advantage to look at it then, IOW, the care factor will increase with multiple people exhibiting the same problem over a short or same period of time.
I know, I should change the ISP and see if the problem goes away. :-)
Sounds like a fair idea to me if you rule out everything on your end and can prove beyond doubt it is the ISP, else you'll just be moving the problem sideways, not up towards resolution.
W dniu 07.10.2013 03:33, Noel Butler pisze:
On 07/10/2013 11:19, Bill Morgan wrote:
On 10/6/2013 5:58 PM, Daniel Parthey wrote:
Hi Bill,
any intercepting virus scanner or personal firewall software between your mail client and the dovecot server?
Regards Daniel McAfee....
I would suggest temporaily disabling McAffle (might be not posssible without uninstaling it, at least its the case with norton and kaspersky) as from my personal experience AV suits tend to break mail transfers. AV's that i had problems with include Norton, Kaspersky, Avast ... We are not using McAffe here but it's probable that if mail filtering or Firewall/Internet security/Anti phishing is enabled, McAffe is intercepting Your mail en route and scanning it what might lead to errors.
As I'm sure Daniel was implying, did you also test without these? Also, do they provide webmail? next time you get a stuck message, login to webmail and see if its OK there, try using only webmail for a week or two, if you have this trouble every day, you'll soon reproduce it, or rule out the ISP end.
and the ISP wasn't interested in the wireshark traces.
Baring in mind, that ISP tech support, is exactly that, "ISP, Tech Support" not Microsoft support, or apple support or whatever, the ISP can only support its services, not your local client software, if they can prove, and your ISP should have by process of elimination, for instance, webmail, you have no trouble, then they have ruled out an ISP related cause, and they are very within their rights to say "not our problem".
Also remember, engineers tend to act/get-involved when complaints are en-mass, its to their advantage to look at it then, IOW, the care factor will increase with multiple people exhibiting the same problem over a short or same period of time.
I know, I should change the ISP and see if the problem goes away. :-)
Sounds like a fair idea to me if you rule out everything on your end and can prove beyond doubt it is the ISP, else you'll just be moving the problem sideways, not up towards resolution.
On 2013-10-06 9:19 PM, Bill Morgan <bill@bmorgan.com> wrote:
On 10/6/2013 5:58 PM, Daniel Parthey wrote:
Hi Bill,
any intercepting virus scanner or personal firewall software between your mail client and the dovecot server?
McAfee....
Well, I'd just stop right there, fire whoever installed Macafee, remove it, and install a real antivirus (ESET is my preferred, but *anything* but Macafee or Norton)...
--
Best regards,
*/Charles/*
participants (5)
-
Bill Morgan
-
Charles Marcus
-
Daniel Parthey
-
Noel Butler
-
Przemysław Orzechowski