From: "Robin H. Johnson" <robbat2@gentoo.org>
To: mlmmj@mlmmj.org
Subject: [mlmmj] Misleading operations log output: moderation & more
Date: Tue, 13 Feb 2018 21:33:19 +0000 [thread overview]
Message-ID: <robbat2-20180213T212446-133084908Z@orbis-terrarum.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
Hi,
Recently saw some behavior that was unclear.
The gentoo-dev-announce list is configured as an announce list.
subonlypost, notoccdenymails, nosubonlydenymails, noaccessdenymails,
moderated.
access:
- (lots of deny lines)
- moderate ^From: .*@gentoo.org
- deny
The user was subscribed as username@gentoo.org, but sent their mail with
a plus-address suffix in From. The plus-address was not subscribed.
Log output: (wrapped for reading)
mlmmj-process:
access - A mail from "username+gentoo-dev@gentoo.org" with
header "From: A User <username+gentoo-dev@gentoo.org>" was
moderated by rule #18 "moderate ^From: .*@gentoo.org"
That was the only log line, and then it seemed to vanish.
What happened is that subonlypost was applied AFTER the access was
processed, and did not log that it decided to drop the mail.
I think that there should be a log message stating it was dropped.
Relatedly, if you try to sub an address that is already on a list, there
should be a log message (and likewise for unsub).
P.S.
'A mail' is also ambiguous on busy lists, since you could have multiple
mails being processed at the same time, need to figure out something to
describe which mail is in logging.
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next reply other threads:[~2018-02-13 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 21:33 Robin H. Johnson [this message]
2018-02-14 11:58 ` [mlmmj] Misleading operations log output: moderation & more Ben Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=robbat2-20180213T212446-133084908Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).