Re: some color definitions dont work
El día Saturday, September 18, 2010 a las 04:37:06PM -0700, Chip Camden escribió: Are you using more than 16 color specifications? No. The problem must be caused by the way the FreeBSD's port is compiling (or patching) the source. If I run ./configure --enable-smtp by hand the colors are working fine with the same .muttrc. I will bring this to the attention of the maintainer of this port in FreeBSD. Thanks (and don't top post :-)) Udo, this is with PORTNAME= mutt-devel PORTVERSION=1.5.19 will forward the original problem description later; Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/
Re: How to match all theaded emails excluding the first one?
On Sun, Sep 19, 2010 at 09:23:15AM +0800, Yue Wu wrote: Hi list, As title, I want to keep all of the topics, but delete all of the others. You can tag/search/delete responses using an heuristic expression, the simpler comes in my mind: ~s Re: If the emails are not too much, tag them using this expression and then perform a manually check. m. -- Cosa volete? Questo diavolo d'uomo ha sempre le tasche ripiene di argomenti irresistibili. -- Pierre Augustin Caron de Beaumarchais
Re: Authenticated Exchange SMTP server problem
On 19 Sep 2010, at 03:26, John J. Foster wrote: Does your /var/log/mail gives any more clues? On the client machine? Apparently I don't have one (this is a vanilla mutt build +tokyocabinet running on OS X. it's /private/var/log/mail.log on a MAC /var is symlinked to /private/var on OS X. At any rate, there is no mail.log.
Re: some color definitions dont work
El día Sunday, September 19, 2010 a las 08:16:23AM +0200, g...@unixarea.de escribió: El día Saturday, September 18, 2010 a las 04:37:06PM -0700, Chip Camden escribió: Are you using more than 16 color specifications? No. The problem must be caused by the way the FreeBSD's port is compiling (or patching) the source. If I run ./configure --enable-smtp by hand the colors are working fine with the same .muttrc. I will bring this to the attention of the maintainer of this port in FreeBSD. Thanks (and don't top post :-)) Udo, this is with PORTNAME= mutt-devel PORTVERSION=1.5.19 will forward the original problem description later; I have played around with the ./configure of the port: the original 'make WITH_MUTT_SMTP=yes' runs: ./configure --disable-fcntl \ --with-ssl=/usr/local \ --with-sharedir=/usr/local/share/mutt --with-docdir=/usr/local/share/doc/mutt --sysconfdir=/usr/local/etc \ --disable-warnings \ --enable-external-dotlock \ --enable-pop \ --enable-imap \ --enable-smtp \ --enable-flock \ --with-libiconv-prefix=/usr/local \ --with-idn \ --disable-gpgme \ --with-gss \ --enable-compressed \ --disable-hcache \ --prefix=/usr/local \ --mandir=/usr/local/man \ --infodir=/usr/local/info/ \ --build=i386-portbld-freebsd8.0 as well this run by hand produces the problem with the color: ./configure --enable-imap --enable-smtp --with-ssl=/usr/local --with-sharedir=/usr/local/share/mutt --with-docdir=/usr/local/share/doc/mutt --sysconfdir=/usr/local/etc --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ while this is fine (deleted --with-ssl=/usr/local from ./configure): ./configure --enable-imap --enable-smtp --with-sharedir=/usr/local/share/mutt --with-docdir=/usr/local/share/doc/mutt --sysconfdir=/usr/local/etc --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ Don't know what could cause this problem exactly concerning --with-ssl=/usr/local; HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/
Re: Authenticated Exchange SMTP server problem
On 18 Sep 2010, at 21:20, Michael Williams wrote: I'm trying to get mutt's smtp support to work with my department's new Exchange server. According to the current draft documentation, Thunderbird can be configured as follows: http://www.physics.ox.ac.uk/it/email/exchange/2010/ThunderbirdSetup.htm. I have confirmed that this configuration works. So, having read Kyle Wheeler's very useful post http://marc.info/?l=mutt-usersm=124285017604463w=2, I have turned the Thunderbird instructions into the following smtp_url: set smtp_url=smtp://m...@physics.ox.ac.uk@mail.physics.ox.ac.uk:587 With this configuration, when I send mail in mutt, the status bar says SSL connection using TLSv1/SSLv3 (AES128-SHA) (which sounds promising) then Authenticating (NTLM), then prompts me for my password. I give this, but after a suspiciously long delay ~10s, I get the error SASL authentication failed. I emphasize that the server appears to work as described in the instructions for configuring SMTP for Thunderbird. I'm using the same username and password in mutt. This is the same username and password I use to make the IMAP connection; I also have 'set imap_user=m...@physics.ox.ac.uk' and that works fine. The server is configured to check that mail is coming from a registered address, and I'm setting the From: header appropriately in mutt. I'm stumped. Does anyone have any ideas? In further testing, I have confirmed SMTP connections to this server work with msmtp. Here is my very short .msmtprc: defaults tls on tls_certcheck off account default host mail.domain.com from m...@domain.com auth on user m...@domain.com (Where domain.com is my real domain, etc.) This works on the command line as follows: $ echo hello | msmtp t...@test.com password for m...@domain.com at mail.domain.com: [I type my password] $ A full verbose log of the communication between msmtp and the server is at the end of this email. So I just want to translate that .msmtprc into a .muttrc. I have set smtp_url=smtp://william...@physics.ox.ac.uk@mail.physics.ox.ac.uk Does anyone know why this doesn't work (SASL authentication failed as described above)? To anticipate some questions, my installation of mutt was built with the necessary SSL/SASL support: +USE_SSL_OPENSSL -USE_SSL_GNUTLS +USE_SASL +USE_GSS (which makes sense as I am able to connect to this server via IMAPS:993.) Any ideas very welcome. msmtp log below. -- Mike $ echo hello | msmtp -v t...@domain.com ignoring system configuration file /Users/mike/.homebrew/Cellar/msmtp/1.4.20/etc/msmtprc: No such file or directory loaded user configuration file /Users/mike/.msmtprc using account default from /Users/mike/.msmtprc host = mail.domain.com port = 25 timeout = off protocol = smtp domain= localhost auth = choose user = m...@domain.com password = (not set) ntlmdomain= (not set) tls = on tls_starttls = on tls_trust_file= (not set) tls_crl_file = (not set) tls_fingerprint = (not set) tls_key_file = (not set) tls_cert_file = (not set) tls_certcheck = off tls_force_sslv3 = off tls_min_dh_prime_bits = (not set) tls_priorities= (not set) auto_from = off maildomain= (not set) from = m...@domain.com dsn_notify= (not set) dsn_return= (not set) keepbcc = off logfile = (not set) syslog= (not set) reading recipients from the command line -- 220 mail.physics.ox.ac.uk Microsoft ESMTP MAIL Service ready at Sun, 19 Sep 2010 18:19:25 +0100 -- EHLO localhost -- 250-mail.domain.com Hello -- 250-SIZE 20971520 -- 250-PIPELINING -- 250-DSN -- 250-ENHANCEDSTATUSCODES -- 250-STARTTLS -- 250-AUTH NTLM -- 250-8BITMIME -- 250-BINARYMIME -- 250 CHUNKING -- STARTTLS -- 220 2.0.0 SMTP server ready TLS certificate information: [snip certificate info] -- EHLO localhost -- 250-mail.domain.com Hello -- 250-SIZE 20971520 -- 250-PIPELINING -- 250-DSN -- 250-ENHANCEDSTATUSCODES -- 250-AUTH NTLM LOGIN -- 250-8BITMIME -- 250-BINARYMIME -- 250 CHUNKING password for m...@domaon.com at mail.domain.com: -- AUTH LOGIN -- 235 2.7.0 Authentication successful -- MAIL FROM:m...@domain.com -- RCPT TO:t...@domain.com -- DATA -- 250 2.1.0 Sender OK -- 250 2.1.5 Recipient OK -- 354 Start mail input; end with CRLF.CRLF -- hello -- . -- 250 2.6.0 47f24188-a0fe-4c12-bfb7-d9b102132...@exchange-cas2.physics.ox.ac.uk [InternalId=3817] Queued mail for delivery -- QUIT -- 221 2.0.0 Service closing transmission channel $ .
Re: GPG - Mailing list encryption
* christoph christ...@kluenter.de [Fri, Sep 17, 2010 at 10:53:55PM +0200] * Am Do, Sep 16, 2010 at 11:51:38 +0200 , schrieb the.real.ka...@gmail.com: Hello list, I am somehow clueless, I searched the web a lot regarding this topic but didn't find a clear statement. Therefore I ask on this list. I'm using mailing lists a lot, no problem so far. I'm also a big GPG user. Some mailing lists I'm on are using encryption too, in order to not have to re-encode the mails on the sever, the admins configured the mailing list in a way that you send an email to one address: secur...@foo.edu.fi for example, but the mail should be encrypted to all the users (which I know) on that list. I didn't figure out a way to manage that kind of lists. How would you do it? I prefer to ask before I start writing my own wrapper for GPG, maybe I miss something easy. In ~/.gnupg/gpg.conf: group 0x=KEYID1 group 0x=KEYID2 group 0x=KEYID3 in muttrc: crypt-hook secur...@foo.edu.fi 0x Hey, thx, looks very promising. Somehow it is not working, and I don't find much information about this crypto-hook. What version is it working with? Do you have more information about that hook, maybe a link to the documentation, which I couldn't find? So I could investigate why it is not running on my own. But its quite hard to keep track of all the keys to use. Yeah, true, but I have a pla for that. Thanks for ypur help, the real kabel
Re: GPG - Mailing list encryption
Hi mutt users, * the.real.ka...@gmail.com the.real.ka...@gmail.com [19. Sep. 2010]: * christoph christ...@kluenter.de [Fri, Sep 17, 2010 at 10:53:55PM +0200] * Am Do, Sep 16, 2010 at 11:51:38 +0200 , schrieb the.real.ka...@gmail.com: Some mailing lists I'm on are using encryption too, in order to not have to re-encode the mails on the sever, the admins configured the mailing list in a way that you send an email to one address: secur...@foo.edu.fi for example, but the mail should be encrypted to all the users (which I know) on that list. I didn't figure out a way to manage that kind of lists. How would you do it? I prefer to ask before I start writing my own wrapper for GPG, maybe I miss something easy. In ~/.gnupg/gpg.conf: group 0x=KEYID1 group 0x=KEYID2 group 0x=KEYID3 in muttrc: crypt-hook secur...@foo.edu.fi 0x Hey, thx, looks very promising. Somehow it is not working, and I don't find much information about this crypto-hook. What version is it working with? It's standard mutt at least since v 1.5.20 but I don't know how long this feature exists. Do you have more information about that hook, maybe a link to the documentation, which I couldn't find? So I could investigate why it is not running on my own. This is the documentation from the mutt manual: http://www.mutt.org/doc/devel/manual.html#crypt-hook 21.Choosing the Cryptographic Key of the Recipient Usage: crypt-hook pattern keyid When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a certain key with a given e-mail address automatically, either because the recipient's public key can't be deduced from the destination address, or because, for some reasons, you need to override the key Mutt would normally use. The crypt-hook command provides a method by which you can specify the ID of the public key to be used when encrypting messages to a certain recipient. The meaning of keyid is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. This is the documentation from the gpg man page: http://www.gnupg.org/documentation/manuals/gnupg-devel/GPG-Key-related-Options.html --group name=value1 Sets up a named group, which is similar to aliases in email pro‐ grams. Any time the group name is a recipient (-r or --recipient), it will be expanded to the values specified. Multiple groups with the same name are automatically merged into a single group. The values are key IDs or fingerprints, but any key description is accepted. Note that a value with spaces in it will be treated as two different values. Note also there is only one level of expan‐ sion --- you cannot make an group that points to another group. When used from the command line, it may be necessary to quote the argument to this option to prevent the shell from treating it as multiple arguments. So basically you tell mutt to call gpg with an group name as recipient and gpg expands the group name to a list of recipients. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-
Re: Authenticated Exchange SMTP server problem
On Saturday, 18 September 2010 at 21:20, Michael Williams wrote: Hi, I'm trying to get mutt's smtp support to work with my department's new Exchange server. According to the current draft documentation, Thunderbird can be configured as follows: http://www.physics.ox.ac.uk/it/email/exchange/2010/ThunderbirdSetup.htm. I have confirmed that this configuration works. So, having read Kyle Wheeler's very useful post http://marc.info/?l=mutt-usersm=124285017604463w=2, I have turned the Thunderbird instructions into the following smtp_url: set smtp_url=smtp://m...@physics.ox.ac.uk@mail.physics.ox.ac.uk:587 With this configuration, when I send mail in mutt, the status bar says SSL connection using TLSv1/SSLv3 (AES128-SHA) (which sounds promising) then Authenticating (NTLM), then prompts me for my password. I give this, but after a suspiciously long delay ~10s, I get the error SASL authentication failed. If your mutt was built with --enable-debug (mutt -v will include the line +DEBUG if so), you can run mutt -d2 to get a trace of mutt's conversation with the SMTP server in ~/.muttdebug0. There should be more clues in there.
Re: Authenticated Exchange SMTP server problem
On Sunday, 19 September 2010 at 13:40, Brendan Cully wrote: On Saturday, 18 September 2010 at 21:20, Michael Williams wrote: Hi, I'm trying to get mutt's smtp support to work with my department's new Exchange server. According to the current draft documentation, Thunderbird can be configured as follows: http://www.physics.ox.ac.uk/it/email/exchange/2010/ThunderbirdSetup.htm. I have confirmed that this configuration works. So, having read Kyle Wheeler's very useful post http://marc.info/?l=mutt-usersm=124285017604463w=2, I have turned the Thunderbird instructions into the following smtp_url: set smtp_url=smtp://m...@physics.ox.ac.uk@mail.physics.ox.ac.uk:587 With this configuration, when I send mail in mutt, the status bar says SSL connection using TLSv1/SSLv3 (AES128-SHA) (which sounds promising) then Authenticating (NTLM), then prompts me for my password. I give this, but after a suspiciously long delay ~10s, I get the error SASL authentication failed. If your mutt was built with --enable-debug (mutt -v will include the line +DEBUG if so), you can run mutt -d2 to get a trace of mutt's conversation with the SMTP server in ~/.muttdebug0. There should be more clues in there. By the way, if I had to guess I'd say that the problem is that the server is advertising NTLM authentication but really only wants a plain password. You can fix this by setting smtp_authenticators=plain in your muttrc, instead of letting SASL pick the strongest it can find.
Re: Authenticated Exchange SMTP server problem
Hi Brendan, thanks very much for these suggestions. On 19 Sep 2010, at 22:43, Brendan Cully wrote: If your mutt was built with --enable-debug (mutt -v will include the line +DEBUG if so), you can run mutt -d2 to get a trace of mutt's conversation with the SMTP server in ~/.muttdebug0. There should be more clues in there. I've rebuilt (and upgraded from 1.5.20 to 1.5.21). Here's the log. I don't see anything unusual. 2010-09-19 23:14:38] Sending message... [2010-09-19 23:14:38] Looking up mail.physics.ox.ac.uk... [2010-09-19 23:14:38] Connecting to mail.physics.ox.ac.uk... [2010-09-19 23:14:38] Connected to mail.physics.ox.ac.uk:587 on fd=6 [2010-09-19 23:14:39] 6 220 mail.physics.ox.ac.uk Microsoft ESMTP MAIL Service ready at Sun, 19 Sep 2010 22:15:25 +0100 [2010-09-19 23:14:39] 6 EHLO astro.ox.ac.uk^M [2010-09-19 23:14:39] 6 250-mail.physics.ox.ac.uk Hello [77.4.235.134] [2010-09-19 23:14:39] 6 250-SIZE 20971520 [2010-09-19 23:14:39] 6 250-PIPELINING [2010-09-19 23:14:39] 6 250-DSN [2010-09-19 23:14:39] 6 250-ENHANCEDSTATUSCODES [2010-09-19 23:14:39] 6 250-STARTTLS [2010-09-19 23:14:39] 6 250-AUTH NTLM [2010-09-19 23:14:39] 6 250-8BITMIME [2010-09-19 23:14:39] 6 250-BINARYMIME [2010-09-19 23:14:39] 6 250 CHUNKING [2010-09-19 23:14:39] 6 STARTTLS^M [2010-09-19 23:14:39] 6 220 2.0.0 SMTP server ready [2010-09-19 23:14:39] ssl_check_preauth: hostname check passed [2010-09-19 23:14:39] X509_verify_cert: unable to get local issuer certificate (20) [2010-09-19 23:14:39] [/CN=winfe.physics.ox.ac.uk/CN=thphys.ox.ac.uk/CN=teaching.physics.ox.ac.uk/CN=smtps.physics.ox.ac.uk/CN=physics.ox.ac.uk/CN=imaps.physics.ox.ac.uk/CN=exchange.physics.ox.ac.uk/CN=exchange-cas3.physics.ox.ac.uk/CN=exchange-cas2.physics.ox.ac.uk/CN=exchange-cas1.physics.ox.ac.uk/CN=autodiscover.thphys.ox.ac.uk/CN=autodiscover.physics.ox.ac.uk/CN=autodiscover.atm.ox.ac.uk/CN=autodiscover.astro.ox.ac.uk/CN=atm.ox.ac.uk/CN=astro.ox.ac.uk/C=GB/ST=Oxfordshire/L=Oxford/O=University of Oxford/OU=Physics/CN=mail.physics.ox.ac.uk] [2010-09-19 23:14:39] X509_verify_cert: unable to get local issuer certificate (20) [2010-09-19 23:14:39] [/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware] [2010-09-19 23:14:39] ssl_check_preauth: digest check passed [2010-09-19 23:14:39] trusted: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware [2010-09-19 23:14:39] ssl_check_preauth: hostname check passed [2010-09-19 23:14:39] ssl_check_preauth: signer check passed [2010-09-19 23:14:39] SSL connection using TLSv1/SSLv3 (AES128-SHA) [2010-09-19 23:14:40] 6 EHLO astro.ox.ac.uk^M [2010-09-19 23:14:40] 6 250-mail.physics.ox.ac.uk Hello [77.4.235.134] [2010-09-19 23:14:40] 6 250-SIZE 20971520 [2010-09-19 23:14:40] 6 250-PIPELINING [2010-09-19 23:14:40] 6 250-DSN [2010-09-19 23:14:40] 6 250-ENHANCEDSTATUSCODES [2010-09-19 23:14:40] 6 250-AUTH NTLM LOGIN [2010-09-19 23:14:40] 6 250-8BITMIME [2010-09-19 23:14:40] 6 250-BINARYMIME [2010-09-19 23:14:40] 6 250 CHUNKING [2010-09-19 23:14:40] SASL local ip: 192.168.1.36;64383, remote ip:163.1.74.81;587 [2010-09-19 23:14:40] External SSF: 128 [2010-09-19 23:14:40] External authentication name: m...@physics.ox.ac.uk [2010-09-19 23:14:40] Authenticating (NTLM)... [2010-09-19 23:14:40] 6 AUTH NTLM [snip hash] [2010-09-19 23:14:40] 6 334 [snip long hash] [2010-09-19 23:14:40] mutt_sasl_cb_authname: getting authname for mail.physics.ox.ac.uk:587 [2010-09-19 23:14:40] mutt_sasl_cb_pass: getting password for m...@physics.ox.ac.uk@mail.physics.ox.ac.uk:587 [2010-09-19 23:14:43] 6 [snip long hash] [2010-09-19 23:14:48] 6 535 5.7.3 Authentication unsuccessful [2010-09-19 23:14:48] SASL authentication failed By the way, if I had to guess I'd say that the problem is that the server is advertising NTLM authentication but really only wants a plain password. You can fix this by setting smtp_authenticators=plain in your muttrc, instead of letting SASL pick the strongest it can find. With smtp_authenticators=plain, authorization fails and .muttdebug0 ends with: 2010-09-19 23:10:21] smtp_authenticate: Trying method plain [...] [2010-09-19 23:10:25] Authenticating (PLAIN)... [2010-09-19 23:10:25] 6 AUTH PLAIN [snip hash] [2010-09-19 23:10:30] 6 504 5.7.4 Unrecognized authentication type [2010-09-19 23:10:30] SASL authentication failed so I assume that plain is not right. (This ties in with the NLTM method Apple Mail autoselects and successfully uses for this server following a test connection.) Any ideas? -- Mike
Re: Authenticated Exchange SMTP server problem
On Sunday, 19 September 2010 at 23:21, Michael Williams wrote: Hi Brendan, thanks very much for these suggestions. On 19 Sep 2010, at 22:43, Brendan Cully wrote: If your mutt was built with --enable-debug (mutt -v will include the line +DEBUG if so), you can run mutt -d2 to get a trace of mutt's conversation with the SMTP server in ~/.muttdebug0. There should be more clues in there. I've rebuilt (and upgraded from 1.5.20 to 1.5.21). Here's the log. I don't see anything unusual. 2010-09-19 23:14:38] Sending message... [2010-09-19 23:14:38] Looking up mail.physics.ox.ac.uk... [2010-09-19 23:14:38] Connecting to mail.physics.ox.ac.uk... [2010-09-19 23:14:38] Connected to mail.physics.ox.ac.uk:587 on fd=6 [2010-09-19 23:14:39] 6 220 mail.physics.ox.ac.uk Microsoft ESMTP MAIL Service ready at Sun, 19 Sep 2010 22:15:25 +0100 [2010-09-19 23:14:39] 6 EHLO astro.ox.ac.uk^M [2010-09-19 23:14:39] 6 250-mail.physics.ox.ac.uk Hello [77.4.235.134] [2010-09-19 23:14:39] 6 250-SIZE 20971520 [2010-09-19 23:14:39] 6 250-PIPELINING [2010-09-19 23:14:39] 6 250-DSN [2010-09-19 23:14:39] 6 250-ENHANCEDSTATUSCODES [2010-09-19 23:14:39] 6 250-STARTTLS [2010-09-19 23:14:39] 6 250-AUTH NTLM [2010-09-19 23:14:39] 6 250-8BITMIME [2010-09-19 23:14:39] 6 250-BINARYMIME [2010-09-19 23:14:39] 6 250 CHUNKING [2010-09-19 23:14:39] 6 STARTTLS^M [2010-09-19 23:14:39] 6 220 2.0.0 SMTP server ready [2010-09-19 23:14:39] ssl_check_preauth: hostname check passed [2010-09-19 23:14:39] X509_verify_cert: unable to get local issuer certificate (20) [2010-09-19 23:14:39] [/CN=winfe.physics.ox.ac.uk/CN=thphys.ox.ac.uk/CN=teaching.physics.ox.ac.uk/CN=smtps.physics.ox.ac.uk/CN=physics.ox.ac.uk/CN=imaps.physics.ox.ac.uk/CN=exchange.physics.ox.ac.uk/CN=exchange-cas3.physics.ox.ac.uk/CN=exchange-cas2.physics.ox.ac.uk/CN=exchange-cas1.physics.ox.ac.uk/CN=autodiscover.thphys.ox.ac.uk/CN=autodiscover.physics.ox.ac.uk/CN=autodiscover.atm.ox.ac.uk/CN=autodiscover.astro.ox.ac.uk/CN=atm.ox.ac.uk/CN=astro.ox.ac.uk/C=GB/ST=Oxfordshire/L=Oxford/O=University of Oxford/OU=Physics/CN=mail.physics.ox.ac.uk] [2010-09-19 23:14:39] X509_verify_cert: unable to get local issuer certificate (20) [2010-09-19 23:14:39] [/C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware] [2010-09-19 23:14:39] ssl_check_preauth: digest check passed [2010-09-19 23:14:39] trusted: /C=US/ST=UT/L=Salt Lake City/O=The USERTRUST Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware [2010-09-19 23:14:39] ssl_check_preauth: hostname check passed [2010-09-19 23:14:39] ssl_check_preauth: signer check passed [2010-09-19 23:14:39] SSL connection using TLSv1/SSLv3 (AES128-SHA) [2010-09-19 23:14:40] 6 EHLO astro.ox.ac.uk^M [2010-09-19 23:14:40] 6 250-mail.physics.ox.ac.uk Hello [77.4.235.134] [2010-09-19 23:14:40] 6 250-SIZE 20971520 [2010-09-19 23:14:40] 6 250-PIPELINING [2010-09-19 23:14:40] 6 250-DSN [2010-09-19 23:14:40] 6 250-ENHANCEDSTATUSCODES [2010-09-19 23:14:40] 6 250-AUTH NTLM LOGIN [2010-09-19 23:14:40] 6 250-8BITMIME [2010-09-19 23:14:40] 6 250-BINARYMIME [2010-09-19 23:14:40] 6 250 CHUNKING [2010-09-19 23:14:40] SASL local ip: 192.168.1.36;64383, remote ip:163.1.74.81;587 [2010-09-19 23:14:40] External SSF: 128 [2010-09-19 23:14:40] External authentication name: m...@physics.ox.ac.uk [2010-09-19 23:14:40] Authenticating (NTLM)... [2010-09-19 23:14:40] 6 AUTH NTLM [snip hash] [2010-09-19 23:14:40] 6 334 [snip long hash] [2010-09-19 23:14:40] mutt_sasl_cb_authname: getting authname for mail.physics.ox.ac.uk:587 [2010-09-19 23:14:40] mutt_sasl_cb_pass: getting password for m...@physics.ox.ac.uk@mail.physics.ox.ac.uk:587 [2010-09-19 23:14:43] 6 [snip long hash] [2010-09-19 23:14:48] 6 535 5.7.3 Authentication unsuccessful [2010-09-19 23:14:48] SASL authentication failed By the way, if I had to guess I'd say that the problem is that the server is advertising NTLM authentication but really only wants a plain password. You can fix this by setting smtp_authenticators=plain in your muttrc, instead of letting SASL pick the strongest it can find. With smtp_authenticators=plain, authorization fails and .muttdebug0 ends with: 2010-09-19 23:10:21] smtp_authenticate: Trying method plain [...] [2010-09-19 23:10:25] Authenticating (PLAIN)... [2010-09-19 23:10:25] 6 AUTH PLAIN [snip hash] [2010-09-19 23:10:30] 6 504 5.7.4 Unrecognized authentication type [2010-09-19 23:10:30] SASL authentication failed so I assume that plain is not right. (This ties in with the NLTM method Apple Mail autoselects and successfully uses for this server following a test connection.) try login instead of plain. The server is advertising AUTH NTLM LOGIN above.
Re: Authenticated Exchange SMTP server problem
On 19 Sep 2010, at 23:42, Brendan Cully wrote: try login instead of plain. The server is advertising AUTH NTLM LOGIN above. That's it! Thanks very much! -- Mike
