From: Iain Parris <ipv2.lst@parris.org>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Sup Autogenerated Fake Sender
Date: Thu, 09 Jul 2020 20:15:46 +0100 [thread overview]
Message-ID: <1594321619-sup-1430@ceres> (raw)
In-Reply-To: <1594320920-sup-9158@rob-Lenovo-Y720-15IKB>
Hi Robert,
Excerpts from Robert Winkler's message of 2020-07-09 14:01:01 -0500:
> Thanks for the explication. Thus, this is an error notice of failed
> sending.
Yes, I believe so - or perhaps of failed retrieval (if you are
downloading a copy of emails from a server).
> Using "V" the mails seem to be completely empty. Well I suppose, they come from
> messages that did not arrive (at least 2; but in both cases they were
> important enough that I was "reminded" ;-)).
That's odd. Are the mail files empty (zero byte files) in your Maildir?
You could try to identify empty files with something like:
find ~/Mail -size 0
The root cause, though, is the malformed email files, rather than a bug
in Sup.
Kind regards,
Iain
next prev parent reply other threads:[~2020-07-09 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 16:50 Robert Winkler
2020-07-09 17:59 ` [sup] " Iain Parris
2020-07-09 19:01 ` Robert Winkler
2020-07-09 19:15 ` Iain Parris [this message]
2020-07-10 4:30 ` Dan Callaghan
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=1594321619-sup-1430@ceres \
--to=ipv2.lst@parris.org \
--cc=supmua@googlegroups.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