Home | Comics | wishlist | Impressum | Datenschutzerklärung | 126.96.36.199
A perl script for the postfix MTA (2.1 and later) to eliminate most forged envelope sender and HELOs (i.e. Bogus Mails). Allows you to score DNSBLs, HELO, MAIL FROM, Client IP Addresses before any queuing is done. Allows you to REJECT messages which have a score higher than allowed.
Take the output of Postfix-style mailq, and print to stdout only the messages matching a pattern. Can find patterns in sender, recipient, deferral reason text, or by status.
You can find a slightly improved version here: pfqgrep.pl with logical AND, courtesy of Joan Juvanteny
New version! (30.07.2008)
This script checks all MX/A hosts for a given domain. It checks if MAIL FROM: <> to postmaster@domain (configurable!) is being accepted. Furthermore, the domain and all it's MXes are checked against various blacklists.
New version: Various errors fixed, use new blacklists, etc.
This deletes all mail from the mailq which matches the regular expression specified as the first argument.
Postfix mailq file reformatter, concatenates a mailq entry into one single line.
A script I use to rebuild Postfix.
check out the license terms.
check out the license terms.
It prints the amount of messages per domain in the queue.
It requires postfix.transform.log by
It first analyses the log to find matching logentries by message-id (thanks to Rahul!). Then these matching entries are grepped for the emailaddress, which needs to specifies as argument to find_in_log.
Doug writes here: "One problem I have is that when I want to see all the log messages for a given email message, there's no single identifier I can grep on. Because of the way I have messages received by smtpd, passed to amavis, then spooled back into smptd I end up with two different Postfix IDs for each messages. Plus, the amavis lines don't include the Postfix ID.
I wrote grep4msg.pl as an answer to this problem. It's a little brute force, but I don't think it will get run very often to cause processor consumption problems. Basically, it parses through all of the mail.log lines and groups them by both their Postfix message ID and the email's Message-ID taking care to relate the two together. Then after all the log file's lines are sorted by these two criteria it groups all the lines with only a message-id with the appropriate Posfix ID lines. It then groups multiple sets of Postfix ID lines if they share the same message-id. Meanwhile it does all this while preserving the order the lines were found in the mail.log. Pretty nifty if I may say so myself."
© by Ralf Hildebrandt
This document contains links to external information sources that I do neither monitor nor control. I explicitly disclaim any liabilities in respect to external references.
You are getting this document without any guarantees. Any methods shown above are meant as demonstration and may be wrong in some place. You may damage your system if you try to follow my hints and instructions. You do this at your own risk!
This file was last modified 31. May 2013 by root