-----Original Message-----
From: vikraman Poduval [SMTP:[EMAIL PROTECTED]]
Sent: Monday, April 24, 2000 9:36 PM
To: [EMAIL PROTECTED]
Subject: [LIH] Fetchmail with MS EXCHANGE
> dear Linux users,
> i have downloaded the fetchmail (5.3) source and recompiled with
>"--enable-NTLM" option. after configuring it is downloading all the mail
>from my pop account (multidrop). But fetcmail sends all downloaded mails to
>EXCG with a id <[EMAIL PROTECTED]> and exchange bounce-back the
>same. how do i resolve it.
Read what esr says about fetchmail and m$ sexchange in the fetchmail faq at
http://www.tuxedo.org/~esr/fetchmail - especially the last few paras.
S2. How can I use fetchmail with Microsoft Exchange?
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. Note: if you 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 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).
Somewhat belatedly, I've learned that there's supposed to be a registry bit
that can fix this breakage:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeIs\Parameters
System\Pop3 Compatibility
This is a bitmask that controls the variations from the standard protocol.
The bits defined are:
0x00000001:
Report exact message sizes for the LIST command
0x00000002:
Allow arbitrary linear whitespace between commands and arguments
0x00000004:
Enable the LAST command
0x00000008:
Allow an empty PASS command (needed for users with blank passwords, but
illegal in the protocol)
0x00000010:
Relax the length restrictions for arguments to commands (protocol requires
40, but some user names may be longer than that).
0x00000020:
Allow spaces in the argument to the USER command.
There's another one that may be useful to know about:
KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MsExchangeIs\Parameters
System\Pop3 Performance
0x00000001:
Render messages to a temporary stream instead of sending directly from the
database (should always be on)
0x00000002: Flag unrenderable messages (instead of just failing commands)
(should only be on if you are seeing the problems reported in KB Q168109)
0x00000004:
Return from the QUIT command before all messages have been deleted.
The Microsoft pod-person who revealed this information to me admitted that
he couldn't find it anywhere in their public knowledge base.
Another specific problem we have seen with Exchange servers has as its
symptom a response to LOGIN that says "NO Ambiguous Alias". Grant Edwards
writes: This means that Exchange Server is too f*&#ing stupid to figure out
which mailbox belongs to you. Instead of actually keeping track of which
inbox belongs to which user, it uses some half-witted, guess-o-matic
heuristic to try to guess your mailbox name from your username.
In your case it doesn't work because your username maps to more than one
mailbox. For some people it doesn't work because their username maps to zero
mailboxes. This is yet another inept, lame, almost criminally negligent
design decision from our friends in Redmond.
You've got several options:
Try giving fetchmail a username of "/NTDomain/NTUsername/MailboxName".
Get your administrator to configure the server so that usernames and mailbox
names are the same.
Get your administrator to add an alias that maps your username explicitly to
your mailbox name.
But, the best option involves a tactical nuclear weapon (an old ASROC will
do), pissing off a lot people who live downwind from Redmond, and your
choice of any Linux, NetBSD, FreeBSD, or Solaris CD.
I'll provide the CD.
Suresh Ramasubramanian [EMAIL PROTECTED]
-----------------------------------------------------------------------
For information on this and other Linux India mailing lists check out
http://lists.linux-india.org/
