Re: Spam "from" reserved netblocks

Geoff Lane wrote:
> "Mike Easter" <[email protected]> wrote in news:dam7ma$mtj$1
> @news.spamcop.net:
> 
> 
>>I can also see that the item was /not/ parsed as a mailhost
>>configuration, another issue which is afoot here.
> 
> 
> I would set up mailhost configuration but I don't know how to do that. The 
> instructions seem to want me to carry out a configuration for every email 
> address that may receive mail. However, I have unlimited addresses for each 
> of several domains, so I can't achieve what I infer to be required.
> 
> Perhaps a key here is that the term "account" is not adequately defined. Is 
> an "account" a Spamcop account, a user account on my local mail server, an 
> ISP account, an email address (no matter whether that corresponds to a 
> configured local user account), etc?

Account in this case is at least at ISP level.

It may actually be at spamcop account level and trust all MTAs that you
set up for that SpamCop account, no matter the path the mail takes
through them. Not sure on this, but it would explain some behavior that
I've seen with the system dealing with things I would expect it to fail on.

> 
> If an "account" is an ISP account, what do I need to do if my ISP uses a 
> server farm and mail be sent to and received from a variety of servers that 
> may have dynamic addresses and for which the number of hosts and IP 
> addresses are hidden from me?

Depends on the ISP. It's highly likely that SC knows about all of the
mail servers for your ISP and will handle them automagically when you go
through the setup. It did for my ISPs, even though it was only trained
with a single email through each one.

-- 
Evidence shows Cyveillance abuse internet resources.
I recommend unchecking their box in SpamCop reports.
Cyveillance are part of the problem.
They are not part of the solution.