how to filter nextcloud email in my inbox
I am sometimes getting mail like this:
Date: Mon, 09 Jan 2023 19:00:03 +0000
From: noreply@torproject.org
To: anarcat@torproject.org
Subject: [REDACTED: event name]
[...]
It's the Nextcloud calendar notifications. Those land straight in my inbox because I couldn't find a reliable way to filter them... And really, there's no way to distinguish this email from another bot writing from noreply@tpo
... so while I could just sinkhole noreply@
into a "nextcloud" folder, it is bound to possibly cause problems in the future.
And, really, there's no way to identify those emails, short of looking at the body. Here are the full headers of the email below the first Received- By
line:
Message-ID: <a19ff3330d10600cc0dffb4b6fbd0e71@swift.generated>
Date: Mon, 09 Jan 2023 19:00:03 +0000
Subject: [REDACTED: event name]
From: noreply@torproject.org
To: anarcat@torproject.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="_=_swift_1673290803_2ed0cc56440e69f6be00ac15eda2e18d_=_"
... maybe I could use the message ID as a pattern here? But at this point I might as well just grep the body.
Really, it seems to me Nextcloud should be a better netizen with its outgoing email. Here's another example:
Date: Wed, 07 Dec 2022 16:18:20 +0000
From: Anarcat via Nextcloud <noreply@torproject.org>
To: [redacted]@torproject.org
Reply-To: Anarcat <anarcat@torproject.org>
Subject: Anarcat shared »private« with you
[ multipart/alternative ]
[ text/plain ]
Anarcat shared »private« with you.
[...]
... at least this one has "Nextcloud" in the From
header, but it 's kind of inconsistent. And again, no other special header to identify this as automatically generated email, in violation of some RFC I forgot the number of (I promise).
So I'm thinking that a simple system fix for this would be to change the From
header to noreply+nextcloud@torproject.org
. That would allow obsessive-compulsive inbox cleaners like me to have some sort of hold on the incoming email. I am not actually sure that the above email works or what it does, we should test it to make sure it doesn't backscatter or fail...
Ideally, this would also be reported upstream.