Detlef
On 7/4/24 14:24, Hans wrote:
Me again, sorry.
Now I got my last mail back with the spam tag!
Subject:
Re: *SPAM* [SOLVED] Re: This is a testmail!
This is the header:
X-Spam-Flag: YES
X-SPAM-FACTOR: DKIM
X-Envelope-From:
bounce-debian-user=hans.ul
On Thu, Jul 4, 2024 at 4:55 PM Detlef Vollmann wrote:
>
> Isn't this the usual DKIM problem with lists?
> The From: has @loop.de, but the sender and DKIM signature
> is from lists.debian.org.
>
> That's why most lists these days rewrite the From: header.
One small nit: rewriting headers is not ap
e spam tag!
Subject:
Re: *SPAM* [SOLVED] Re: This is a testmail!
This is the header:
X-Spam-Flag: YES
X-SPAM-FACTOR: DKIM
X-Envelope-From: bounce-debian-user=hans.ullrich=loop...@lists.debian.org
DMARC-Filter:
OpenDMARC Filter v1.4.1 mail39c50.megamail
On 2024-07-04 at 15:25, Hans wrote:
> Hi The Wanderer,
>
>> Hans, are you certain you composed those three messages the same
>> way, using the same interface of the same program, and sent them
>> the same way?
>
> No, the first mail was created natively (= a new mail),
To clarify: the mail I li
Hi The Wanderer,
> Hans, are you certain you composed those three messages the same way,
> using the same interface of the same program, and sent them the same
> way?
No, the first mail was created natively (= a new mail), the one with the
"[SOLVED] in the subject was a reply to someones mail fro
On 2024-07-04 at 12:59, Thomas Hochstein wrote:
> Hans wrote:
>
>> Now I got my last mail back with the spam tag!
>
> That's very surprising.
>
>> X-Spam-Flag: YES
>> X-SPAM-FACTOR: DKIM
>> Authentication-Results: mail39c50.megamailservers.eu;
>> dkim=fail reason="signature verification failed
Hans wrote:
> Now I got my last mail back with the spam tag!
That's very surprising.
> X-Spam-Flag: YES
> X-SPAM-FACTOR: DKIM
> Authentication-Results: mail39c50.megamailservers.eu;
> dkim=fail reason="signature verification failed" (1024-bit key)
> header.d=megamailservers.eu header.i=@megama
Me again, sorry.
Now I got my last mail back with the spam tag!
Subject:
Re: *SPAM* [SOLVED] Re: This is a testmail!
This is the header:
X-Spam-Flag: YES
X-SPAM-FACTOR: DKIM
X-Envelope-From: bounce-debian-user=hans.ullrich=loop...@lists.debian.org
DMARC
My apologies for flooding the list with what should have been a private
mailing. Roger
Am Donnerstag, 4. Juli 2024, 13:58:07 CEST schrieb Hans:
Answering myself:
At the moment everything is looking fine.
Maybe after the big issue yesterday, the mail admins somewhere in the world
have fixed the problem? Dunno. Whatever, strange.
I will watch this in the future.
Let's close
eader.b=Kt+u3inW;
dmarc=none;
spf=none (spool.mail.gandi.net: domain of
"bounce-debian-user=debian=rogerprice@lists.debian.org" has no SPF policy
when checking 82.195.75.100)
smtp.mailfrom="bounce-debian-user=debian=rogerprice@lists.debian.org"
Hi folks,
this is a tes
Hmm, this is strange. Maybe I wrote my testmail from scratch.
This one is a reply as it have been, when the issue appeared.
Strangely my own testmail appeared without the SPAM tag this time.
Maybe there is a difference, if I am using a reply mail.
I will watch this and search for more informat
Subject and the content LGTM.
--
Best,
ID
On 2024-07-04 at 07:14, Hans wrote:
> Hi folks,
>
> this is a testmail, because I got some trouble with the mailingist.
> As reported before, I get all ,mails from
> debian-user@lists.debian.org with tagged with *SPAM added to
> the subject. This is because of som
Hi folks,
this is a testmail, because I got some trouble with the mailingist. As
reported before, I get all ,mails from debian-user@lists.debian.org with
tagged with *SPAM added to the subject. This is because of some DKIM
failure, as reported before. As I could fix this by setting a
15 matches
Mail list logo
