On Thu, Jul 26, 2001 at 09:54:05PM +0200, Joost Kooij wrote: | I could never figure out what went wrong, because when I sent the exchange | competence center people an smtp + pop3 dump illustrating the mangling, | they were completely baffled about the possibility of sending email with | telnet, so I gave up.
... | Umm, actually it doesn't or didn't. Fetchmail had to be patched to allow | incorrect pop3 "list" responses from a certain vendor's mail server, | because it reported not the actual message size, but the size of the | compressed entry in the mail database. It is also explained in the | fetchmail FAQ. | | When the company where this happened, tried to get some of the support | they were paying (very big time) for, there was no answer. So two bsd | gurus who were affected by this debugged it a bit and even found the likely | cause of the problem sent a patch to the fetchmail bazaar. | | Shortly after the patched version of fetchmail hit the net, the submitters | of the patch were contacted by an exchange developer. After some pounding | with rfc's, he agreed that it was a bug and gave a magic registry hack to | fix exchange, ie. one has to add a key called "pop3 compatibility" to be | compliant with the rfc's. LOL! Great story. Thanks Joost. | Since knowing about this, it has never been a doubt to me that open source | has better support than closed source, even if that's what you're actually | using. "What Every Retailer Should Know" ... (if you don't know what I am talking about search the debian-user archives to find a hilarious MS press release) -D