I think I know what is happening , but I want to make sure. A bunch of my list 
admins are getting bounces like below?

I think it is someone or probably a BOT, trying to subscribe to our lists, But 
they are using a bad email address so it bounces to the admin. (Our lists are 
set to confirm/approve for joining).  I assume they are just trying to join any 
lists that don’t have confirm/approve to see if they can then get the users of 
the list, maybe, What else could they be trying to do?

I have seen a couple of different bad emails addresses used, so I just can’t 
ban this one,  I am telling list admins to ignore them. But if they get worse I 
think they can set this setting to “NO”

Should Mailman send you, the list owner, any bounce messages that failed to be 
detected by the bounce processor? Yes is recommended.
(Details for bounce_unrecognized_goes_to_list_owner)

Which would stop these notifications? But it is recommended to leave it to 
“yes”.


Any other options ideas?  Am I on the right track?


Here is a bounce example with  our list info stripped.

***********************************
Error: Invalid user address

Error message below:
550 - Requested action not taken: no such user here

Message details:
  Subject: confirm 174c7e02aa6603b72ba30e59c5e24c7fceebd826
  Sent date: Wed Apr 14 23:08:48 UTC 2021
  MAIL FROM: xxx-software-xxx-boun...@mailman.xxx.xxx
  RCPT TO: 17323547...@vtext.com<mailto:17323547...@vtext.com>
  From:
< XXX-software-XXX-request@ mailman.XXX.XXX >

  To:
<17323547...@vtext.com<mailto:17323547...@vtext.com>>

  Size: 11.3 KiB


------------------------------------------------------
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/

Reply via email to