There are better scripts for creating contacts in the AD... there should be
one on cdolive.com that imports data from a spreadsheet. But that is not the
problem- managing a large # of contacts in exchange is the problem -
especially if he wants any sort of categorization. Editing and deleting when
is also a PITA - can't just open outlook and make changes like you can in
the contact folder.

A list server, such as available from lsoft.com, is much better. They sell a
lite version that might work ok for 27,000 contacts, but it's probably
better limited to about 5000. (I use it for 2800 subscribers.) Bulk mail
apps will also work well and should be able to easily handle 27,000
messages. Outlook would take days to send that many.

A list server can handle bounces much better - as sue said, you'll get
bounces and it's better if the software processes them and deletes the
address. On the two lists I run (12000 total subscribers), it's more like
2 -4% - around 400 total bounces per mailing. The software removes the
addresses for me after 2 consecutive bounces.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"F.H. Muffman" wrote in message
...
Diane Poremsky [MVP] wrote:
Honestly, if price isn't an issue, I'd buy a copy of Exchange and
make all the contacts Custom Recipients (if that's still the term)
in the Global Address list. You could then set up a locked down
distribution list, and even a custom method for users to unsubscribe.

Conversely, you could really use any sort of server based LISTSERV
type program.

Personally, I don't think Outlook is really designed for a
newsletter type spam system. Sure you can shoehorn it in there,
but, you can shoehorn a database into Excel too, but, it should
really be done in SQL Server (or access).

importing them into exchange gal would be a nightmare. a list server
or mail application designed for sending mass mail would be a much
better option

I didn't think it'd be a nightmare with powershell in exchange 2007, and
for 2000 and 2003,
http://groups.msn.com/windowsscript/...&sorts tring=
looks pretty easy.

=)

--
f.h.