Exchange
m |
m (→External Links) |
||
(22 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
− | =SMTP/IMAP= | + | [[Image:Xbill.png|thumb|160px|right|Screenshot of [http://en.wikipedia.org/wiki/XBill XBill]]] |
+ | Fun with ''Microsoft Exchange''. | ||
+ | |||
+ | <!-- =SMTP/IMAP= | ||
==Staff== | ==Staff== | ||
Here are the current settings for SMTP and IMAP to access staff email | Here are the current settings for SMTP and IMAP to access staff email | ||
− | smtp-server=lupin.shu.ac.uk/user=shu\ | + | # old setting: smtp-server=lupin.shu.ac.uk/user=shu\engjw3 |
+ | smtp-server=cedar.shu.ac.uk:587/user=engjw3/novalidate-cert/tls | ||
incoming-folders=my.email@shu.ac.uk {exchange.shu.ac.uk:143/imap/user=shu\myusername}inbox | incoming-folders=my.email@shu.ac.uk {exchange.shu.ac.uk:143/imap/user=shu\myusername}inbox | ||
Line 9: | Line 13: | ||
Here are the current settings for SMTP and POP3 to access student email | Here are the current settings for SMTP and POP3 to access student email | ||
− | smtp-server= | + | smtp-server=hera.shu.ac.uk/user=jwedekin |
incoming-folders=my.email@student.shu.ac.uk {hera.shu.ac.uk/pop3/user=myusername}inbox | incoming-folders=my.email@student.shu.ac.uk {hera.shu.ac.uk/pop3/user=myusername}inbox | ||
+ | |||
+ | Here are the IMAP settings for upcoming Google mail for students | ||
+ | incoming-folders=my.email@my.shu.ac.uk {pop.gmail.com/imap/ssl/novalidate-cert/user=myusername@my.shu.ac.uk}inbox, | ||
+ | |||
+ | --> | ||
=Exchange protocol bugs= | =Exchange protocol bugs= | ||
Line 16: | Line 25: | ||
==Failure of plain authentication== | ==Failure of plain authentication== | ||
− | You get the following error message: ''Retrying PLAIN authentication after AUTHENTICATE failed''. This is because Microsoft Exchange protocol mistakenly advertises plain authentication even though it does not support it. You need to | + | You get the following error message: ''Retrying PLAIN authentication after AUTHENTICATE failed''. This is because Microsoft Exchange protocol mistakenly advertises plain authentication even though it does not support it. You need to force the email client to ignore this. E.g. with ''alpine'' |
disable-these-authenticators=PLAIN | disable-these-authenticators=PLAIN | ||
==Kerberos authentification failure== | ==Kerberos authentification failure== | ||
− | You get the following error messages: ''Unknown Kerberos failure: An invalid name was supplied'' and ''Kerberos mechanism status: Hostname cannot be canonicalized''. This is because Microsoft Exchange protocol mistakenly advertises kerberos authentication even though it does not support it. | + | You get the following error messages: ''Unknown Kerberos failure: An invalid name was supplied'' and ''Kerberos mechanism status: Hostname cannot be canonicalized''. This is because Microsoft Exchange protocol mistakenly advertises kerberos authentication even though it does not support it. E.g. ''alpine'' users need to add this option |
disable-these-authenticators=GSSAPI | disable-these-authenticators=GSSAPI | ||
==Workaround both problems== | ==Workaround both problems== | ||
− | To work around both problems you need to disable plain authentication as well as Kerberos host authentication | + | To work around both problems you need to disable plain authentication as well as Kerberos host authentication. E.g. with ''alpine'' |
disable-these-authenticators=PLAIN,GSSAPI | disable-these-authenticators=PLAIN,GSSAPI | ||
+ | |||
+ | ==Message to save shrank!== | ||
+ | You get the following error message: ''Message to save shrank!''. This is because [http://objectmix.com/pine/205808-message-save-shrank-2.html Exchange server often does not compute the message size properly] (also see [http://www.washington.edu/alpine/changes/1.00-to-1.10.html alpine changelog]). To the email client this looks like the message was not transferred completely. ''alpine'' users need to upgrade to a recent version which allows you to ignore this error and proceed with saving the message. | ||
+ | |||
+ | =External Links= | ||
+ | * [http://www.washington.edu/alpine/ Alpine Messaging System] | ||
+ | ** [http://business-php.com/opensource/ez-pine-gpg/ Script for using PGP with Alpine] | ||
+ | ** [http://ubuntuforums.org/showthread.php?t=710101 Saving passwords with Alpine] | ||
+ | * [http://www.computerperformance.co.uk/exchange2003/exchange2003_SMTP_Auth_Login.htm How to troubleshoot Microsoft Exchange Server 2003] | ||
+ | * [https://esp.shu.ac.uk/pwm/ SHU password self-service] | ||
+ | |||
+ | [[Category:General]] |
Latest revision as of 20:55, 12 January 2011
Fun with Microsoft Exchange.
Contents |
[edit] Exchange protocol bugs
Microsoft Exchange server has several protocol bugs which you may need to work around.
[edit] Failure of plain authentication
You get the following error message: Retrying PLAIN authentication after AUTHENTICATE failed. This is because Microsoft Exchange protocol mistakenly advertises plain authentication even though it does not support it. You need to force the email client to ignore this. E.g. with alpine
disable-these-authenticators=PLAIN
[edit] Kerberos authentification failure
You get the following error messages: Unknown Kerberos failure: An invalid name was supplied and Kerberos mechanism status: Hostname cannot be canonicalized. This is because Microsoft Exchange protocol mistakenly advertises kerberos authentication even though it does not support it. E.g. alpine users need to add this option
disable-these-authenticators=GSSAPI
[edit] Workaround both problems
To work around both problems you need to disable plain authentication as well as Kerberos host authentication. E.g. with alpine
disable-these-authenticators=PLAIN,GSSAPI
[edit] Message to save shrank!
You get the following error message: Message to save shrank!. This is because Exchange server often does not compute the message size properly (also see alpine changelog). To the email client this looks like the message was not transferred completely. alpine users need to upgrade to a recent version which allows you to ignore this error and proceed with saving the message.