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.