After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 201144 - NTLM auth for POP/IMAP (aka SPA)
NTLM auth for POP/IMAP (aka SPA)
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Dan Winship
Evolution QA team
evolution[IMAP] evolution[interop] ev...
: 214295 (view as bug list)
Depends on:
Blocks: 216290
 
 
Reported: 2001-01-15 22:08 UTC by Dan Winship
Modified: 2013-09-10 13:50 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Dan Winship 2001-01-15 22:08:15 UTC 
If we want to support NTLM (Exchange Server) authentication for POP and IMAP,
we need to grab the code from fetchmail to do that. (I don't know if this
is important at all. No one has asked for it yet...)
Comment 1 bliberatore 2001-09-04 18:45:41 UTC 
Ok, I'll ask for it, so I can access my Microsoft Exchange Server...
Comment 2 Dan Winship 2001-11-28 22:45:49 UTC 
*** bug 214295 has been marked as a duplicate of this bug. ***
Comment 3 Dan Winship 2001-11-28 22:48:30 UTC 
This is 90% written already.

Louie: add this to the interop tracking bug once that exists.
Comment 4 Andrew Thiessen 2001-12-10 08:36:44 UTC 
Hate to jump on this little bandwagon, but since QWest decided to
change everyone over from their service to MSN, I have had to go back
to using Outlook (cringe) as MSN requires SPA. MSN requiring SPA is
somewhat of a recent development, and conspiracy theorists will tell
you that they are afraid of Ximian ;-)
Comment 5 Not Zed 2002-02-06 02:40:51 UTC 
dan, still working on this?
Comment 6 Dan Winship 2002-02-06 03:11:22 UTC 
I haven't actually done any work specifically on NTLM for Camel.
The NTLM code is all in soup, it's just a matter of pulling it
out, probably making it use the DES and MD4 code from NSS instead
of its own (assuming NSS exports those routines?), and refactoring
it into the CamelSasl framework. If either of you has spare time,
feel free to grab the bug. I'm not going to get to it before 1.1.0.

(eltester has an account on lewdness.ximian.com with the same
password as on peabody that you can use to test.)
Comment 7 Dan Winship 2002-02-08 01:57:48 UTC 
Fixed in CVS. (I wrote and tested it against the 1.0 branch,
but none of the SASL stuff seems to have changed on HEAD, so it
should work...)