From: Niklas Morberg <niklas.morberg@axis.com>
Cc: Simon Josefsson <jas@extundo.com>, <ding@gnus.org>
Subject: Re: imap folder for outgoing messages
Date: Wed, 05 Dec 2001 11:13:08 +0100 [thread overview]
Message-ID: <uk7w29dqj.fsf@axis.com> (raw)
In-Reply-To: <vaf8zci3thy.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 05 Dec 2001 10:29:13 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I just use fully qualified group names in gnus-message-archive-group
> and don't bother with setting gnus-message-archive-method at all.
Thanks, this seems to do the trick.
FWIW, I did manage to reproduce the original problem in a
more orderly fashion. Fresh gnus from CVS this morning.
When starting gnus the first time, only one nnimap server
was present in the server buffer (the proper one). I then
typed C-x m and composed an email. The value of the Gcc
field when composing the message was
Gcc: nnimap:"Sent Items"
After sending this first message, one additional nnimap
server showed up in the Server buffer:
{nnimap:} (denied)
and no message got stored in the Sent Items folder after
composing and sending a second message. After sending yet
another message, a third nnimap server showed up:
{nnimap:nil} (denied)
The other two nnimap servers are still there. Sending works,
but copies are not stored.
Kai's solution now makes the Gcc field to be:
Gcc: "nnimap+MY.IMAP.SERVER:Sent Items"
and everything works as expected. I would still say there
is a bug somewhere that causes the creation of these void
nnimap servers, but I don't get bitten by it anymore.
Niklas
next prev parent reply other threads:[~2001-12-05 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 12:22 Niklas Morberg
2001-12-04 17:13 ` Paul Jarc
2001-12-04 17:27 ` Kai Großjohann
2001-12-04 19:02 ` Simon Josefsson
2001-12-05 8:37 ` Niklas Morberg
2001-12-05 9:29 ` Kai Großjohann
2001-12-05 10:13 ` Niklas Morberg [this message]
2001-12-05 10:27 ` Kai Großjohann
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=uk7w29dqj.fsf@axis.com \
--to=niklas.morberg@axis.com \
--cc=ding@gnus.org \
--cc=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).