Il 01/06/20 21:15, Mark Sapiro ha scritto:
The trace headers in the message you attached all indicate it was sent
and delivered to ada3167eb87301cb4835917425f07...@libero.it.
You're right, I overlooked those headers and took for granted the recipient
address I found from the MTA logs was the real one.
If this is
not a deliverable address for the end recipient, how did it get there?
Have you checked your MTA logs to see what is there for this reminder.
I.e., was anything sent to this address?
Ok, let's assume it is a deliverable address. Running the following one-liner
yields nothing:
# for i in /var/log/mail.log* ; do EXE=cat ; if [[ "$i" == *.gz ]] ; then EXE=zcat ; fi ;
echo "$EXE $i ---------------" ; $EXE $i | grep ada3167eb87301cb4835917425f07242 ; done
Command explained: look for the string ada3167eb87301cb4835917425f07242 into
all the the MTA logs and output the lines that contain it. Obviously my MTA
does log every recipient address it send messages to.
What was sent to the real list
member address?
Same one-liner above, with the message ID
0000000000123253.000000005ED46F3F.00004A46 as filter:
# for i in /var/log/mail.log* ; do EXE=cat ; if [[ "$i" == *.gz ]] ; then EXE=zcat ; fi ;
echo "$EXE $i ---------------" ; $EXE $i | grep
0000000000123253\.000000005ED46F3F\.00004A46 ; done
cat /var/log/mail.log ---------------
Jun 1 05:00:16 myhostname courierfilter:
zdkimfilter[19015]:id=0000000000123253.000000005ED46F3F.00004A46: response: 250
not filtered.
Jun 1 05:00:26 myhostname courierd:
newmsg,id=0000000000123253.000000005ED46F3F.00004A46: dns; myhostname.and.fqdn
([::1])
Jun 1 05:00:26 myhostname courierd:
started,id=0000000000123253.000000005ED46F3F.00004A46,from=<mailman-boun...@myhostname.and.fqdn>,module=esmtp,host=libero.it,addr=<real-list-mem...@libero.it>
Jun 1 05:00:27 myhostname courieresmtp:
id=0000000000123253.000000005ED46F3F.00004A46,from=<mailman-boun...@myhostname.and.fqdn>,addr=<real-list-mem...@libero.it>:
250 fagcjaRdEBNRlfagcj6sQm mail accepted for delivery
Jun 1 05:00:27 myhostname courieresmtp:
id=0000000000123253.000000005ED46F3F.00004A46,from=<mailman-boun...@myhostname.and.fqdn>,addr=<real-list-mem...@libero.it>,success:
delivered: smtp-in.libero.it [213.209.1.129]
Jun 1 05:00:27 myhostname courieresmtp:
id=0000000000123253.000000005ED46F3F.00004A46,from=<mailman-boun...@myhostname.and.fqdn>,addr=<real-list-mem...@libero.it>,status:
success
Jun 1 05:00:31 myhostname courierd:
completed,id=0000000000123253.000000005ED46F3F.00004A46
cat /var/log/mail.log.1 ---------------
zcat /var/log/mail.log.2.gz ---------------
zcat /var/log/mail.log.3.gz ---------------
zcat /var/log/mail.log.4.gz ---------------
I've replaced the real list member address with 'real-list-member', but it's
not the forged (or real) address above with the hex number and I've double
checked this one is really subscribed to the list.
It seems unlikely that some intermediary would rewirit the address to
ada3167eb87301cb4835917425f07...@libero.it everywhere in the message
headers and body including the line:
https://my.real.domain.where.i.host.mailman/options/my.real.list.name/ada3167eb87301cb4835917425f07242%40libero.it
It really looks like it came from your Mailman for that user.
I agree, but how?
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
