From: Felix Natter <fnatter@gmx.net>
To: ding@gnus.org
Subject: Mails not sent / not not appear in nnfolder+sent
Date: Sun, 22 Jan 2023 16:32:43 +0100 [thread overview]
Message-ID: <875ycyshyc.fsf@bitburger.home.felix> (raw)
hello Gnus experts,
I am using Gnus v5.13 / GNU Emacs 27.1 and for quite some time,
occasionally, some mails are not actually sent _and/or_ do not appear in the
sent-mails backend (nnfolder+sent:sent-mail.<year>-<month>).
That is, *maybe* they are sent, but do not end up in sent-mail-**.
I'm not sure I matched this correctly, but it seems this is a
problematic case in *Messages*:
Sending email
250 Requested mail action okay, completed: id=1N1OXT-1oZnjj2sXb-012t77
Sending email done
221 gmx.net Service closing transmission channel
Sending...done
Deleting article /home/felix/News/drafts/drafts/190 in drafts...
Saving file /home/felix/.newsrc...
... and this is a normal case:
Sending email
250 Requested mail action okay, completed: id=1MQ5vW-1p6KQW3o2a-00M3AZ
Sending email done
221 gmx.net Service closing transmission channel
Saving file /home/felix/Mail/sent/sent-mail/2023-01...
Wrote /home/felix/Mail/sent/sent-mail/2023-01
Sending...done
Deleting article /home/felix/News/drafts/drafts/191 in drafts...
Saving file /home/felix/.newsrc...
How can I debug this / add additional logging?
Is there a chance that this is fixed in a newer emacs?
How can I be sure that the mail is actually sent when this occurs?
Many Thanks and Best Regards,
Felix
--
Felix Natter
next reply other threads:[~2023-01-22 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 15:32 Felix Natter [this message]
2023-01-22 17:52 ` Gijs Hillenius
2023-01-27 20:03 ` Felix Natter
2023-01-27 22:23 ` Eric Abrahamsen
2023-02-04 12:39 ` Felix Natter
2023-03-20 12:51 ` Felix Natter
2023-03-21 0:52 ` Emanuel Berg
2023-03-21 10:06 ` Felix Natter
2023-03-21 13:19 ` Emanuel Berg
2023-01-23 7:10 ` Gijs Hillenius
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=875ycyshyc.fsf@bitburger.home.felix \
--to=fnatter@gmx.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).