One thing to keep in mind is that the sysadmins can also change the way they block messages. The filtering is more than just an inconvenience. Transforming the subject might be too much work, *and the sysadmins could just change the way they filter subjects to match the changes.
> Subject: Re: empty subject now? > (I simply removed the subject in all response emails) > I guess I can keep the subject but remove the > Sory for the inconvenience. Changing the subject processing is probably a big deal. Writing the code that drops "http://", "ftp://", or other protocol indicators; drops "www", or "ftp"; drops the extension; changes each "." to " [dot] " isn't as easy as removing the subject. Changing something like "http://www.fq.dn/dir/fn.ext?stuff" into something like "fq [dot] dn [dot] /dir/fn [] stuff" would be convenient and useful. But, later, the filtering might be changed to match. Maybe just counting and numbering the response messages? Just adding "--001", "--002", and so on... Would it be easier to alter the inbound subject from "a multipart request" to something like "a multipart request --001" "a multipart request --002" ... "a multipart request --010" ... "a multipart request --042" and so on? --- [My Signature Here] --- ~~~~~~~~~~~~~~~ ACCMAIL Info (automatically generated) ~~~~~~~~~~~~~~ To UNSUBscribe: Send UNSUBSCRIBE ACCMAIL to [EMAIL PROTECTED] To get the ACCMAIL FAQ: Send e-mail to "[EMAIL PROTECTED]" and enter only this line in the BODY of the note: send usenet/news.answers/internet-services/access-via-email ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
