* This is the vopmailbeta mailing list *
> Now I can't find who did it. Their logs are dated July > and I don't keep logs that long and I don't have logging > turned on. Well, that would be the first step, wouldn't it? No offense, but logging transactions and archiving those logs is really a fundamental aspect of administering a mail server. > How to I deal with this? I want to block this kind of > behaviour from the source. Let me see if I get this right... A customer sent spam through your service. The destination ISP realized it sometime later, and provided you with the information to track the offending individual down. However, you do not have the proper information being logged or do not maintain logs back that far. Your response, then, is to inconvenience a undetermined amount of your customers by preventing them from using this one specific feature of e-mail which was abused by a single customer. Furthermore, you'd rather do this than keep detailed, accurate logs and zip them up once a month? The latter would ensure that no matter how anyone attempts to abuse your server in the future, you are able to track them down. Am I missing something? Don't get me wrong, I think your feature request has potential for other reasons, such as enforcing a corporate standard. I just suspect that your going about solving this one specific problem in a Columbus kind of a way. Benjamin S. Rogers http://www.c4.net/ v.508.240.0051 f.508.240.0057 ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
