On Sunday 12 November 2006 12:43, K.J. Petrie (Instabook) wrote:
I have a domain. Let's call it example.com, and I have an ISP (call them
dirtcheapbroadband.net). Dirtcheapbroadband give me a POP mailbox as part
of the service at myname(_at_)dirtcheapbroadband(_dot_)net(_dot_) However, I
want to send
and receive mail as anything(_at_)example(_dot_)com(_dot_) So I set up an
domainparkingishere.net to forward all mail addressed to
myname(_at_)dirtcheapbroadband(_dot_)net(_dot_) I send my outgoing mail
dirtcheapbroadband.net's server, which doesn't seem to mind my From
identity not being a dirtcheapbroadband.net one.
I suspect that you will find that dirtcheapbroadband.net will eventually
notice too much spam coming from domainparkingishere.net and block them.
I used to do this for my father via my domain host to his AOL account.
Eventually my webserver got blocked by AOL.
It's a much easier solution to pick a domain host that offers mailboxes and
pop the mail direct from there. If you really want it all delivered to you
locally, you can use something like fetchmail to pull all the messages to
I see your point, but I think that you are missing one important issue...
The relationship between the forwarder and the receiver is a trust
relationship. If your ISP gave you an option to whitelist certain
forwarders, it would be based on your trust of the forwarder. If they did it
globally, it would be based on their trust of the forwarder. Such trust
relationships cannot be established via a standardized protocol.
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
please go to http://v2.listbox.com/member/?list_id=735