SmartList in general, just doesn't work the way I believe you want it to
I've been using smartlist since 1994, I believe I like everything about it but a few minor details, one of which I'm trying to investigate by surveying a group of people who may have the same problems I have, i.e., SmartList managers.
For example, if I'm waiting for a response from address x, never send a request to x.
I do not understand what you mean by this; if you mean while waiting for confirmation the address will not receive list email, confirm does that. If
No, I explained the problem. I don't want 10 clicks of a submit page to drop 440 you have been subscribed messages into someone's mail box. Right now the worst that happens is they get 44 subscribed messages, a bunch of e-mails and 44 unsubscribed messages. With confirm, it would be possible for someone to have us do their dirty work and drop 4400 did you want to be subscribed messages into their mailbox. In other words, confirm aggravates the situation.
Check a reject list before sending.
The reject list is not checked prior to confirm's operation. Hence, it's possible to harass someone using the subscription mechanism.
initial question), I believe the answer is that SmartList will not operate the way you require.
I don't require that smartlist do it, merely that it is integrable into a smartlist environment. -- Greg Higgins higgins@peg.com