Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
allot of visitors just enter an invalid email in the WEB form just to download some files or do other tasks.
Does this surprise you? Perhaps you should consider a different system where the user has a choice of opting in after they have seen the content you have to offer. I even go as far as to keep a special email address that is just this side of /dev/null specifically for this purpose. Not surprisingly, it gets orders of magnitude more true SPAM for Viagra and other products to "make my dinger bigger" than my 'real' mailboxes. I am not saying that YOU are abusing their email address, but this practice IS abused SO MUCH that you are being treated as a criminal as a byproduct.
is it possible to BLACKLIST specific email addresses so the system does not send to those addresses? I can grep from the postfix mail log all those fake emails and place them somewhere
Yes, in fact I think that there is an easy an elegant solution for you. Postfix supports filtering on any of several parameters, including recipient and sender - email address or whole domains. To use it, you have to put the addresses in a list, which you can do with grep (or sed if you need more functionality) and then run postmap on the list to create a database hash table for postfix. You then add this hashed list to an entry in main.cf and postfix should discard the messages based upon this list.
I think that this is the section of the Postfix how-to documentation that best describes what you are after. The Postfix documentation is extensive, so you might want to browse around and experiment with the different restriction classes and capabilities.
There is nothing magical about the names and you can change them to whatever works for you. I have $config_directory set to /etc/postfix which is where I keep my mysql mapping files. Then in the map file you need the following:
user = <database user name>
password = <database user password>
dbname = <database name>
table = <the table>
select_field = as needed
where_field = as needed
What does your smtpd_recipient_restrictions block look like. You should certainly have more than that one line and the order of the checks is important. In your case it appears that a rule above this check is permitting the sending access. I would also look in your mail log to verify that the recipient address isn't getting mangled too.
smtpd_recipient_restrictions: The access restrictions that the Postfix SMTP server applies in the context of the RCPT TO command.
check_recipient_access: Search the specified access(5) database for the resolved RCPT TO address, domain, parent domains, or localpart@, and execute the corresponding action.
BtW, I have also used the report function to ask the moderators to trim these posts and place them in a thread of their own rather than appending to an older thread. This will allow your question to better get the attention it deserves.
Also found the problem. After making the changes, I tried testing with sendmail command. But the above settings will work only for RCPT method. So while trying to send email via telnet (telnet localhost 25; ehlo doamin... .. ) it worked fine. Thanks a lot for helping.