Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Someone has decided to relay LOTS of spam through our sendmail server. I know almost nothing about sendmail. I want to still allow our users to send mail through our server while in the field, but block this spammer. How should I go about this?
Facts:
-It is POSSIBLE, though not probable, that they hacked our web server at some point over the past few days, though the password has since been changed.
-They send through about half (10) of our employees' addresses, but only started a few days ago. Hence I doubt they guessed their passwords in that time.
-An example sendmail log entry of the spammer:
116797:Sep 2 16:47:17 www sendmail[29878]: n82KlF6E029878: from=<daniel@[OURCOMPANYNAME].com>, size=6462, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=189-73-143-176.dsl.pltce701.brasiltelecom.net.br [189.73.143.176] (may be forged)
Someone has decided to relay LOTS of spam through our sendmail server. I know almost nothing about sendmail. I want to still allow our users to send mail through our server while in the field, but block this spammer. How should I go about this?
Facts:
-It is POSSIBLE, though not probable, that they hacked our web server at some point over the past few days, though the password has since been changed.
-They send through about half (10) of our employees' addresses, but only started a few days ago. Hence I doubt they guessed their passwords in that time.
-An example sendmail log entry of the spammer:
116797:Sep 2 16:47:17 www sendmail[29878]: n82KlF6E029878: from=<daniel@[OURCOMPANYNAME].com>, size=6462, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=189-73-143-176.dsl.pltce701.brasiltelecom.net.br [189.73.143.176] (may be forged)
Ideas?
Hi zachlac if i was you change to firebird email, i have useing it for 10 months and not one spam
So I've forced SSL/TLS and disabled anonymous login, as well as enabled relaying. Ideally now someone should have to provide credentials to send through our relay. The problem now is that I don't know how to check to see if this fixed the problem. The log shows that the spammers are still trying, but I can't tell if the mail's getting through.
Also, we're having trouble allowing our employees to send mail from outside of our domain through our relay. They keep getting
550 5.7.1 <[SOMEEMAIL]@gmail.com>... Relaying denied. Proper authentication required.
We're using saslauthd, which is using PAM. Should I switch to shadow, passwd, or what? What's the advantage to PAM, and is there a major disadvantage to shadow?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.