Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: upgrade from Debian's 5.10.6-0.CVS.20050317-1 to 5.11+v0.4.dfsg-1 breaks outbox on imap
Date: Tue, 16 May 2006 13:05:52 +0200	[thread overview]
Message-ID: <87ejyu5iwf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87ves6uuf6.fsf@myxomop.com> (Alexander Kotelnikov's message of "Tue, 16 May 2006 14:37:49 +0400")

Alexander Kotelnikov <sacha@myxomop.com> writes:

>>>>>> On Mon, 15 May 2006 16:25:57 +0200
>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
> SJ> 
> SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>>>>>> On Mon, 15 May 2006 13:46:31 +0200
>>>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
> SJ> 
> SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>>> 
>>>>> After I upgraded from more than one year old gnus my outgoing mail is
>>>>> no longer stored on imap after I send it.
>>>>> 
>>>>> Parts of imap configuration follow:
>>>>> (nnimap-stream ssl)
>>>>> 
>>>>> (setq
>>>>> imap-ssl-program '("stunnel -c -v 3 -a ~/.ssl/ -f -r %s:%p")
>>>>> imap-use-utf7 nil
>>>>> imap-log t
>>>>> imap-client-eol "
>>>>> \n"
>>>>> imap-server-eol "
>>>>> \n"
>>>>> imap-calculate-literal-size-first t
>>>>> imap-process-connection-type t)
>>>>> 
>>>>> (setq gnus-message-archive-group "nnimap+myxomop:INBOX.outbox")
>>>>> 
>>>>> 
>>>>> Here goes a part of *imap-log*
>>>>> 
>>>>> 190 APPEND "INBOX.outbox" {453}
>>>>> * BAD Invalid tag
> SJ> ...
>>>>> 190 NO Message contains invalid header
> SJ> 
> SJ> This sounds as if your imap-client-eol should be "\n" and not "\r\n".
>>> 
>>> Now it is
>>> 
>>> 189 OK Completed
>>> 190 APPEND "INBOX.outbox" {450}
>>> 
>>> and gnus needs C-g to get out of infinite wait.
> SJ> 
> SJ> Maybe you need to set imap-calculate-literal-size-first to nil?
>
> None of combinations 
> imap-calculate-literal-size-first t/nil 
> and
> imap-client-eol "\r\n"/"\n" works :(

Maybe imap-server-eol has to be "\n" too?  Otherwise, I think imap.el
will wait for the continuation line terminated with a \r\n, but that
won't happen.

If that doesn't work either, you'll have to debug imap.el to find out
what it is looking for, and comparing that with what's in the "
*nnimap* foo" buffer.



  reply	other threads:[~2006-05-16 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15  9:22 Alexander Kotelnikov
2006-05-15 11:46 ` Simon Josefsson
2006-05-15 12:40   ` Alexander Kotelnikov
2006-05-15 14:25     ` Simon Josefsson
2006-05-16 10:37       ` Alexander Kotelnikov
2006-05-16 11:05         ` Simon Josefsson [this message]
2006-05-16 11:48           ` Alexander Kotelnikov
2006-05-16 13:43             ` Simon Josefsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ejyu5iwf.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).