Re: External Systems - email

Josh Hillman ( (no email) )
Fri, 9 May 1997 17:32:38 -0400

> Why not create a service type that doesn't have an ES association
> with it and test with that type? Thats what I do.

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

> Josh Hillman wrote:
> >
> > Is there a way for Emerald to NOT create an emailbox for a newly
> > 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
> > service, eventhough that service normally would have one assigned to
it. I
> > frequently create (and later delete) services for testing purposes, but
> > I happen to create one, then add a real user later on, then run
> > 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
> > enter into the E-mail field (such as "none" or "null" or some
> > name) so that when Emerald runs the batch, it knows to NOT create a
> > for that service?