Hi guys,
Just a quick question. My (excellent) hosting company are in the process of moving to a new, better, server. They're changing from one control panel (VHCS2) to a new one (ispCP) at the same time.
ispCP creates several email addresses by default, including [email protected], [email protected] and [email protected]
The only issue is, the hosting company have those emails set up to forward to their own email account, for THEM to read. Fair enough they should know if someone is complaining about spamming etc (which I'd never do!). But isn't that what [email protected] is for?
The example I used to one of their staff was this: What if a long lost friend of mine (or anyone else) sees my site and wants to email me. They don't see my addy on the site, but decide to go pot luck and send a "long time no see" email to [email protected] or [email protected]. The hosting company has now intercepted my personal correspondence, which I believe is illegal under RIPA etc.
Surely if someone was getting spammed from a domain registered as residing on that hosting company's servers, a simple email to [email protected] would suffice? After all such info (abuse email etc) is posted on most whois records so long as the hosting company sets it up that way.
What do you all think? Am I over-reacting when I hate the idea that several email accounts on my own domain are forwarded to some outside third party without my consent?
All thoughts welcome
EDIT - the staff member concerned told me I could delete the webmaster@ and abuse@ addresses. but that they as the hosting company have the "rights" to the postmaster@mydomain addy as they run the SMTP server. Whaa?! I never heard that before?
Just a quick question. My (excellent) hosting company are in the process of moving to a new, better, server. They're changing from one control panel (VHCS2) to a new one (ispCP) at the same time.
ispCP creates several email addresses by default, including [email protected], [email protected] and [email protected]
The only issue is, the hosting company have those emails set up to forward to their own email account, for THEM to read. Fair enough they should know if someone is complaining about spamming etc (which I'd never do!). But isn't that what [email protected] is for?
The example I used to one of their staff was this: What if a long lost friend of mine (or anyone else) sees my site and wants to email me. They don't see my addy on the site, but decide to go pot luck and send a "long time no see" email to [email protected] or [email protected]. The hosting company has now intercepted my personal correspondence, which I believe is illegal under RIPA etc.
Surely if someone was getting spammed from a domain registered as residing on that hosting company's servers, a simple email to [email protected] would suffice? After all such info (abuse email etc) is posted on most whois records so long as the hosting company sets it up that way.
What do you all think? Am I over-reacting when I hate the idea that several email accounts on my own domain are forwarded to some outside third party without my consent?
All thoughts welcome
EDIT - the staff member concerned told me I could delete the webmaster@ and abuse@ addresses. but that they as the hosting company have the "rights" to the postmaster@mydomain addy as they run the SMTP server. Whaa?! I never heard that before?
Last edited:
The servers are awesome as well - great bandwidth and throughput, highly reliable etc, I really like them. They have a new UK datacentre server now too. I'm not complaining about that, especially for £12 a year