"KEVIN ZEMBOWER" <KZEMBOWER@jhuccp.org> writes:
I still think that what I want to do is not a great departure from what many folks might like a mailing list system to do. I have a input text box on a web page where viewers can fill in their email address if they want to be notified when the page changes. My simple perl script appends their email address to a flat file that has one email address per line. I'd like to be able to use this file of email addresses as the distribution list for SmartList. However, I'd like SmartList to handle the bounces. I'd also like to be able to have users subscribe and unsubscribe directly to the -request address. My perl script wouldn't "care" if another program, such as SmartList, were also adding and deleting lines.
Let's turn your question around: why isn't your perl script following SmartList dist file format? It should 'obviously' never remove anyone above the "(Only addresses...)" line; it should not alter that line; it add new addresses at the bottom of the file; it **MUST** follow SmartList's locking convention. Altering your perl script it almost certainly simpler and *safer* than trying to change SmartList's conventions. Those rules are, after all, coded into most of the scripts and rcfiles that comes with SmartList. BTW: can you tell your mailer to wrap the text of your paragraphs? You're sending message with lines that are more than 700 characters long! Write too long a paragraph and your message will go over the 1000 character limit in rfc 822 (and now rfc 2822), at which point it'll either be bounced, dropped, or mutilated by many MTAs and MUAs. Philip Guenther