I have attached an updated config.xml and james-smtphandlerchain.xml file.
The config.xml file contains an additional RemoteDelivery mailet
(transport-internal processor). The 'transport-internal' processor is
now used instead of 'transport' for internal email. Both transports (for
internal and external) send the email back to Postfix to the same port
(port 10026). You must change the port of the 'transport-internal' to
the port you want internal email to be sent (thus the port your virus
scanner locally listens on). Or if you want Postfix to do the queuing
for you you must add an additional re-injection port to
/etc/postfix/master.cf and tell Postfix to send the email to the virus
I have also added a line to james-smtphandlerchain.xml to make sure that
the new spool directory is monitored. James-smtphandlerchain contains a
ThrottlingMailHandler that monitors the queues and if the queues grow
beyond a certain limit it throttles incoming connections. This was added
to make sure that if incoming email cannot be handled fast enough
Postfix queues the mail instead of the internal MPA.
The updated config.xml should be copied to
/usr/share/djigzo/conf/james/SAR-INF and james-smtphandlerchain.xml
should be copied to /usr/share/djigzo/conf/james/conf (overwrite the
I hope my explanation is clear enough
Zitat von Martijn Brinkers
This is possibe by adding an additional RemoteDelivery mailet.
Currently one RemoteDelivery mailet is used for sending email back
to postfix. The catch is that the additional queue cannot be
monitored using the Web interface (the MPA outgoing queue).
If you are interested in the solution I can send you a modified and
commented config.xml (this is where you must add the additional
Not monitoring the second MPA queue would be okay for starting.
Would be glad to get it working with the two output channels. Is the
only thing to do the changed config.xml or are there additional
changes to do?
Users mailing list
Djigzo open source email encryption