Script toolshed for Postfix

policyd-weight.org by Robert Felber
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.
pfqgrep.pl by Rob Chanter
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.
check-null-mail-host-new.pl by Philip Kizer, additions and rewrite by Ralf Hildebrandt
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.
delete-from-mailq by ?
This deletes all mail from the mailq which matches the regular expression specified as the first argument.
mailqfmt.pl 0.6 2004/01/20 by Matthias Andree
Postfix mailq file reformatter, concatenates a mailq entry into one single line.
rebuild_postfix by Ralf Hildebrandt
A script I use to rebuild Postfix.
spamrep_today by Roger Marquis
check out the license terms.
spamrep_today_byuser by Roble
check out the license terms.
qSummary.pl by Andre Galvani <agalvani@zip.net>
It prints the amount of messages per domain in the queue.
find_in_log by Ralf Hildebrandt
It requires postfix.transform.log by Rahul Dhesi.
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 17. Nov 2010 by root