Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Connecting to IMAP when exiting a group that has nnml emails
Date: Mon, 28 Sep 2020 08:14:56 -0700	[thread overview]
Message-ID: <87y2kuhr0v.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m23632x8c0.fsf@codeisgreat.org>

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Today I encountered a very strange problems:
>
> 1. While in a group that has emails from nnml backend, I presed 'm' and
> started composing email. After pressing C-c C-c to send the email a
> buffer opened for a very short time and vanished. I had doubt, so I
> check the 'sent archive' group. It didn't have the email. Then I went to
> server and checked that the email has actually gone.  2. While in the
> same group, I marked a few emails as expirable. Then pressed 'q' to exit
> to group buffer. Gnus started to connect to IMAP. I don't know why. The
> emails are managed by nnml backend in this group.
>
> Could you please tell me how to diagnose such issues? These issues are
> not permanent. I restared Gnus as well as Emacs a few times. Sometimes
> these problem occur sometimes not.

Perhaps you've got posting styles slightly misconfigured so that, when
composing a message from the nnml group, the Gcc header is set to the
nnimap "Sent" group? And/or your `nnmail{-fancy,}-expiry-target' is set
to a group on the nnimap server? That would account for Gnus connecting
to IMAP after send/expiry.

When you compose a mail, check what the Gcc header says. And I'm
guessing the expiry thing is a separate problem.



  reply	other threads:[~2020-09-28 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 14:51 Pankaj Jangid
2020-09-28 15:14 ` Eric Abrahamsen [this message]
2020-09-28 16:40   ` Pankaj Jangid
2020-09-28 17:04     ` Pankaj Jangid
2020-09-28 22:15       ` Eric Abrahamsen
2020-09-29 11:30       ` Eric S Fraga
2020-09-29 12:30         ` Pankaj Jangid

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=87y2kuhr0v.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    /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).