7 posts / 0 new
Last post
#1 Mon, 09/10/2007 - 13:03
FilipeLacerda

SPAM problem

Hello,

We have a spam problem. Someone is sending SPAM from one of the accounts... and we cannot find out who.

So, is there anyway of implementing a spam filter to prevent spam to be send out of the server ???

thanks

Mon, 09/10/2007 - 13:05
FilipeLacerda

because, spam assassin is implemented and check for all websites, but i believe it only works out for incoming mails, and not outgoing...

Thanks

---
filipe

Mon, 09/10/2007 - 13:11 (Reply to #2)
Joe
Joe's picture

<div class='quote'>because, spam assassin is implemented and check for all websites, but i believe it only works out for incoming mails, and not outgoing...</div>

This is just the wrong way to go about solving this problem. You need to trace it to its source and get rid of the source.

--

Check out the forum guidelines!

Mon, 09/10/2007 - 13:11 (Reply to #3)
FilipeLacerda

hello!

Well, i'd love to find out who. But i cannot see the maillog.

where is that?

thanks

Mon, 09/10/2007 - 13:15 (Reply to #4)
Joe
Joe's picture

Depends on the OS. Red Hat based distros put it in /var/log/maillog and Debian-based distros put it in /var/log/mail.log. You can look at the log in Webmin:System:System Logs module, or from the command line.

--

Check out the forum guidelines!

Mon, 09/10/2007 - 13:28 (Reply to #5)
FilipeLacerda

Thank you very much.... I've found it :)

cheers

Mon, 09/10/2007 - 13:09
Joe
Joe's picture

<div class='quote'>We have a spam problem. Someone is sending SPAM from one of the accounts... and we cannot find out who.</div>

Find out who!

It's in the maillog. Every message sent through your server is logged. You can know which account sent the message and where it went just by looking in the log.

Then you can decide whether to close that account or bring legal action, if the offender is your customer, or if the offender broke into the account due to a weak password, you can reset the password to something stronger, and then keep an eye on system a little more closely in the future (and make sure your users have strong passwords!).

--

Check out the forum guidelines!

Topic locked