> | |> | Your mailing list is intrinsically linked with marketers, AKA > | spammers. > | |> | I will not post to your mailing list again under these circumstances. > | |> | You are generating a spam problem and you need to monitor DNS > traffic. > | | > | |> Any public mailinglist is by it's definition public. So there is no way > | |> to prevent people from using it to do the wrong thing with the > | |> information on any public mailinglist. > | | > | | I think you misunderstood what I was saying. > | | I was ONLY referring to the gratuitous DNS traffic I got when I post > | to the > | | list. This was immediate and repeatable, so it indicates it was > | initiated on the > | | list server end. > | | I can only conclude this behavior is by design, or your server is > | compromised. > | | You may not even realize this is happening. > | > | It is not my server. It seems you assumtion is not correct in this matter. > | > | Have you considered that some people verify the sender of a message. It > | should only verify the sender (which is the mailinglist) but I noticed > | some read the From: header and verify those. > > I think you may want to learn that "Sender ID Framework" actually works > this way. So it seems there are SIDF users on the mailinglist. > > I guess there are some Exchange users here.
I get a 'digest' of the list and only the "body" contains my email address but some users may get each individual posting relayed immediately from the original sender. I sure don't like it, but in that case, there are numerous legitimate mechanisms which would explain DNS traffic like I saw. The most obvious cure is still the easiest. I'm outa here... Bye... Marty B. -- Electile Dysfunction : the inability to become aroused over any of the choices for President put forth by either party in the 2008 election.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
