We see the same, adding ~150Mbps of POP3 traffic on just one cluster. It started on 2016-04-18, but took about two weeks to grow, levelling off as of about 2016-05-01.
Probably a code update broke POP3 UIDL caching or the don't-redownload decision. I can't imagine it is entirely broken, or we'd see reports of duplication. Would it help for us to collect login sources or timestamps? It's not really hurting, but would be nice to fix...or auto-punt to IMAP. Simon- On Fri, May 27, 2016 at 06:56:08PM +0000, Kirk MacDonald wrote: > Sorry to drag up an older thread. Has there been any further discoveries on > this front? Based on our message store interface bps records I'd say this > behavior looks to have started April 17 or 18 2016. > > > Kirk MacDonald > System Administrator > Internet > Eastlink > > > -----Original Message----- > From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Michael Wise > Sent: Thursday, May 05, 2016 3:13 PM > To: mailop@mailop.org > Subject: Re: [mailop] Microsoft POP3 Troubles > > > Well, I got an answer, but am no further ahead as such. > I'd suggest treating them as a malfunctioning POP3 client and suggest ... > that they upgrade to IMAP4 instead? :) > It doesn't seem to be coming from an area that would suggest it's a rogue > tenant, but that cannot be completely ruled out. > > Please let me know if it turns out to be in any way actually malicious > instead of a misconfigure or timeout. > > Aloha, > Michael. _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
