Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #270833 > unrolled thread

Results of Testmail_1-3

Back to article view | Back to linux.debian.user

Contents

  Results of Testmail_1-3 Hans <hans.ullrich@loop.de> - 2024-07-04 22:20 +0200
    Re: Results of Testmail_1-3 The Wanderer <wanderer@fastmail.fm> - 2024-07-04 22:20 +0200
    Re: Results of Testmail_1-3 Dan Purgert <dan@djph.net> - 2024-07-04 23:20 +0200
    Re: Results of Testmail_1-3 Michael Kjörling <c9bc136c6063@ewoof.net> - 2024-07-04 23:30 +0200
      Re: Results of Testmail_1-3 Max Nikulin <manikulin@gmail.com> - 2024-07-05 05:20 +0200
        Re: Results of Testmail_1-3 Keith Bainbridge <keithrbau@gmail.com> - 2024-07-05 08:00 +0200
          [SOLVED] Re: Results of Testmail_1-3 Hans <hans.ullrich@loop.de> - 2024-07-05 10:20 +0200

#270833 — Results of Testmail_1-3

So, these are th eresults:

1. A new created maiil does not have a spam tag.

2. Reply to my own mail does also not have a spam tag.

3. Reply to any user mail DOES have a spam tag.

So it looks like there is something , which some mailservers do not like. 

As I am sending only text from me, seldom the text of the users, I suppose, 
there is something in the header of the mail, which causes this issue.

I suppose, I can do nothing else but create a new mail and copy and paste from 
the received mail of the user. This should avoid the spam tag.

Weired thing at all.....

Hans

[toc] | [next] | [standalone]

#270834

[Multipart message — attachments visible in raw view] — view raw

On 2024-07-04 at 16:12, Hans wrote:

> So, these are th eresults:
> 
> 1. A new created maiil does not have a spam tag.
> 
> 2. Reply to my own mail does also not have a spam tag.
> 
> 3. Reply to any user mail DOES have a spam tag.
> 
> So it looks like there is something , which some mailservers do not
> like.
> 
> As I am sending only text from me, seldom the text of the users, I
> suppose, there is something in the header of the mail, which causes
> this issue.
> 
> I suppose, I can do nothing else but create a new mail and copy and
> paste from the received mail of the user. This should avoid the spam
> tag.

That will break threading, though, unless you manually set up your reply
to include In-Reply-To: and/or References: headers with proper contents
(which will depend on the message you're replying to). And for all we
know, doing that might bring the problem back.

> Weired thing at all.....

I would really recommend pursuing the cause with your mail provider, and
if they don't/won't fix it, considering switching mail providers.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#270842

[Multipart message — attachments visible in raw view] — view raw

On Jul 04, 2024, Hans wrote:
> So, these are th eresults:
> 
> 1. A new created maiil does not have a spam tag.
> 
> 2. Reply to my own mail does also not have a spam tag.
> 
> 3. Reply to any user mail DOES have a spam tag.
> 
> So it looks like there is something , which some mailservers do not like. 


Looking at your "test3" mail that you replied (and got ***SPAM*** on); I
see the following details (and a score of -5.8 vs. a target of 4.0)

  tests=DKIM_INVALID,DKIM_SIGNED,                                    
        MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,                                                    RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,URIBL_BLOCKED


The "DNSWL_HI" is the big help there, having a value of "-5". But even
without that, from the look of things, your message would only be about
a 0.2 thanks to the DKIM checks.  

  DKIM_INVALID => 0.1
  DKIM_SIGNED => 0.1

Note -- checked on spamassassin 3.4.6 running on Bullseye.

HTH 

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860

[toc] | [prev] | [next] | [standalone]

#270843

On 4 Jul 2024 22:12 +0200, from hans.ullrich@loop.de (Hans):
> Weired thing at all.....

This "testing" of yours, so far, involves about two dozen emails, each
of which sent to about 3000 people. (Yes, I realize that I'm adding to
the deluge; I do apologize. This will be my _only_ one in this thread.)

Seriously, do all the about 3000 subscribers to debian-user (plus the
about 500 who are subscribed to the digest version of the list)
_really_ need to take part in your testing? Do the list archives
really need to be cluttered up with all this, which has nothing
whatsoever to do with Debian even in the slightest and is of _no_
general interest to the Debian users community? Could you not have
determined by looking at the publicly accessible archives that
whatever mangling you might be seeing almost certainly does _not_
happen before a problematic email reaches the list server?

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

[toc] | [prev] | [next] | [standalone]

#270850

On 05/07/2024 04:27, Michael Kjörling wrote:
> On 4 Jul 2024 22:12 +0200, from Hans:
>> Weired thing at all.....
> 
> This "testing" of yours, so far, involves about two dozen emails, each
> of which sent to about 3000 people.

1. <https://www.debian.org/MailingLists/#codeofconduct>
> Do not send "test" messages to determine whether your mail client is working.

2. There is <https://lists.debian.org/debian-lists-test/> (side note: I 
believed, it was mentioned either on the page cited above or on 
<https://wiki.debian.org/DebianMailingLists>)

3. <https://www.debian.org/support#usenet>
> A lot of our mailing lists can be browsed as newsgroups, in the linux.debian.* hierarchy. 

is an alternative to fetch messages that do not pass through 
subscriber's mail provider. However not all headers may be available there

[toc] | [prev] | [next] | [standalone]

#270857

On 5/7/24 13:13, Max Nikulin wrote:
> On 05/07/2024 04:27, Michael Kjörling wrote:
>> On 4 Jul 2024 22:12 +0200, from Hans:
>>> Weired thing at all.....
>>
>> This "testing" of yours, so far, involves about two dozen emails, each
>> of which sent to about 3000 people.
>
> 1. <https://www.debian.org/MailingLists/#codeofconduct>
>> Do not send "test" messages to determine whether your mail client is 
>> working.
>
> 2. There is <https://lists.debian.org/debian-lists-test/> (side note: 
> I believed, it was mentioned either on the page cited above or on 
> <https://wiki.debian.org/DebianMailingLists>)
>
> 3. <https://www.debian.org/support#usenet>
>> A lot of our mailing lists can be browsed as newsgroups, in the 
>> linux.debian.* hierarchy. 
>
> is an alternative to fetch messages that do not pass through 
> subscriber's mail provider. However not all headers may be available 
> there
>

I wonder if the repeated replying to self has raised questions with the 
spam filters?

Hans,  do you have access to an alternate smtp server, maybe your ISP or 
gmail?

-- 
All the best

Keith Bainbridge

keithrbau@gmail.com
keith.bainbridge.3216@gmail.com
+61 (0)447 667 468

UTC + 10:00

[toc] | [prev] | [next] | [standalone]

#270858 — [SOLVED] Re: Results of Testmail_1-3

Hi folks,

first of all:  No, I can not change my provider nor use another smtp server.

second: I thought, this issue involves other people on this list, too, which 
might be interesting for them.

third: I supposed, this issue is caused by debian mailservers, because this 
issue appears ONLY at the debian list and nowhere else, I tested here.

fourth: As this issue seem only affect me, I suggest to close this discussion, 
because it creates a lot of unnecessary traffic.

So I set this to "solved" and won't ask further more.

Thank you everyone, for your patience and your help!

Best regards and have a nice weekend!

Hans 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web