[quote user="tomt"]But how do you manage email for 100+ domains using Mercury ?
I though if you created a user account, the that user would apply to all domains ![/quote]
Absolutely not a silly question.
We compose the mailboxes as mXXXX###, where XXXX is the customer number, and ### is a running ID. Using this as email addresses makes very little sense, though you're correct, any domain hosted on each instance of Mercury can use this combination as a valid address. We do not expose this to the end-users, we expose all through aliases. Sure this fact is somewhat a thorn in the eye, but it is merely a technical problem - until some vicked person decides to abuse our system. The alias is composed as the customer wants the address or adresses formed. Some prefer initials, some other have full names etc. By doing this scenario, it is very easy to explain that a mailbox (referred to as a maildrop in the RFCs) can host any number of addresses, just as a traditional mailbox along the road. We also use the aliases for off-site routes, aka relays, with valid local domain address, routing the mesage off host. It also makes it easy to connect several customer domains into just one maildrop. It is very popular here to have domains under .se, .eu, .com and so forth, having them all point to the same maildrop for each individual.
When a customer wants a mailing list, for ex. info@domain.com routed to a party of three, we do set this up as a mailing list. Naming the list as XXXX.info (where XXXX again is the customer number) with real address XXXX.info@domain.com and do set up an alias relaying info@domain.com to XXXX.info@domain.com.
All information is handled in a separate database accesible over the web, connects domains to the customer, settin up DNS, maildrops, passwords, autoreplies etc. All is synched through separate synchronizing programs, the Pascal source for one of them (a somewhat older version) is downloadable from this site.
Hope this answered your questions, if not fire away.
[quote user="tomt"]But how do you manage email for 100+ domains using Mercury ?
I though if you created a user account, the that user would apply to all domains ![/quote]
<P>Absolutely not a silly question.
We compose the mailboxes as mXXXX###, where XXXX is the customer number, and ### is&nbsp;a running ID. Using this as email addresses makes very little sense, though you're correct, any domain hosted on each instance of Mercury can use this combination as a valid address. We do not expose this to the end-users, we expose all through aliases. Sure this fact is somewhat a thorn in the eye, but it is merely a technical problem - until some vicked person decides to abuse our system. The alias is composed as the customer wants the address or adresses formed. Some prefer initials, some other have full names etc. By doing this scenario, it is very easy to explain that a mailbox (referred to as a maildrop in the RFCs) can host any number of addresses, just as a traditional mailbox along the road. We also use the aliases for off-site routes, aka relays, with valid local domain address, routing the mesage off host. It also makes it easy to connect several customer domains into just one maildrop. It is very popular here to have domains under .se, .eu, .com and so forth, having them all point to the same maildrop for each individual.</P>
<P>When a customer wants a mailing list, for ex. <A href="mailto:info@domain.com">info@domain.com</A> routed to a party of three, we do set this up as a mailing list. Naming the list as XXXX.info (where XXXX again is the customer number) with real address <A href="mailto:XXXX.info@domain.com">XXXX.info@domain.com</A> and do set up an alias relaying <A href="mailto:info@domain.com">info@domain.com</A> to <A href="mailto:XXXX.info@domain.com">XXXX.info@domain.com</A>.</P>
<P>All information is handled in a separate database accesible over the web, connects&nbsp;domains to the customer, settin up DNS, maildrops, passwords, autoreplies etc. All is synched through separate synchronizing programs, the Pascal source for one of them (a somewhat older version) is downloadable from this site.</P>
<P>Hope this answered your questions, if not fire away.</P>
