From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: upas sending duplicate copies
Date: Thu, 03 Sep 2020 11:23:26 -0400 [thread overview]
Message-ID: <F69852EB-AD32-47BF-9B31-16C76A50F8EA@stanleylieber.com> (raw)
running latest code, no other recent changes to my mail setup. people are reporting receiving duplicate copies of mail from me. i don't see any obvious signs of delivery failures in my logs, but i do see what appear to be multiple deliveries of the same message to remote servers, around 3-5 minutes apart. of course, it's all intermittent, and doesn't happen with every recipient.
this never used to happen before that i'm aware of.
sl
next reply other threads:[~2020-09-03 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 15:23 Stanley Lieber [this message]
2020-09-04 3:03 ` [9front] " ori
2020-09-10 16:20 ` Stanley Lieber
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=F69852EB-AD32-47BF-9B31-16C76A50F8EA@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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).