Hi,
Last summer Comcast changed its POP3 server to an ATT server that
truncates email when the POP3 TOP command is used with messages over
75-80 KB. This occurred in many areas including mine which is
Montgomery County, Maryland USA. I eventually identified a workaround
but in the meantime got nowhere with Comcast. The county's cable
office filed a complaint on my behalf. Comcast's response was that
they hadn't made any changes that would cause email truncation.
Their assertion was obviously false since I had provided a reproducer
which telnet's to port 110 and executes the TOP command. Comcast's
public relation reps told the county and me that they would look into
it but have done nothing over the last several months. The county
advised me of the County Cable Commission, a quasi-judicial body that
can order certain things of Comcast.
Since Comcast now is basically the only game in town I've decided to
go before the CCC to see if they can get Comcast to fix their POP3 bug
or at least have them admit that their system is broken and that it is
not fetchmail's problem. I am writing for a few reasons. To see if
anyone:
- has been impacted by this bug and if so, would be willing to
provide a written statement. You would not need to show up.
- would be willing to provide a sort of written expert statement that
there is a problem. Likewise, you would not need to show up. But you
would need to sign your name.
- has any Comcast material that says they provide POP3 server access
(they told me they don't "support" telnet ?! as a mail reader, only
Outlook and their webmail program).
- would like to be a party to the case
If you reply to me directly please indicate whether or not I may use
your name and email in the proceedings.
Jim Foley