The "documentation" is a brief email that I sent with their login/password.
they have to at least once read the email if they want the access info.

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of ## Dusty Carden
> Sent: Friday, June 25, 1999 8:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [IMail Forum] [EMAIL PROTECTED] - WANT
> TO AVOID
>
>
> Question is... how do you get them to "read" the documentation? <g>
>
> Dusty
>
> ----- Original Message -----
> From: Robert E. Spivack <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 24, 1999 3:43 AM
> Subject: RE: [IMail Forum] [EMAIL PROTECTED] - WANT TO
> AVOID
>
>
> > One addition:
> >
> > I run only virtual domains, about 200 of them, and have found that many
> > email client software doesn't handle the
> > login [EMAIL PROTECTED] well, so I pro-actively tell all
> my users to
> > always login using username%somedomain.com since the % will always work.
> >
> > It just takes a little pro-active documentation to explain that their
> > 'public' address is [EMAIL PROTECTED], but ONLY for logging in from
> their
> > software, they must use user%somedomain.com
>
>
>

Reply via email to