Re: I'm curious, how does Amazon.com end up on the SCBL?
"Mike Easter" <[email protected]>
| Newsgroups | gmane.mail.spam.spamcop.user |
|---|---|
| Organization | SpamCop |
| Message-ID | <[email protected]> |
Pete wrote: Subject: I'm curious, how does Amazon.com end up on the SCBL? If you don't put your question where it belongs, in the body of your message, it isn't possible to answer the question in context without pasting your subject into the body of the reply. That isn't the correct way to write a news message or question. For practice and propriety in writing subjects and bodies, you can structure properly by writing the body first, then writing a brief subject to encapsulate or name/say what is contained in the body. That is, the subject should not be the only place to find the question or point of a post. <manufactured body question> > how does Amazon.com end up on the SCBL? 'It' amazon.com isn't on the SCbl, for several reasons. - amazon.com isn't an IP, SCbl lists IP addresses, not domains - the source IP 207.171.165.134 rDNS mm-retail-out-1102.amazon.com is *not* SCbl listed - rather it was tagged for listing because you configured to use sorbs lists > How does this happen? Pardon > my ignorance for how the system works. > Here is the URL for the block: www.spamcop.net/sc?id=z933385992z1be4a0540a738d21ef328cdc495cccc3z You can examine the Xlines for how your configuration of the spamcop filter blocked an item: X-SpamCop-Checked: 192.168.1.103 207.69.195.97 207.69.195.24 66.94.225.140 207.115.20.47 207.115.20.47 207.171.165.134 X-SpamCop-Disposition: Blocked dnsbl.sorbs.net That tells you that the last Xline IP 207.171.165.134 caused the item to be tagged for blocking from the inbox because it was listed in one of the sorbs blocklists. -- Mike Easter kibitzer, not SC admin