Try this tutorial:
http://www.iredmail.org/wiki/index.php? … IP.address

(Note: i will convert above mediawiki document to Markdown format soon.)

A simple solution is, APPEND one more lookup table (either hash or sql, whatever you want/prefer) in Postfix parameter 'virtual_alias_maps', to query this global catchall setting. For example:

virtual_alias_maps = ..., hash:/etc/postfix/global_catchall

File /etc/postfix/global_catchall:

* catchall@domain.com

Then:

# postmap hash:/etc/postfix/global_catchall

You know that a global catchall like above will accept ALL emails (including spams) sent to non-existing mail addresses, right? you're warned.

Also, any reason for running Amavis on an Inet Port, instead of a Unix Socket? Surely the Unix Socket would be more efficient for this?

Reference: http://www200.pair.com/mecham/spam/bypassing.html

With a inet port, you don't need to care about file location of socket file, and you can even run Amavisd on another server.

Yes. You can define transports in /etc/postfix/master.cf first, then you can set one of them with iRedAdmin-Pro (in domain profile page).

Currently we have only transport for receiving defined in transport_maps, but Postfix will query transports for both send/receive emails defined in transport_maps.

Oh, sorry, my mistake.

*) To use a transport for SENDING email, you have to define it in Postfix parameter 'sender_dependent_default_transport_maps'. This is NOT manageable with the latest iRedAdmin-Pro release.

*) To use a transport for DELIVERING received email to local mailbox, you have to define it in Postfix parameter 'transport_maps'. This is manageable with iRedAdmin-Pro.

It'll need a few tweaks but most of the content from the original MediaWiki file is there, along with instructions on the use of hash: instead of pcre: (see attachment)

I've used pcre:

/.*/ postmaster@example.com

instead but if there is a hash way of doing it then please let me know

Document committed: http://www.iredmail.org/docs/send.out.e … esses.html

Note: i removed some code related to 'hash' table to make document clearer (let reader thinks less and finish required steps.)