Thank you for the info.
Can we setup a rule that essentially says, if it is to hostmaster or abuse,
send it to whoever and that way give the client access to making, changing
aliases? Or would the rule be subject to override, in the event the
customer setup an alias of abuse. In other words, which takes precedence,
rules or aliases?
Thanks,
At 10:27 PM 3/27/00, you wrote:
>Hi,
>Answers in text:.....
>----- Original Message -----
>From: "Don Brown" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, March 27, 2000 10:33 PM
>Subject: [IMail Forum] Setup for Host/Content/App Provider
>
>
> > Hi Y'all (y'all is a defined word in Texas),
> >
>
>eh, is a defined word in Canada...
>
> > A ten minute (or less) conversation with someone who has been there would
> > be great, but failing to know anyone, maybe someone can take a few minutes
> > to give us some pointers.
> >
> > We are a hosting and development company. Almost all of our e-mail
>service
> > is Forward -- we just pass it through to the client's box at his ISP
> > (connectivity provider).
> >
> > Our mail server runs on separate box, apart from the box on which the web
> > site is hosted. So, we will not have a unique IP (MX) for each of the
> > Imail virtual domains.
> >
> > We would like some advice on the best way to accomplish the following:
> >
> > 1. We want to allow our customers to use a web interface to do their own
> > configuration (i.e. adding/changing forward addresses, etc.), but we don't
> > want them to be able to create a pop account. I'm guessing that there is
> > some flexibility to do that . .
> >
>when you create a user, DON'T tick the 'Host Administrator' or 'System
>Administrator' boxes.
>This disables 'creating new users' and 'Alias administration'
>
>
> > 2. In every case we want everything addressed to Hostmaster and to Abuse,
> > to come to us. We don't want the customer to be able to do anything to
> > redirect those messages. Ditto, in most but not all cases, for anything
> > addresses to Webmaster.
>
>Just set these up in your alias administrator. The customer can't change
>these as per above answer (1)
>
> >
> > 3. If something is addressed to [EMAIL PROTECTED] and johnnnnnn is not
> > a defined forward or pop, then we want it to go to a default forwarding
> > account/user for that particular domain.
>
>Create an alias called 'nobody' and direct it's output to the desired REAL
>user.
>The nobody alias is special, and catches everything which is not
>specifically addressed. Officially this is called a 'catch all' but it
>should be called a 'catch rest'.
>
>Anthony
>
> >
> > We RTFM and looked through the knowledge base, but we would like to hear
> > from users with experience. It will be appreciated.
> >
> > Thanks,
> > --
> > Don Brown - Dallas, Texas USA Internet Concepts, Inc.
> > [EMAIL PROTECTED] http://www.inetconcepts.net
> > PGP Key ID: 04C99A55 (972) 788-2364 Fax: (972) 788-5049
> > PGP Fingerprint: 2A72 3C0F D3F4 5086 E588 89BA 7353 1710 04C9 9A55
> > PGP Key Servers: http://pgpkeys.mit.edu:11371 ldap://certserver.pgp.com
> > --
> >
> > Please visit http://www.ipswitch.com/support/mailing-lists.html
> > to be removed from this list.
> >
>
>Please visit http://www.ipswitch.com/support/mailing-lists.html
>to be removed from this list.
--
Don Brown - Dallas, Texas USA Internet Concepts, Inc.
[EMAIL PROTECTED] http://www.inetconcepts.net
PGP Key ID: 04C99A55 (972) 788-2364 Fax: (972) 788-5049
PGP Fingerprint: 2A72 3C0F D3F4 5086 E588 89BA 7353 1710 04C9 9A55
PGP Key Servers: http://pgpkeys.mit.edu:11371 ldap://certserver.pgp.com
--
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
