On 04/03, Alex wrote: > How can I either use the existing system or emails stored on the > current system to test the new system before putting it into > production?
The best option may be to create a temporary DNS MX Record pointing to the new server, and just send mail to it. If normal mail gets flagged as spam, or mail with http://spamassassin.apache.org/gtube/ gets flagged as non-spam, the test has failed. Actually, you don't need an MX record. Just put the host name of the server after the @ in the email address. Or username@[IP_address] (with square brackets) might work. You could try forwarding some of your emails from the old system, but you won't be able to mimic them perfectly because you can't forge the sending IP. But you could copy a bunch of them over and run spamassassin on them after delivery, probably using formail. Without formail, if your mailboxes are in Maildir format, you can check a ham folder for false positives with: for file in `find /home/darxus/Maildir/{cur,new} -type f` ; do spamc < $file >> output ; done Then do "grep 'X-Spam-Status: Yes' output" to find false positives. -- My free public whitelist + blacklist needs your input: http://www.chaosreigns.com/iprep/
