Preserving evolution mail during OS changes

[dsavage at peaknet.net]

On Sun, 2003-09-07 at 17:31, Kai Thomsen wrote:
> On Sun, 7 Sep 2003 17:02:50 -0500 (CDT), dsavage at peaknet.net wrote:
>
> > Before doing a fresh install of Severn on my laptop, I copied a
> > tarball of my home directory to another system. After Severn was
> > intalled, I restored my ~/evolution/ subdirectory from that tarball,
> > and also reviewed my send& receive mail configs.
> >
> > This restored all old e-mail and folders. Inbound e-mail resumed
> > immediately, but I am unable to send evolution e-mail thru my ISP as
> > before. Every time I try to send a test message I get the following
> > error:
> >
> >      Error while performing operation:
> >      MAIL FROM response error: Command unrecognized: ""
>
> Google found this thread:
>
>   http://www.mail-archive.com/evolution@lists.ximian.com/msg03317.html

Kai,

My Ethereal trace is very similar to the one in that thread. Note step
10:

1. My client initiates a SMTP session with a TCP 3-way handshake to my
ISP's SMTP server's standard smtp port:
lioness          smtp.peaknet.net TCP      32818 > smtp [SYN]
Seq=3593689985 Ack=0 Win=5840 Len=0
smtp.peaknet.net lioness          TCP      smtp > 32818 [SYN, ACK]
Seq=3480868317 Ack=3593689986 Win=5792 Len=0
lioness          smtp.peaknet.net TCP      32818 > smtp [ACK]
Seq=3593689986 Ack=3480868318 Win=5840 Len=0

2. The server responds, identifying itself with a welcome banner:
smtp.peaknet.net lioness          SMTP     Response: 220 nsi01.peaknet.net
ESMTP Sendmail 8.12.8/8.12.8; Mon, 25 Aug 2003 22:50:33 -0500

3. My client acknowledge that response:
lioness          smtp.peaknet.net TCP      32818 > smtp [ACK]
Seq=3593689986 Ack=3480868403 Win=5840 Len=0

4. My client tells the server it understands SMTP extensions:
lioness          smtp.peaknet.net SMTP     Command: EHLO e

	*** NOTE: My client's name is not 'e' ***

5. The server sends a TCP ACK of the EHLO command:
smtp.peaknet.net lioness          TCP      smtp > 32818 [ACK]
Seq=3480868403 Ack=3593689995 Win=5792 Len=0

6. The server responds to the EHLO command, indicating it is ready to
proceed:
smtp.peaknet.net lioness          SMTP     Response: 250-nsi01.peaknet.net
Hello as1-6-187.peaknet.net [208.4.19.187], pleased to meet you

7. My client sends a TCP ACK of that response:
lioness          smtp.peaknet.net TCP      32818 > smtp [ACK]
Seq=3593689995 Ack=3480868643 Win=6432 Len=0

8. Preliminaries complete, my client starts the send mail cycle:
lioness          smtp.peaknet.net SMTP     Command: MAIL
FROM:<dsavage at peaknet.net>

9. The server validates my account:
smtp.peaknet.net lioness          SMTP     Response: 250 2.1.0
<dsavage at peaknet.net>... Sender ok

10. My client aborts (HUH???):
lioness          smtp.peaknet.net SMTP     Command: QUIT

11. Both sides shut the down TCP connection:
smtp.peaknet.net lioness          SMTP     Response: 221 2.0.0
nsi01.peaknet.net closing connection
lioness          smtp.peaknet.net TCP      32818 > smtp [RST]
Seq=3593690034 Ack=0 Win=0 Len=0
smtp.peaknet.net lioness          TCP      smtp > 32818 [FIN, ACK]
Seq=3480868737 Ack=3593690034 Win=5792 Len=0
lioness          smtp.peaknet.net TCP      32818 > smtp [RST]
Seq=3593690034 Ack=0 Win=0 Len=0

This suggests to me that (a) my evolution client is misconfigured, or
(b) there's a bug in Severn's version of evolution.

--Doc Savage
  Fairview Heights, IL