Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Ive set up header check to bounce back anything going to a certain person, say
/^to: aaa@aaa.com$/ REJECT (aaa.com being a valid virtual domain)
I then mapped this email to my user name to see if it is still receiving any emails. When I try to send from yahoo to aaa.aaa.com, it gets rejected (yay!)
Yet Im still getting spams to this address. How are they getting in? To make matters worse, I'm also getting aaa@bbb.com where bbb.com isnt even on my domains list
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
The RFC821 and RFC822 headers don't have to agree. What you're filtering on is the RFC822 (message header) but in order to get the message to you, only the message envelope needs to point to your address.
I think Postfix has support for user maps. You could always point that user to /dev/null.
thanks however, this rule should apply not just for existing users right?
Im actually using this header check to make my catchall account easier to browse through for valid emails that may have been sent to the wrong email address say aaa1@aaa.com. Our clients just love us for catching these types of good emails.
Therefore I cant just point a user to a null destination
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Ahh, so you're directing the "left overs" that don't go to an actual user into a catchall account? Right, you do not want to /dev/null your catchall. However, you should be able to setup a usermap and "create" the invalid user, and direct just that user to /dev/null. *DISCLAIMER I haven't done this with Postfix so it's all a theory, but it's a theory based on about 7 years of e-mail administration.
but that would mean having to make a bunch of non real users just to throw away the bad mail, this isnt so bad but we may be talking about tens to hundreds of bogus users
It would be really nice to have the to: caught by the above syntax or any other means
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
You can do that only if the filter hooks into the MTA to read the RCPT TO: rather than just scanning the To: on the message header. The SEIVE filter in Qmail will let you do the former. There must be something similar in Postfix, but like I said, I'm not familiar with it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.