Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
there's not a huge amount you can do, but one thing I'd suggest is using fail2ban to trawl the logs and block specific client IP's doing this, there is a bit of replication of IP's in there from what I can see, so that's a start.
Use of Address Verification, while being an effective tool against SPAM, is not without issues. If you haven't already have a look at the Postfix documentation on the subject: http://www.postfix.org/ADDRESS_VERIFICATION_README.html There is little you can do to stop the attempts to probe your system as a potential open relay except use tools like fail2ban or the BSD version of spamd, but if you are experiencing performance issues because of this check you may want to try alternative tactics. For example, my list of checks is contained below (which is a little bit DNS heavy because of the fact that I have the RBL checks early on). The important point is that the order of your checks can also have an impact on performance and it may be possible to reject spam with a light weight check before running heavier one.
Note that I am using reject_unauth_destination (which stops open relaying). I am also using reject_unknown_recipient_domain, which is a form of address verification, but it is checked after verification that it is an authorized destination. In the sender restrictions, I am using things like reject_non_fqdn_sender and reject_unknown_sender_domain, which send a 550 level reject code in response to crap generated from worms like Conficker.
# reject_rbl_client dnsbl.sorbs.net -- this catches more spam, but also creates quite a few false positives
Basically, an inbound message claiming to be from "firstname.lastname@example.org" will result in the Postfix SMTP deamon attempting to verify that sender address by connecting to the MX responsible for the domain and running an SMTP session up to RCPT TO - where it will typically quit.
Disable that feature (which I personally would not use) and your problem should go.
Relay attempts manifest themselves in the logs with this: "Relay access denied" and this will give you handle on if you have a problem with that:
zgrep -e "Relay access denied" /var/log/mail* (or the location of your mail log)
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
You definitely need to modify your configurations and add fail2ban or spamd but it would also be possible (since it seems like these are all coming from the same repeated ip addresses) that you could block this at a firewall level as well and that may help free up some of your bandwidth as well. I would certainly consider that as well.