Author Topic: Fail to send authenticated email  (Read 4400 times)

oreo

  • Newbie
  • *
  • Posts: 40
    • View Profile
    • http://
Fail to send authenticated email
« on: February 29, 2004, 04:35:18 pm »
I have a SL-5500 with SR3.10. Anyone use authenticated email?

I can send email using the non-auth server. When I use the auth server the message goes to the Sent folder but is not received by the email server. I tried both Authentication settings, i.e., \'Same as incoming mail server\' and \'Log on using\'.

Outgoing server:
Non-authenticated: smtp.myisp.net
Authenticated: smtpauth.myisp.net

I can send authenticated email to smtpauth with a Pocket PC using the same settings.

Do you have any information that may help?

Anonymous

  • Guest
Fail to send authenticated email
« Reply #1 on: February 29, 2004, 08:07:46 pm »
Is there a way to change the default value for the platform ID from linux to Windows? This may be why the ASMTP server rejects email messages.

Information is sent to the SMTP authentication server identifying the Operating System - as per User-Agent request-header field under RFC 1945 (the HTTP 1.0 spec) and RFC 2068 (the HTTP 1.1 spec). Some sites utilize this information and re-direct or restrict access.

Can I change this information? If the secure site is rigidly controlled, it may deny access to non-Windows platforms.

Some of the information the Zaurus sends to the SMTP server:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Linux 2.4.18-rmk7-pxa3-embedix armv4l)

Some of the information the Pocket PC sends to the SMTP server:
User-Agent Mozilla/4.0 (compatible; MSIE 4.01; Windows CE; PPC)
UA-OS: Windows CE Version 4.20

Any ideas?

oreo

  • Newbie
  • *
  • Posts: 40
    • View Profile
    • http://
Fail to send authenticated email
« Reply #2 on: March 01, 2004, 10:02:07 am »
It seems the ASMTP server does not accept the user-ID and password credentials sent when the user agent provides authentication information. It must be a limit of the Sharp OS. I put the Zaurus on the shelf and will use the PPC.

Is there another OS I can install that allows sending authenticated email?

alioth

  • Newbie
  • *
  • Posts: 2
    • View Profile
    • http://
Fail to send authenticated email
« Reply #3 on: March 01, 2004, 01:22:04 pm »
See the message \"e-mail: SMTP AUTH + SSL/TLS\" in the Software forum for details about one problem that I found with SMTP AUTH.  In particular, the Zaurus mailer gets confused and does not attempt to authenticate if the SMTP \"220\" greeting contains continuation lines.  For example, I cannot get my Zaurus to authenticate with smtpauth.earthlink.net, which emits three lines

$ telnet smtpauth.earthlink.net 25
220-stork.mail.pas.earthlink.net ESMTP Exim 3.33 #1 Thu, 26 Feb 2004 08:45:36 -0800
220-NO UCE. EarthLink does not authorize the use of its computers or network
220 equipment to deliver, accept, transmit, or distribute unsolicited e-mail.

I have gotten SMTP authentication to work with the e-mail provider tuffmail.com, which only emits a single line in its SMTP greeting.

oreo

  • Newbie
  • *
  • Posts: 40
    • View Profile
    • http://
Fail to send authenticated email
« Reply #4 on: March 01, 2004, 02:41:10 pm »
Read your helpful post. I get the same continuation lines as you describe. Now I understand how the Zaurus mailer fails to authenticate.

On Thursday, I can try a different SMTP server and will post the results here. And tuffmail.com is in my back pocket as a solution.

On the smtpauth.earthlink.net server:
I cannot get anywhere. Do you know the syntax?

220-heron.mail.pas.earthlink.net ESMTP Exim 3.33 #1 Mon, 01 Mar 2004 12:02:06 -0800
220-NO UCE.  EarthLink does not authorize the use of its computers or network
220 equipment to deliver, accept, transmit, or distribute unsolicited e-mail.
help
214-Commands supported:
214-    HELO EHLO MAIL RCPT DATA AUTH
214     NOOP QUIT RSET HELP
HELO
250 heron.mail.pas.earthlink.net Hello h-68-164-XXX-XX.snvacaid.dynamic.covad.net [68.164.XXX.XX]
EHLO
250-heron.mail.pas.earthlink.net Hello h-68-164-XXX-XX.snvacaid.dynamic.covad.net [68.164.XXX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH PLAIN LOGIN CRAM-MD5
250-STARTTLS
250 HELP
MAIL
500 Unrecognized command
RCPT
500 Unrecognized command
DATA
503 MAIL FROM command must precede DATA
AUTH
504  mechanism not supported

Anonymous

  • Guest
Fail to send authenticated email
« Reply #5 on: March 01, 2004, 04:50:44 pm »
Quote
Read your helpful post. I get the same continuation lines as you describe. Now I understand how the Zaurus mailer fails to authenticate.  

On Thursday, I can try a different SMTP server and will post the results here. And tuffmail.com is in my back pocket as a solution.

On the smtpauth.earthlink.net server:
I cannot get anywhere. Do you know the syntax?  

220-heron.mail.pas.earthlink.net ESMTP Exim 3.33 #1 Mon, 01 Mar 2004 12:02:06 -0800
220-NO UCE.  EarthLink does not authorize the use of its computers or network
220 equipment to deliver, accept, transmit, or distribute unsolicited e-mail.
help
214-Commands supported:
214-    HELO EHLO MAIL RCPT DATA AUTH
214     NOOP QUIT RSET HELP
...

See RFC821, RFC1869, and RFC2554 for details of the protocol; it is not easy to simulate SMTP AUTH by hand since certain parameters have to be  sent using BASE64 encoding.  Here is an example of the AUTH LOGIN protocol from http://www.thecabal.org/~devin/postfix/smtp-auth.txt :

        01: S: 220 saslserve.example.com ESMTP
        02: C: EHLO saslclient.example.com
        03: S: 250-saslserve.example.com
        04: S: 250-PIPELINING
        05: S: 250-SIZE 10240000
        06: S: 250-ETRN
        07: S: 250-AUTH LOGIN DIGEST-MD5 CRAM-MD5 PLAIN
        08: S: 250 8BITMIME
        09: C: AUTH LOGIN
        10: S: 334 VXNlcm5hbWU6
        11: C: Ym9maA==
        12: S: 334 UGFzc3dvcmQ6
        13: C: Ym9maA==
        14: S: 235 Authentication successful
        15: C: MAIL FROM:<devin@example.com> SIZE=697
        16: S: 250 Ok
        17: C: RCPT TO:<root@saslserve.example.com>
        18: S: 250 Ok
        19: C: DATA
        20: S: 354 End data with <CR><LF>.<CR><LF>
        21: S: 250 Ok: queued as 1CF2E1D962
        22: C: QUIT
        23: S: 221 Bye

where lines 11 and 13 are the BASE64 encodings  of the username and password.  

To get the Zaurus to authenticate, you need to suppress all of the 220 lines except the first.  I used the utility netcat running on a Linux PC to dump the transmissions between the Zaurus and the SMTP server.  There is a variant of netcat called netsed that can apparently perform edits on a network connection such as suppressing the 220 lines.  I have not found Zaurus versions of netcat and netsed.

oreo

  • Newbie
  • *
  • Posts: 40
    • View Profile
    • http://
Fail to send authenticated email
« Reply #6 on: March 01, 2004, 07:45:52 pm »
W, that is a detailed protocol. Thanks for the explanation.

I\'ll try for a server solution with the SMTP 220 greeting having no continuation lines.

oreo

  • Newbie
  • *
  • Posts: 40
    • View Profile
    • http://
Fail to send authenticated email
« Reply #7 on: March 05, 2004, 03:28:21 pm »
I tried the smtp.comcast.net server. Now ASMTP works.
This server has no SMTP 220 continuation lines.

Thanks for the help.