How can I use fetchmail with Microsoft Exchange?
It’s been reliably reported that Exchange 2000’s POP3 support is so broken that it’s unusable. One symptom is that messages without a terminating newline get the POP3 message termination dot emitted — you guessed it — right after the last character of the message, with no terminating newline added. This will hang fetchmail or any other RFC-compliant server. IMAP is alleged to work OK, though. Older versions of Exchange are semi-usable. They randomly drop attachments on the floor, though. Microsoft acknowledges this as a known bug and apparently has no plans to fix it. Fetchmail using IMAP supports the proprietary NTLM mode used with M$ Exchange servers. To enable this, configure fetchmail with the –enable-NTLM option and recompile it. Specify a user option value that looks like `user@domain’: the part to the left of the @ will be passed as the username and the part to the right as the NTLM domain. M$ Exchange violates the POP3 and IMAP RFCs. Its LIST command does not reveal the real
It’s been reliably reported that Exchange 2000’s POP3 support is so broken that it’s unusable. One symptom is that messages without a terminating newline get the POP3 message termination dot emitted — you guessed it — right after the last character of the message, with no terminating newline added. This will hang fetchmail or any other RFC-compliant server. IMAP is alleged to work OK, though. Older versions of Exchange are semi-usable. They randomly drop atttachments on the floor, though. Microsoft acknowledges this as a known bug and apparently has no plans to fix it. Fetchmail using IMAP supports the proprietary NTLM mode used with M$ Exchange servers. To enable this, configure fetchmail with the –enable-NTLM option and recompile it. Specify a user option value that looks like `user@domain’: the part to the left of the @ will be passed as the username and the part to the right as the NTLM domain. M$ Exchange violates the POP3 and IMAP RFCs. Its LIST command does not reveal the rea
Fetchmail now supports the proprietary NTLM mode used with M$ Exchange servers. To enable this, configure fetchmail with the –enable-NTLM option and recompile it. M$ Exchange violates the POP3 RFCs. Its LIST command does not reveal the real sizes of mail in the pop mailbox, but the sizes of the compressed versions in the exchange mail database (thanks to Arjan De Vet and Guido Van Rooij for alerting us to this problem). Fetchmail works with M$ Exchange, despite this brain damage. Two features are compromised. One is that the –limit option will not work right (it will check against compressed and not actual sizes). The other is that a too-small SIZE argument may be passed to your ESMTP listener, assuming you’re using one (this should not be a problem unless the actual size of the message is above the listener’s configured length limit).
It’s been reliably reported that Exchange 2000’s POP3 support is so broken that it’s unusable. One symptom is that messages without a terminating newline get the POP3 message termination dot emitted — you guessed it — right after the last character of the message, with no terminating newline added. This will hang fetchmail or any other RFC-compliant server. IMAP is alleged to work OK, though. Older versions of Exchange are semi-usable. They randomly drop attachments on the floor, though. Microsoft acknowledges this as a known bug and apparently has no plans to fix it. Fetchmail using IMAP supports the proprietary NTLM mode used with M$ Exchange servers. To enable this, configure fetchmail with the –enable-NTLM option and recompile it. Specify a user option value that looks like ‘user@domain’: the part to the left of the @ will be passed as the username and the part to the right as the NTLM domain. M$ Exchange violates the POP3 and IMAP RFCs. Its LIST command does not reveal the real
M$ Exchange violates the POP3 RFCs. Its LIST command does not reveal the real sizes of mail in the pop mailbox, but the sizes of the compressed versions in the exchange mail database (thanks to Arjan De Vet and Guido Van Rooij for alerting us to this problem). Fetchmail works with M$ Exchange, despite this braindamage. Two features are compromised. One is that the –limit option will not work right (it will check against compressed and not actual sizes). The other is that a too-small SIZE argument may be passed to your ESMTP listener, assuming you’re using one (this should not be a problem unless the actual size of the message is above the listener’s configured length limit). If you want these fixed, go bug the Evil Empire. Or, better yet, install a real operating system on your server and run IMAP.
Related Questions
- I have spoken to Microsoft and they have advised that I can purchase Exchange, SharepOint and CRM on a monthly subscription basis. How can I purchase this agreement?
- Is F-Secure Anti-Virus for Microsoft Exchange compatible with F-Secure Policy Manager 7.0 on the same server?
- How can I use fetchmail with Microsoft Exchange?
