Hence, some emails may have 10-25 lines of "To" entries, as well as everybody's email address is provided to those that use webnotify.

My first idea was to have the To: changed to a "bit bucket" address, and then place all the entries in a Bcc: line. But it was brought to my attention that some mail servers, will not accept mail that have "undisclosed" receipients or too many "undiscolosed" receipients. So, I guess the next alternative may be to actually email each person indvidually rather than a group. I know this may cause more overhead, but most MTAs are now improving to the point that they will do parallel sending so each message doesn't have to reconnect to the same remote mailserver multiple times if the messages are queued in a fashion that the connections can be cached.

PeterThoeny has commented that the blocking of Bcc is usually done by mail filters, this clarifies why one should not use BCC: "Some have mail filters rejecting anything that is not TO or CC recipient."

Maybe the individuals being emailed can be examined, and all the users @domain1 can be submitted sequentially; so if the MTA has a connection to that domain it will not have to reestablish connections, and send all the emails over the one connection.

Other alternatives are the end user could use some form of filtering such as procmail or maildrop; to manipulate the email or use MUA configuration options to not display the To header (at some loss) -- but I would like to see Twiki try and improve the readability of the emails by reducing the amount of unnecessary info within the email.

-- ErrolCasey - 05 Jun 2002