Here's the issue. It would be nice if the user preference signatureLocation had one more option. The current choices are:
headers - which puts it in the header only, great for imap users message - which puts it in header AND the body I would like for it to go ONLY into the body. The logic is this... It makes it a lot easier to support pop3 and imap users. On many systems, people use a procmail, sieve, whatever script to check the header and if the result is Spam, move to a SPAM folder. This allows use with tools like the dovecot antispam, etc. However, if a user needs to use pop3 instead of imap, now there is a problem since it will still move it to the spam folder, which some email clients cannot get to. The user would correctly change their signatureLocation to something that would ONLY put the signature in the body (not the header), and, therefore, the standard scripts would never move the message to the spam folder. So many systems are configured this way, but, then one has to find a way to code around pop users. If the location was not in the header, nothing to do. Steve ------------------------------------------------------------------------------ Malware Security Report: Protecting Your Business, Customers, and the Bottom Line. Protect your business and customers by understanding the threat from malware and how it can impact your online business. http://www.accelacomm.com/jaw/sfnl/114/51427462/ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
