aboutsummaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
...
* Ready to ship.Eric S. Raymond2001-02-071-0/+4
* We get a report on the diff size now.Eric S. Raymond2001-02-071-0/+2
* Ready to ship.Eric S. Raymond2001-02-071-1/+1
* Moved to MailMan.Eric S. Raymond2001-02-071-12/+8
* Good, we can get list statistics again.Eric S. Raymond2001-02-071-12/+4
* Initial revisionEric S. Raymond2001-02-071-0/+26
* Copy loop has monitoring and termination now.Eric S. Raymond2001-02-071-1/+12
* Initial revisionEric S. Raymond2001-02-071-0/+222
* First cut at ODMR support.Eric S. Raymond2001-02-0717-193/+138
* *Is* controlled by an option.Eric S. Raymond2001-02-071-2/+0
* Documentation patch.Eric S. Raymond2001-02-071-1/+1
* str -> chr.Eric S. Raymond2001-02-071-1/+1
* Ready to ship, but no ATRN.Eric S. Raymond2001-02-074-6/+33
* Cosmetic fix.Eric S. Raymond2001-02-071-5/+42
* Note the SIGPIPE problem.Eric S. Raymond2000-12-121-2/+10
* Minor corrections.Eric S. Raymond2000-12-121-1/+1
* Samuel Leo's LMTP enhancement.Eric S. Raymond2000-12-065-6/+43
* The retry patch.Eric S. Raymond2000-12-014-18/+55
* Minor bugfixes.Eric S. Raymond2000-12-016-17/+36
* Chip Salzenberg's patch.Eric S. Raymond2000-12-011-2/+4
* Correction.Eric S. Raymond2000-11-271-1/+2
* 5-6-0bis fix for smtpname.Eric S. Raymond2000-11-276-4/+15
* Ready to ship.Eric S. Raymond2000-11-261-0/+5
* Ready to ship a gold version.Eric S. Raymond2000-11-267-29/+26
* Make showdots work from the command line.Eric S. Raymond2000-11-241-1/+3
* Handle `principal' correctly.Eric S. Raymond2000-11-241-4/+4
* Ready to ship.Eric S. Raymond2000-11-1116-15/+125
generated by cgit v1.2.3 (git 2.46.0) at 2026-07-11 18:39:16 +0000
P 3 TOP commands, however Comcast has found that increasing the amount of data TOP returns beyond the value of 64K has a tendency to crash Microsoft Outlook Express when an abnormally large header is sent. Increasing the value beyond 64K would open the platform to malicious use of large headers that adversely impacts system performance. Virtually all of Comcast's high-speed Internet customers use Outlook Express. Comcast has not received requests from other subscribers who seek to use the TOP command in the manner you have requested. Further, Comcast has not received any other complaints regarding email truncation with the TOP command. Should you wish to continue checking your mail through manual commands you might try using the RETR command, which will return the entire message. ... Date: Fri, 5 Mar 2004 16:28:11 -0500 Mr. Foley: This is in response to your question regarding &quot;POP 3 RFC compliance.&quot; We have tried to answer your question about Comcast's services by talking about the specific application in which you are interested and how that application relates to technical information regarding the configuration of Comcast's Internet service. We have provided you all the information that we can by explaining that Comcast limits the optional POP 3 Top Command to a value of 64k because any larger value has a tendency to crash Microsoft Outlook and could leave Comcast's system open to the malicious use of large headers intended to impair system performance. The decision by Comcast to place limitations on the optional POP 3 TOP email commands is a technical business decision made by Comcast in the best interest of all its customers and its system. ... ... With respect to the specific RFC at issue, RFC 1939, POP 3, it is our understanding that it is a protocol &quot;intended to permit a workstation to dynamically access a maildrop on a server host in a useful fashion. Usually, this means that the POP3 protocol is used to allow a workstation to retrieve mail that the server is holding for it. Pop 3 is not intended to provide extensive manipulation operations of mail on the server.&quot; POP 3 was created in May 1996 and has not been revised since, despite the many changes in computer hardware and software related to handling of email since that time. In any event, the TOP command is identified as an optional POP 3 command in RFC 1939. ... </PRE> <!--endarticle--> <HR> <P><UL> <!--threads--> <LI> Previous message: <A HREF="008522.html">[fetchmail]fetchmail vs Maillenium; mail truncated to 80K </A></li> <LI> Next message: <A HREF="008524.html">[fetchmail]fetchmail vs Maillenium; mail truncated to 80K </A></li> <LI> <B>Messages sorted by:</B> <a href="date.html#8523">[ date ]</a> <a href="thread.html#8523">[ thread ]</a> <a href="subject.html#8523">[ subject ]</a> <a href="author.html#8523">[ author ]</a> </LI> </UL> </body></html>