On 08/13/2011 02:24 PM, Stefan Michael Guenther wrote:
Hi,
I have installed Djigzo on a OpenSUSE 11.1, together with an email archiving solution
called MPP.
MPP was connected to postifx with the following parameters:
main.cf:
----------
content_filter = mppscan:[127.0.0.1]:10025
master.cf:
--------------
localhost:10026 inet n - n - 10 smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o myhostname=xxx.xxx.de
-o smtpd_helo_restrictions=
-o smtpd_client_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o smtpd_data_restrictions=
-o smtpd_end_of_data_restrictions=
-o smtpd_authorized_xforward_hosts=127.0.0.0/8
mppscan unix - - n - 10 lmtp
-o lmtp_send_xforward_command=yes
-o lmtp_cache_connection=no
-o disable_mime_output_conversion=yes
To add Djigzo to the mailflow I changed the content filter ln main.cf to
content_filter = djigzo:127.0.0.1:10023
and added the following lines to master.cf:
djigzo unix - - n - 4 smtp
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o smtp_generic_maps=
I changed the port in /usr/local/djigzo/conf/james/SAR-INF/smtp_server_config.xml to
10023 and in /usr/local/djigzo/conf/james/SAR-INF/smtp_transport_config.xml the gateway
port to 10025 because MPP is waiting for incoming connections on that port.
For an incoming mail Postfix and Djigzo produce the following lines in their logfiles:
Aug 13 14:11:26 lxserver postfix/qmgr[26723]: 4E8679F029A:
from=<s.guenther(a)in-put.de>de>, size=9249, nrcpt=1 (queue active)
Aug 13 14:11:26 lxserver postfix/smtp[28125]: 4E8679F029A:
to=<s.guenther(a)xxxxx.de>de>, relay=127.0.0.1[127.0.0.1]:10023, delay=0.66,
delays=0.48/0.02/0.05/0.11, dsn=2.6.0, status=sent (250 2.6.0 Message received)
13 Aug 2011 14:11:26 | INFO incoming | MailID: 96e32cc0-102a-4b04-ac7e-e2abef86afe5;
Originator: s.guenther(a)in-put.de; Sender: s.guenther(a)in-put.de; Remote address: 127.0.0.1;
Recipients: [s.guenther(a)xxx.de]; Subject: test 11; Message-ID:
<4E4669F6.9070000(a)in-put.de>de>; (mitm.application.djigzo.james.mailets.Log) [Spool
Thread #2]
13 Aug 2011 14:11:26 | INFO internal | MailID: 96e32cc0-102a-4b04-ac7e-e2abef86afe5;
Originator: s.guenther(a)in-put.de; Sender: s.guenther(a)in-put.de;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #2]
13 Aug 2011 14:11:26 | INFO postDecrypt | MailID: 96e32cc0-102a-4b04-ac7e-e2abef86afe5;
Originator: s.guenther(a)in-put.de; Sender: s.guenther(a)in-put.de;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
13 Aug 2011 14:11:26 | INFO transport | MailID: 96e32cc0-102a-4b04-ac7e-e2abef86afe5;
Originator: s.guenther(a)in-put.de; Sender: s.guenther(a)in-put.de; Remote address: 127.0.0.1;
Recipients: [s.guenther(a)a-a-w.de]; Subject: test 11; Message-ID:
<4E4669F6.9070000(a)in-put.de>de>; (mitm.application.djigzo.james.mailets.Log) [Spool
Thread #3]
That's it, where is the email? There are no further lines in the logfiles of Postfix
or MPP. The email seem to be stucked somewehere in Djigzo, but where and why?
It seems you are mixing LMTP and SMTP (see posting by Andreas).
The email are probably still in the MPA outgoing queue (or in the MPA
error queue if there was a problem delivering the email). The MPA
outgoing queue is the queue of email which are being sent back from the
encryption engine. Normally they are sent to Postfix on localhost:10026
but with your changes they are being sent to localhost:10025. LMTP is
AFAIK not compatible with SMTP (minor differences but enough to not be
compatible I think). If MPP uses the LMTP protocol, try to change it to
use the SMTP protocol.
Kind regards,
Martijn Brinkers
--
Djigzo open source email encryption