A small go project that will hopefully grow into a mailq management tool for postfix
Go to file
Jan Philipp Timme 3402b2e71c Use debian buster in Vagrantfile 2019-11-03 15:41:38 +01:00
mailq Properly use methods to build up MailQ struct 2019-01-06 19:07:10 +01:00
vagrant-util Use example.local since example.com has nullMX in place 2019-11-03 15:41:02 +01:00
.gitignore Prepare skeleton to build a very basic test environment 2019-01-26 11:38:32 +01:00
README.md Add a basic README.md, fix missing entry in /etc/hosts in Vagrantfile 2019-01-27 10:45:45 +01:00
Vagrantfile Use debian buster in Vagrantfile 2019-11-03 15:41:38 +01:00
main.go Rename QEntrySortConfig to QSortConfig 2019-01-01 21:23:04 +01:00
shell.go Rename QEntrySortConfig to QSortConfig 2019-01-01 21:23:04 +01:00

README.md

mailq-inspector

State of this tool: Still in development, nothing is really stable at this point

The goal of mailq-inspector is to provide an easy way to inspect and handle mails that are stuck in your postfix mailq. It is written in go, so all you need to do to build it is run go build.

How to use

At this point, i still need to write a lot of code (and documentation). Just invoke mailq-inspector and maybe pass --help to it to get a rough idea of available options.

Testing

In order to provide an environment that can be used to test this tool without sacrificing an actual production mailserver, a Vagrantfile is included. Invoke vagrant up to build the box. Invoke vagrant rsync-auto if you want /vagrant to stay in sync with the environment on your local machine.

Finally, invoke vagrant ssh to ssh into the vagrant box.

To test mailq-inspector, change into /vagrant and run it:

cd /vagrant
./mailq-inspector