Daniel Black skrev, on 08-02-2008 13:19:
> On Fri, 8 Feb 2008 10:41:35 pm Tony Earnshaw wrote:
> 
>> I notice you cite my post; I stick to what I wrote: Postfix (2.5 in my
>> case) has no trouble with dkim-milter 2.4.3 and mailings to over 1000
>> LDAP posixGroup based recipients at a time. But Unix sockets have given
>> problems in the past, inet none.
> 
> I just assumed that unix vs inet problems were chroot related however i'm 
> willing to try the inet path (I was limited due to vserver firewall rules 
> when I don't control the host).
> 
>> And all my dkim-milter based stuff is 
>> called out of master.cg, not main.cf. dkim-milter is called by my last
>> smtpd listener before the message goes to cleanup.
> 
> Can you please provide the config you use?

master.cf; 10026 is the last of three smtpd listeners:

:10026       inet        n   -   n   -    50    smtpd
    -o content_filter=
    -o smtpd_client_restrictions=
    -o smtpd_helo_restrictions=
    -o smtpd_sender_restrictions=
    -o smtpd_error_sleep_time=0
    -o smtpd_recipient_restrictions=permit_mynetworks,reject
    -o receive_override_options=no_unknown_recipient_checks
    -o smtpd_milters=inet:localhost:10004
    -o disable_mime_output_conversion=yes
    -o milter_macro_daemon_name=ORIGINATING
    -o milter_default_action=accept

Default milter_protocol is 3 (6 as advised for PF 2.5 *does* give 
SMFIC_HEADER faults).

milter_macro_daemon_name corresponds to 'MTA ORIGINATING' in 
/etc/dkim-filter.conf - even though people have written that that's not 
necessary any more with current versions of dkim-milter.

Best,

--Tonni

-- 
Tony Earnshaw
Email: tonni at hetnet dot nl

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to