Re: [Evolution] imap server errors when sending mail.

[Jeffrey Stedfast <fejj ximian com>]

On Mon, 2003-07-14 at 09:59, Ian Perryman wrote:
> Ever since I have started using evolution, I have had difficulty with
> sending mail reliably.  Sometimes the message would be mangled in my
> "sent" folder after being sent, sometimes it would be left in the
> outbox, only to be resent the next time I sent a message ( recipients
> would receive multiple copies).  Long delays would occur when sending
> before the message would be transferred from the outbox to the sent
> folder.
>
> I could not find anything in the archives on this topic, so I I ran
> evolution as follows:
> iperryma>export CAMEL_VERBOSE_DEBUG=1
> iperryma>evolution > tmp/evolution_dump 2>&1
>
> I am using imap with a MS Exchange Server to view my mail. I leave the
> mail on the server.
>
> I use SMTP to send mail to an internal host mail server (no SSL) and
> no authentication.
>
> Occasionally, I get error messages when sending mail.  A pop up window
> with something  like "an error occured but message was sent ok".
>
> The message is still sitting in my "outbox" but indeed the recipients
> received the mail.
>
> In the output file the following lines appear:
>
> (evolution:5696): camel-imap-provider-WARNING **: Unexpected response
> from IMAP server: Subject: BAD Protocol Error: "Unidentifiable command
> specified"
> sending : A00011 NOOP 
> received: From: BAD Protocol Error: "Unidentifiable command specified"

looks like a broken server... NOOP is an IMAP command that clients send
to the server just to let the server know that we are still interested
in seeing our mail. Basically, after a set period of time of inactivity,
some servers will disconnect their clients. NOOP is meant to prevent
this auto-disconnect.

>  
>
> (evolution:5693): camel-imap-provider-WARNING **: Unexpected response
> from IMAP server: From: BAD Protocol Error: "Unidentifiable command
> specified"
> sending : A00012 LIST "" {1+} 
> % 

another perfectly valid command...

> Any ideas what might be going on? This behaviour does not occur for my
> colleagues using Mozilla in a similar configuration.

broken server as far as I can tell...

Jeff

> Regards,
> Ian Perryman
-- 
Jeffrey Stedfast
Evolution Hacker - Ximian, Inc.
fejj ximian com  - www.ximian.com