A question - related to Re: hughes.net filtering content for spam

On 5/8/2006 4:17 PM Tom Morrissey scribbled:

> A week or so back I presented this forum with an SMTP Server Error: 554,
> Error Number: 0x800CCC6F that I was getting when I tried to send spam
> reports (quick or otherwise) to SC through SMTP.hughes.net using OE as my
> mail client.
> 
> After much VERY painful dialogue with various (way too many) hughes.net
> support staff I finally got somebody who should know to admit to the fact
> that hughes.net was filtering both outgoing and incoming email content and
> flat refusing to send on mail it identified as spam.  This filter is
> trapping my spam reports containing the spam as .eml attachments under these
> criteria and giving me the message described above.
> 
> Lucky for me I have other smtp paths through which I can report spam to SC.
> It is an interesting situation though.
> 
> I don't use my hughes.net incoming mail account so I don't really "benefit"
> from the service, instead I'm just hampered from reporting spam through
> their smtp server to SC that I happen to get through other incoming paths.
> 
> 
Cox is doing the same thing, started 2-3 months ago on outgoing -
everything I was sending out hit the floor.  2 weeks ago, my spam dried
up - I posted the fact here, at first in wonderment.  Cox sent an email
to their customers about 4-5 days after they started using new filters
on incoming.  Everyone is forced to use a webmail account to go and
clean out the spam box.  Just today I noticed a forwarding setting I'm
thinking about exploring.

Does anyone know if I can take my special SC address and try to forward
to it?  Or is entering it into their system a SC no-no?  Cox will
probably block it, but worth the try...