From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: nnimap problem with current cvs
Date: Wed, 17 Sep 2003 18:33:15 -0400 [thread overview]
Message-ID: <87n0d3gi50.fsf@amalthea.paradoxical.net> (raw)
In-Reply-To: <ilu65jrt73h.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Press G e on groups on the starttls server and make sure they either
> is "nnimap:hostname" or contain the entire select method _exactly_
> as typed in .gnus. Perhaps you have some group that uses a old
> version of the select method, and since Gnus notice that they are
> different, it opens a new server for it. If you know how to
> reproduce getting the non-referral (i.e., non-"nnimap:hostname"
> version) select method in the group buffer, please tell. Gnus
> should, IMHO, use the "nnimap:hostname" syntax, so you can modify
> the g-s-s-m without re-subscribing to all groups on the old server.
> I'm not sure why you don't get this problem on direct startup
> though.
Well, when it started happening every time I posted a message via
nntp, I really started to get suspicious. Sending mail didn't trigger
the issue...looking at my Gcc setup, I do sort sent mail and new into
different imap mailboxes...
I fixed this by subscribing to the sent-news mailbox (for some reason,
I had forgotton to do this). This seems to have fixed the problem,
even though I see messages from Gnus indicating it's re-doing a
STARTTLS session while in the middle of posting to nntp.
We'll see what the logs say after this post...
--
Josh Huber
next prev parent reply other threads:[~2003-09-17 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 21:36 Josh Huber
2003-09-17 21:53 ` Simon Josefsson
2003-09-17 22:33 ` Josh Huber [this message]
2003-09-17 22:35 ` Josh Huber
2003-09-17 22:40 ` Josh Huber
2003-09-17 22:39 ` Simon Josefsson
2003-09-17 22:42 ` Josh Huber
2003-09-17 23:32 ` Simon Josefsson
2003-09-18 1:31 ` Josh Huber
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=87n0d3gi50.fsf@amalthea.paradoxical.net \
--to=huber@alum.wpi.edu \
/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).