I use lists to accomplish what you are doing as others have said but I use our employee database to update the lists so you don't have to keep subscribing and unsuscribing users. I only have about 350 users but we have lots of turnover and its too much to keep up with.
 
I do this by having my SQL server do a DTS export to a text file (users.lst) every hour containing nothing but a list of everyone's email address for the list criteria. I then have that file copied over the list's users.lst file every hour.
 
You could do the same from excel, access or whatever manually
----- Original Message -----
From: Mike Goetz
Sent: Friday, March 02, 2001 4:39 PM
Subject: [IMail Forum] SMTP32.EXE Boom!

This is a strange problem.  We have about 200 users on our corporate mail server, which is running a Windows NT 4.0 Server machine with IMail 6.06.  We have created group aliases and have office users in their own respective groups, but we also have an ALL_USERS alias that sends to everyone that has an e-mail address on the server.  Sending to the smaller branch office lists, no problem.  Sending to All_Users?  The mail from the client end just shows the mail went out.  But if you happen to be next to the IMail server when you send to All_Users you’d see a Dr. Watson application error box pop up that says “SMTP.EXE has failed” etc.  It seems to be related to a large number of users in a group alias.

 

Has this happened to anyone before?  Anyone know what it could be?  Should I investigate doing a list instead?

 

Also, on a related question, is there a way to secure these aliases so that only certain people can send to these addresses?  What I‘ve had our managers do is just type the alias addresses in the BCC field to hide where it’s going but that secret won’t last. 

 

Thanks!

Reply via email to