#11486 java-devel list not showing my emails
Closed: Fixed 7 months ago by kevin. Opened 10 months ago by jwhimpel.

At 10:54 -0500 on Tue, 22 Aug 2023, I sent an email to java-devel@lists@lists.fedoraproject.org and server@lists.fedoraproject.org. The subject line reads "JEE Development Environment question".

The email shows on the server@lists.fedoraproject.org but not at java-devel@lists.fedoraproject.org.

Another user in a private email to me said he also had email not showing in java-devel@lists.fedoraproject.org.

My email address is john@jlhimpel.net.

Evolution shows the following header info:
Message-Id: eb90e57dbc186ea9d63453578df9f60a5d0ca9ed.camel@jlhimpel.net
Subject: JEE Development Environment question
From: John W. Himpel john@jlhimpel.net
Reply-To: john@jlhimpel.net
To: java-devel@lists.fedoraproject.org, server@lists.fedoraproject.org
Date: Tue, 22 Aug 2023 10:54:45 -0500
Organization: Himpel Family
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38)
Mime-Version: 1.0
X-Evolution-Identity: 1361220416.1873.0@dubby.jlhimpel.net
X-Evolution-Fcc: folder://1312347391.14090.21%40dubby.jlhimpel.net/INBOX
X-Evolution-Transport: 1361220416.1873.1@dubby.jlhimpel.net

Describe what you would like us to do:

Please investigate if java-devel@lists.fedoraproject.org is having issues.

When do you need this to be done by? (YYYY/MM/DD)

Not an urgent priority, but would like feedback as it is my primary source for Fedora java support questions/issues.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

10 months ago

I can see it discarded it, but I can't see why. ;(

Aug 22 15:54:47 2023 (1490) DISCARD: <eb90e57dbc186ea9d63453578df9f60a5d0ca9ed.camel@jlhimpel.
net> {'moderation_sender': 'john@jlhimpel.net', '_parsemsg': False, 'version': 3, 'lang': 'en', 'moderation_reasons': [('Header "{}" matched a header rule', 'No, score=0.8 required=5.0 tests=BAYES_50,SPF_HELO_NONE\r\n\tautolearn=no autolearn_force=no version=3.4.0')], 'received_time': datetime.datetime(2023, 8, 22, 15, 54, 47, 419199), 'original_size': 2413, 'envsender': 'noreply@lists.fedoraproject.org', 'to_list': True, 'listid': 'java-devel.lists.fedoraproject.org', 'rule_hits': ['header-match-java-devel.lists.fedoraproject.org-2'], 'rule_misses': ['dmarc-mitigation', 'no-senders', 'approved', 'emergency', 'loop', 'banned-address', 'member-moderation', 'header-match-config-1', 'header-match-config-2', 'header-match-config-3', 'header-match-java-devel.lists.fedoraproject.org-0', 'header-match-java-devel.lists.fedoraproject.org-1']}

I don't see anywhere a 'header-match-java-devel.lists.fedoraproject.org-2' rule. ;(

Metadata Update from @abompard:
- Issue assigned to abompard

9 months ago

Metadata Update from @abompard:
- Issue assigned to abompard

9 months ago

Hey! Thanks for the detailed info, and for the log search Kevin.
In the list admin on the header filter page, I see a rule on the 2nd line that matches on the header x-redhat-spam-score with pattern [3-9]. I think this is the culprit. If I look at the header value in the log message, it looks like it contains much more that the raw score number, so the regex is probably matching all the time at least with required=5.0.
Note that it's the second header filter in the list, which would match the rule name ending in -2.

I'm not sure when emails go through redhat's spamassassin before reaching mailman, but it looks like some do, at least.

There are other lists that seem to have a widely matching regex:

# select list_id, header, pattern from headermatch join mailinglist on mailinglist.id = headermatch.mailing_list_id where header  = 'x-redhat-spam-score' ;
                 list_id                  |       header        | pattern 
 security.lists.fedoraproject.org         | x-redhat-spam-score | .*\*
 security-commits.lists.fedoraproject.org | x-redhat-spam-score | .*\*\*
 java-devel.lists.fedoraproject.org       | x-redhat-spam-score | [3-9]

Hope that helps!

I've just deleted that rule... can you try posting again now?

If you still can't post, please re-open this or file a new issue. I'm hoping it's fixed. :)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 months ago

Log in to comment on this ticket.

Boards 1
ops Status: Backlog