[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SMTP port specification



At Mon, 3 Dec 2012 14:35:48 -0500,
Haines Brown wrote:
> 
> On Mon, Dec 03, 2012 at 02:42:25PM +0100, Herbert J. Skuhra wrote:
> > On 03.12.2012 14:14, Haines Brown wrote:
> > >On Sun, Dec 02, 2012 at 11:00:52PM +0100, Herbert J. Skuhra wrote:
> > >>On Sun, 2 Dec 2012 15:37:54 -0500
> > >
> > >>"Where do you set 'wl-smtp-posting-user'?
> > >
> > >I had it orginally then it was lost when struggling to find what
> > >works.
> > >
> > >I put it in. Now when I sent a test message I get error:
> > >
> > >	Error in folder name `~/Mail/wl-sent
> > 
> > I guess your wl-fcc is wrong. Try:
> > 
> > (setq wl-fcc "+wl-sent")
> 
> Herbert,
> 
> OK, tried that. Now the error is:
> 
>   [smtp-server recipients id err smtp-sasl-user-name smtp-sasl-mechanisms 
>   wl-draft-write-sendlog failed smtp smtp-response-error 535 elmo-remove-passwd 
>   format "SMTP:%s/%s@%s" signal server mechanism user] 6)
>   wl-draft-send-mail-with-smtp()
>   ...
> 
> Beck to the authentication problem it seems. If so, another 
> possiblity occurs to me. 

Is there a buffer called `*trace of SMTP session to …*` after the
authentication failure? This buffer contains the dialog between WL and
the server and should give you good overview over what exactly
happens.

E.g.

,----[ *trace of SMTP session to mail.xlhost.de* ]
| 220 mail.xlhost.de ESMTP Postfix 
| Process SMTP getötet
| (2.7.1) (Linux)
| EHLO w500.major-mode.org.ictsoc.de
| 250-app1a.xlhost.de
| 250-PIPELINING
| 250-SIZE 50480000
| 250-ETRN
| 250-STARTTLS
| 250-AUTH CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
| 250-AUTH=CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
| 250-ENHANCEDSTATUSCODES
| 250 8BITMIME
| STARTTLS
| 220 2.0.0 Ready to start TLS
| EHLO w500.major-mode.org.ictsoc.de
| 250-app1a.xlhost.de
| 250-PIPELINING
| 250-SIZE 50480000
| 250-ETRN
| 250-AUTH CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
| 250-AUTH=CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
| 250-ENHANCEDSTATUSCODES
| 250 8BITMIME
| AUTH PLAIN XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
| 235 2.7.0 Authentication successful
| …
`----

The AUTH PLAIN contains the base64 encoded username and password, you
can check what WL is actually sending by decoding the string with
`base64-decode-string'.

Best,
  -- David
-- 
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

Attachment: pgpS4yEMlCJmN.pgp
Description: OpenPGP Digital Signature