From: ori@eigenstate.org
To: sirjofri+ml-9front@sirjofri.de, 9front@9front.org
Subject: Re: [9front] “empty” mail (possible unimportant bug)
Date: Fri, 02 Oct 2020 08:00:19 -0700 [thread overview]
Message-ID: <B810BCC731C8C988601E64F48ED7ADFE@eigenstate.org> (raw)
In-Reply-To: <4A046B5D379ACFB93A9E1CC27944A9A9@sirjofri.de>
> Hey all,
>
> occasionally I receive “empty” mails on my upas/smtp server (9front). Looking at the mail in /mail/box/ it looks like this:
>
> From gmail.com!koepketemi17ixibs Fri Oct 2 11:16:06 CES 2020
> Received: from gmail.com ([104.148.61.185]) by oat; Fri Oct 2 11:16:06 CES 2020
>
> (followed by two empty lines)
>
> I don't claim this mail has anything to do with gmail and I don't know the username/email address. Oat is my machine. Generally I just delete these mails, they don't break anything. So this is just for your information.
>
> I know there were some changes in the last weeks (at least new tmdate) and it's possible that this bug is already fixed (by accident). I'll just try updating and hope my imap still works.
>
> sirjofri
I've seen similar emails -- but they were arriving at an OpenBSD
box, and showed up as empty in Unix clients when I sanity checked
upas/fs. I've been blaming them on incompetent spammers.
So, a few questions:
- Does this happen regularly?
- Is there any typical source email for this?
- Does the raw data in /mail/box/... also seem empty?
If it turns out to happen regularly enough to be worth looking at
more deeply, maybe we could patch smtpd to tee off the raw smtp
session bytes into /sys/log.
next prev parent reply other threads:[~2020-10-02 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 10:16 sirjofri+ml-9front
2020-10-02 15:00 ` ori [this message]
2020-10-02 15:25 ` [9front] " sirjofri+ml-9front
2020-10-03 3:54 ` ori
2020-10-04 0:32 ` Lyndon Nerenberg
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=B810BCC731C8C988601E64F48ED7ADFE@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=sirjofri+ml-9front@sirjofri.de \
/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).