🚀 go-pugleaf

In article <7l123c$hf0$1@newsource.ihug.co.nz>, "James"
<smithies@ihug.co.nzZZZ> wrote:
> Simon Lyall <simon.lyall@ihug.co.nz.invalid> wrote in message
> news:7kv36f$25e$1@newsource.ihug.co.nz...
> > In ihug.general Bob Generic <anna-m@ihug.co.nz> wrote:
> > > One would assume, that if you do not want to received spam to your
> > > mailbox, just set it to spam@spam.com
> >
> > Best policy is to use an address that you know will be bogus. Recently a
> > New RFC came out that suggested you create and address that ended in
> > ".invalid" . In theory as time goes on software will automaticly recognize
> > these addresses and not even try to reply to them.
> >
> > You can just tack "invalid" onto you address (like this one) or you can
> > use something like spam@spam.invalid . As long as the address ends in
> > invalid.
>
> Forgive me if I'm totally being an idiot here, Simon...
> 
> But won't there also be bulk e-mail software that will just snip ".invalid"
> off the end, to get a valid e-mail address instead?
> 
> Or is the invalid tag something that software will add on to addresses that
> bounce mail back?
> 
> Just wondering :) Just seems a bit more sensible to use something at random,
> ie ihug.co.nz0384 or something. I guess that still puts load on your
> servers, maybe that's what you're trying to avoid?
> 

How would it place a load on IHUG's servers? If the domain is invalid
(like ihug.co.nz0384) then surely the message would never get to IHUG. The
spammer's SMTP server would not be able to find an IP for that domain and
the message would never be sent. An 'unable to be sent' message would be
sent to the spammer's mailbox, if they used a valid return address.

Cheers

-- 
Andy Kistler

Remove *NOSPAM* from email address to reply