Re: [fetchmail-devel] RFC: Workaround for comcast bug - 6.3.X or 6.4.X stuff?

[Matthias A. <mat...@gm...>]

Rob MacGregor <rob...@gm...> writes:

> On 04/01/06, Matthias Andree <mat...@gm...> wrote:
>> Greetings,
>>
>> I prepared this patch in response to the many comcast ("Maillennium")
>> problem reports all across the net, which blacklists the POP3 TOP
>> command on servers that greet us with "Maillennium POP3/PROXY server".
>>
>> I'm asking for comments: do others think avoiding the truncation of
>> messages after approx. 82 kB justifies this incompatible bug fix (it is
>> incompatible because it marks messages read on the server)?
>
> I think that, assuming the warning is logged every time fetchmail
> starts up (ie once in daemon mode, every time when run by hand), then
> this isn't a bad thing.

Well, the warning is logged every time. After all, we want to annoy
users a bit and have them pester Comcast.

> Of course, I'm not the one doing the coding, so I don't have to suffer
> the mess that'll result :)

No, but you keep pointing people to the FAQ and --fetchall otherwise :-)

>> (I'd like to post a prominent notice referring them to our FAQ and lists.)
>
> How about including the URLs of the FAQ and the lists in the output of
> the help output, and the FAQ URL above the output of "fetchmail -v -v"
> and above?

Sounds reasonable.

> Probably wouldn't hurt to include the URL for the FAQ in the man page,
> at the top (yes, the fetchmail page URL is at the bottom, but who
> reads that far?).  Also at the bottom of the list footer?  Ram it in
> their faces :-)

My plan.

> Finally, I think that as long as ESRs page exists and makes no
> reference to the new project, there are going to be problems.

Yes, but we cannot do much about that except grab a phonebook and call
him up. At least this procedure worked with bogofilter at some point in
time...

-- 
Matthias Andree