From: sirjofri+ml-9front@sirjofri.de
To: 9front@9front.org
Subject: Re: [9front] 9front mailing list blocks my messages without notice
Date: Tue, 21 Jul 2020 11:04:14 +0000 (UTC) [thread overview]
Message-ID: <958e47db-17c3-43cf-a5cd-64c589eedb1e@sirjofri.de> (raw)
In-Reply-To: <AD034435C80D8AE139CE7815A3FA1ED9@ewsd.inri.net>
Hello,
so let's try sending another mail and see if that arrives. This time from the mail address that's subscribed to the list.
21.07.2020 05:04:31 sl@stanleylieber.com:
> 9front mailing list server has been known to reject mails from
> perfectly good senders.
That's not nice, but even then, that's how it is.
> my logs show mails from sirjofri@sirjofri.de starting on Oct 6
> 06:42:59 EDT 2019. this address is not currently subscribed to the
> list, but at least some of the messages from it did get through and
> were saved in the mailing list mbox.
Does the mailing list block messages from addresses that are not subscribed?
> From sirjofri.de!sirjofri Fri Jul 10 03:16:12 EDT 2020 remote from
> ewsd Received: from oat.nine.sirjofri.de ([5.45.105.127]) by ewsd; Fri
> Jul 10 03:16:12 EDT 2020 Received: from email.faircode.eu
> ([178.5.83.171]) by oat; Fri Jul 10 09:14:50 CES 2020
Is it possible that it's something about the helo/ehlo string? Because email.fairemail.eu is the mobile client I use and it's its ehlo string. I currently changed it to sirjofri.de, it seems like my mail server does not overwrite it when relaying mail to other servers?
On the other hand I never configured mail server relays myself, so I don't know exactly if mail clients send mails to the destination or the own mail server (relay) first.
If it really is the ehlo string this mail should arrive.
> starting on Jul 15 14:07:56 EDT 2020 the list received messages from
> sirjofri+ml-9front@sirjofri.de, which is currently subscribed. none
> of those messages have made it to the list.
I don't think I wrote mails from this address other than the subscription mail itself. I prefer using the +ml-9front address for automatic sorting of mails, but still send from the "untagged" address.
If 9front mail server is unable to handle these plus signs I can change my subscribed address.
> seemingly intermittent failures:
> ewsd Jun 18 21:41:43 delivery sirjofri at net!sirjofri.de (pizarro.uberspace.de:185.26.156.189) rcptto failed: 450 plugin timeout (D9DC0AF1-E322-4160-9A1E-981D3DD19CC7.1)
> ewsd Jul 4 10:27:00 delivery sirjofri at net!sirjofri.de (sirjofri.de:185.26.156.189) rcptto failed: 550 sirjofri@sirjofri.de That recipient is not allowed
> ewsd Jul 5 11:39:19 delivery sirjofri at net!sirjofri.de (sirjofri.de:185.26.156.189) rcptto failed: 550 sirjofri@sirjofri.de That recipient is not allowed
> ewsd Jul 5 12:04:16 delivery sirjofri at net!sirjofri.de (sirjofri.de:185.26.156.189) rcptto failed: 550 sirjofri@sirjofri.de That recipient is not allowed
These are from my old mail server (uberspace). I think we can ignore them, (if they didn't add my domain to some blocklist).
> one day only:
> ewsd Jul 15 12:35:12 [oat.nine.sirjofri.de/5.45.105.127] sirjofri.de!sirjofri+ml-9front -> 9front.org!9front-owner sendercheck: rejected: spf fail
> ewsd Jul 15 12:39:54 ehlo from 5.45.105.127 as oat.nine.sirjofri.de
> ewsd Jul 15 12:39:57 [oat.nine.sirjofri.de/5.45.105.127] sirjofri.de!sirjofri+ml-9front -> 9front.org!9front-owner sendercheck: rejected: spf fail
> ewsd Jul 15 12:59:23 ehlo from 5.45.105.127 as oat.nine.sirjofri.de
> ewsd Jul 15 12:59:30 [oat.nine.sirjofri.de/5.45.105.127] sirjofri.de!joel -> 9front.org!9front-owner sendercheck: rejected: spf fail
> ewsd Jul 15 13:03:49 ehlo from 5.45.105.127 as oat.nine.sirjofri.de
> ewsd Jul 15 13:03:57 [oat.nine.sirjofri.de/5.45.105.127] sirjofri.de!sirjofri -> 9front.org!9front-owner sendercheck: rejected: spf fail
> ewsd Jul 15 13:13:43 ehlo from 5.45.105.127 as oat.nine.sirjofri.de
> ewsd Jul 15 13:13:51 [oat.nine.sirjofri.de/5.45.105.127] sirjofri.de!sirjofri+ml-9front -> 9front.org!9front-owner sendercheck: rejected: spf fail
Really, don't ask me why spf failed here. I didn't change these and they are configured to check the mx records (which points to the new server oat.nine.sirjofri.de). Since they are only one day I think these will not happen anymore.
So let's see if this mail arrives or look how we can fix these issues. Thank you for your response.
sirjofri
next parent reply other threads:[~2020-07-21 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AD034435C80D8AE139CE7815A3FA1ED9@ewsd.inri.net>
2020-07-21 11:04 ` sirjofri+ml-9front [this message]
2020-07-21 14:25 ` Stanley Lieber
2020-07-30 0:48 ` sl
[not found] <CBF4C42EED78C22F0FE8ADFAECF31CF8@ewsd.inri.net>
2020-07-30 4:07 ` sirjofri+ml-9front
2020-07-30 4:29 ` Stanley Lieber
2020-07-30 8:24 ` hiro
[not found] <DAC7D1CFF4CD7B1AA7BA81DFBD2A17C6@ewsd.inri.net>
2020-07-21 13:20 ` Steffen Nurpmeso
2020-07-20 8:20 Joel Fridolin Meyer
2020-07-21 1:02 ` [9front] " sl
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=958e47db-17c3-43cf-a5cd-64c589eedb1e@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).