On 7 Nov 2008, at 20:08, Martin Strand wrote:
We're an email service provider hosting ~3000 domains. Customers can
delegate their domains to our nameservers and administer email
accounts with a web interface.
I figured it would be a good idea to reserve the postmaster@ and
abuse@ addresses for hosted domains and forward them to our own
postmaster account.
Now one of these customers wants to create a
[EMAIL PROTECTED] account and use it for his personal email...
I just want to ask what you guys think about this policy, am I just
being silly when reserving these addresses in the customer's own
domain? Should I drop that restriction and leave their domains alone?
In general, instead of reserving [EMAIL PROTECTED] and [EMAIL PROTECTED], I
would instead set those mailboxes up with a BCC or similar to your own
mailboxes. Then if the customer wants to set them up for him/herself,
they can. If I were a customer of yours, I would want to be able to
see what arrives at those mailboxes as well (for any number of reasons).
That said, a couple points:
1. I would advise your customer not to use [EMAIL PROTECTED] as a
personal mailbox.
2. If you do make the arrangement I recommend above, the fact that all
his personal mail is going to your mailbox might be enough to dissuade
him.
For all but one of your customers, the BCC-ing (or however you choose
to do it) is a pure gain for them, since now they can do a little more
than they could do before. For this one customer...well, other people/
admins are going to treat the [EMAIL PROTECTED] as the postmaster
address, regardless of how he decides to use it; and as a result, you
are somewhat obligated to too.
Anyways...those are just my thoughts on the matter. It's obviously up
to you.
-Neil.
