Hi, > There is no mechanism reporting back to the spam sender > that "hey, I know you are spam, and I am not sending this email". > Consequently, the spammer thinks you are an open relay and ends up > filling your spam folder with 10s of thousands of files. Eventually, James > (and Windows) gags on this folder.
You should change the spam processor to delete recieved spam. > Also, if your users go to another machine and setup a new mail client, > when they send a new email there is no report back to them that > because of their new ip address, the email was rejected. You should use remote address not in sender to run a bounce mailet, such as "redirect", to return their message with a message, like "You are not authorised to send mail on this server, contact [EMAIL PROTECTED] if you believe this is a mistake" >This is > probably IMHO the most serious of issues in a corporate environment - > users need to _trust_ that no news is good news. ie if no error > is reported back to you, then the email was successful. There is *nothing* that precludes you from configuring current versions of James to bounce any mail which isn't sent successfully. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
