On 9/10/2022 8:37 AM, Julian H. Stacey wrote:
No known instances of members reporting us as spam.
Un-realised reports are worse, where you only later discover your domain name or an IP number has been falsely listed.
I searched for a tool to periodically run, to automatically scan with a list of RBL providers, whether any RBL has silently listed your domain names or numbers: http://www.anti-abuse.org/multi-rbl-check/ https://mxtoolbox.com/blacklists.aspx https://rspamd.com/doc/modules/rbl.html Any recommendations ?
Opinion: Bad enough that some commercial companies profit by dumping their admin problems on the innocent far end. Worse that the far end may be an unpaid organisation, so companies steal time from volunteer admins. Worst are fake RBL lists, criminal libelling for profit http://berklix.org/~jhs/mail/sorbs/
I have list members who admitted incompetence to unsubscribe majordomo, less with mailman. Worse were the lazy who refused to learn, demanding to waste volunteer admin time for manual help. Procmail rules discarded their noise. Worst were malicious faked reports to black listers.
Cheers,
I do not have the entire thread here, but I have had an experience with at&t. My e-mail address is @att.net, and I login to the web a few times a month - once to see my bill, and maybe two times to look at my spam folder. More than half of the time, the web site does not accept my password, and I cannot use the "change password" link. So I call the 800 support number and get a new temporary password. I am assuming that one or more persons is/are trying to login to my account, and thus my account is getting "frozen". Last Saturday night it happened, and I called support. I was told that they could not give me a new password over the phone; they would have to put a temporary password in the USPS mail. This is a new policy that started a few days before mu call. The support person to whom I talked said that at&t was trying to block IP addresses from where these login attempts are coming. I have no idea if this is related to the problem that started this thread.
--Barry Finkel