Devuan bug report logs - #388
Duplicate bugs created from single submit@bugs.d.o message

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Dimitris <dimitris@stinpriza.org>
Subject: bug#388 closed by Mark Hindley <mark@hindley.org.uk> (Re:
 bug#388: twice again...)
Message-ID: <handler.388.D388.167457969114814.notifdone@bugs.devuan.org>
References: <Y9AOlGKbG1/7MSI3@hindley.org.uk>
 <df972f20-133d-da2f-5984-aa1d8a3ccd32@stinpriza.org>
X-Devuan-PR-Message: they-closed 388
X-Devuan-PR-Package: bugs.devuan.org
X-Devuan-PR-Keywords: moreinfo
Reply-To: 388@bugs.devuan.org
Date: Tue, 24 Jan 2023 17:02:04 +0000
Content-Type: multipart/mixed; boundary="----------=_1674579724-14829-1"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the bugs.devuan.org package:

#388: Duplicate bugs created from single submit@bugs.d.o message

It has been closed by Mark Hindley <mark@hindley.org.uk>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.


-- 
388: https://bugs.devuan.org/cgi/bugreport.cgi?bug=388
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: Dimitris <dimitris@stinpriza.org>, 388-done@bugs.devuan.org

Subject: Re: bug#388: twice again...

Date: Tue, 24 Jan 2023 17:00:04 +0000

On Sun, Feb 23, 2020 at 03:30:56PM +0200, Dimitris wrote:
> On 2/23/20 3:10 PM, Mark Hindley wrote:
> > You appear to be using the Thunderbird Autocrypt addon. This is adding a
> > duplicate To: header to your email. And that means the email is handled twice by
> > debbugs.
> 
> aha! nice catch.
> autocrypt is indeed integrated in enigmail addon, so i could add
> per-recient rules to send unsigned to submit@b.d.o .

Closing as resolved.

Mark

[Message part 3 (message/rfc822, inline)]

From: Dimitris <dimitris@stinpriza.org>

To: submit@bugs.devuan.org

Subject: bugs.devuan.org using mass mailer Entity, classified as spam..

Date: Fri, 31 Jan 2020 15:52:09 +0200

[Message part 4 (text/plain, inline)]

Package: bugs.devuan.org

hey,

i don't know when this change happened, but i see bugs.devuan.org using
" X-Mailer: MIME-tools 5.509 (Entity 5.509) "

which is clarified as spam in some systems, because of "Entity".
a very common rule for mass mailers in email header_checks.. our own rule :

/^X-Mailer:.*\b(0001|Aristotle|Avalanche|Blaster|Bomber|Crescent
Internet Tool|DejaVu|DiffondiCool|E-Mail Delivery Agent|Emailer
Platinum|eMerge|Entity|Extractor|UltraMail|Sonic|Floodgate|GeoList|GOTO
Software
Sarbacane|Mach10|MailWorkz|MassE-Mail|MaxBulk.Mailer|MDaemon|MegaPro|Aureate|MultiMailer|News
Breaker Pro|SmartMailer|StormPort|SuperMail-2|Bluecom|Achi-Kochi
Mail|Direct Email |Andrew's SuperCool Blastoise|MailerGear|Advanced Mass
Sender|SpireMail|UltimDBMail|Mabry)\b/	REJECT No mass mailers allowed.
You are probably sending spam


came accross this, when i saw that an old bug was closed, and according
to bugs.d.o i was notified, but never got an email..
so, looked into mail.log and found out why.

it wasn't like that before, see following examples :

newest blocked message with entity x-mailer :
https://bugs.devuan.org/cgi/bugreport.cgi?bug=306;msg=19

older message received normally, without x-mailer header :
https://bugs.devuan.org/cgi/bugreport.cgi?bug=240;msg=9

thanks,
d.

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.