Sometimes I do that, but every once in a while, someone will get a normal
PPP account (or some other) but already have an email address somewhere
else and don't want one locally, so in that case, it's pointless to have it
automatically create a mailbox. Currently, I just go and delete the
mailboxes if I remember about it...
BTW Dale, on an unrelated note, did you find out anything the other day
regarding the Ascend-Maximum-Time problem? Just curious.
Josh Hillman
hillman@talstar.com
> Josh Hillman wrote:
> >
> > Is there a way for Emerald to NOT create an emailbox for a newly
created
> > service when "batching accounts?" This isn't the norm, but it'd be
nice if
> > there were a way to have Emerald skip the creation of an emailbox for
new
> > service, eventhough that service normally would have one assigned to
it. I
> > frequently create (and later delete) services for testing purposes, but
if
> > I happen to create one, then add a real user later on, then run
External
> > Systems / Batch Accounts, an emailbox will have been created for the
> > testing service.
> >
> > In a future release of Emerald, would it be possible to have a keyword
to
> > enter into the E-mail field (such as "none" or "null" or some
user-defined
> > name) so that when Emerald runs the batch, it knows to NOT create a
mailbox
> > for that service?