At 9:31 AM -0500 1/29/05, John E. Malmberg wrote:
Somehow the vmsperl mailing list got into the spamcop.net list.
(reason: 530 5.7.1 Blocked - see http://www.spamcop.net/bl.shtml?63.238.179.181:
This has happened from time to time, but the address you show here is not the address of lists.develooper.com, the MTA for all the Perl mailing lists. 63.238.179.181 is for called qsl.net, which is where you are sending mail from.
I am sorry, I should have noticed that it was my mail relay service I.P. address.
But I am not sending from that I.P. address. The only e-mail that originates from that I.P. address is that of the owner of the QSL.NET service.
All other e-mail from that I.P. address will only go to members of the QSL.NET service.
So it must have been a member of QSL.NET that reported their own mail relay. Unless of course that QSL.NET had a security breach, which I doubt.
As I am double subscribed to this list, I did not miss anything.
I usually subscribe to mailing lists with the qsl.net e-mail address set to no mail because the QSL.NET spam filters are too aggressive for mailing lists, and sometimes will reject real e-mail from them, but just use qsl.net for posting because of the same spam filters foil most of the harvesting and worms.
That no-mail option is not available on this mailing list.
I will see if the encompasserve.org postmaster will whitelist the qsl.net I.P. address which will prevent this condition from happening the next time a qsl.net member has an accident.
-John [EMAIL PROTECTED] Personal Opinion Only
