-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi tony,


>>i'm still unclear, tho, as to the driving rationale (performance?
>>security? politics?) one chooses one over the other ...
> 
> The Cyrus overview document mostly talks about security differences
> between them. (2) seems simpler from that point of view, though if you
> need to scale up to multiple hosts, you must use (1).

good. same idea i'm getting ...

>>      "The CMU folks recommend using LMTP over TCP or unix sockets - no
>>matter what MTA you use - on general principle, mostly for perfomance
>>reasons"
>>
>>is this still valid? recommended? w/ "today's" Exim?
> 
> 
> Yes, this is as opposed to using the "deliver" program, which is an LMTP
> client which the MTA talks to over a pipe. Obviously Exim has the
> necessary functionality built in.

fair nuf.  thx.


to _that_ end, and fwiw, i'm in the process of 'settling on':


        begin routers
        ...

        pre_cyrus_localuser:
            debug_print             = "EXIM-DEBUG [R:pre_cyrus_localuser] for 
[EMAIL PROTECTED]"
            driver                  = redirect
            hide_child_in_errmsg
            data                    = ${quote:[EMAIL PROTECTED]@${domain}
            redirect_router         = cyrus_localuser

        cyrus_localuser:
            debug_print             = "EXIM-DEBUG [R:cyrus_localuser] for 
[EMAIL PROTECTED]"
            driver = accept
        # local_part contains the domain here (format is <"[EMAIL 
PROTECTED]"@domain>)
            log_as_local            = true
            local_part_suffix       = +*
            local_part_suffix_optional
            retry_use_local_part
            domains                 = +local_domains
            cannot_route_message    = Unknown user
            transport               = cyrus_lmtp_unixsock

where these router choices are as suggested by:

        "Using Full Email Address for Cyrus LMTP Deliver"
        
http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050808/msg00041.html
        
http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050815/msg00063.html
and,


        begin transports
        ...
        cyrus_lmtp_unixsock:
            debug_print             = "EXIM-DEBUG [T:cyrus_lmtp_unixsock] for 
[EMAIL PROTECTED]"
            driver                  = lmtp
            socket                  = MY_PID_DIR/lmtp.socket
            user                    = MY_MAIL_USER


now, when *previously* using a 'pipe' trasnport to talk to the dovecot-lda, i'd 
used:

        #dovecot_lda:
        #    debug_print             = "EXIM-DEBUG [T:dovecot_lda] for [EMAIL 
PROTECTED]"
        #    driver                  = pipe
        #    command                 = 
MY_APP_DIR/dovecot/libexec/dovecot/deliver \
        #                              -c MY_CONF_DIR/dovecot-deliver.conf \
        #                              -d [EMAIL PROTECTED]
        #    message_prefix          = ""
        #    message_suffix          = ""
        #    delivery_date_add
        #    envelope_to_add
        #    return_path_add
        #    log_output
        #    user                    = MY_MAIL_USER


noting here the use of the several options ('message prefix', etc.), and 
reading that BOTH lmtp
is 'somewhat of a cross bet smtp & pipe' and 'there are only three options to 
the LMTP driver',

is it safe to assume that the LMTP 'driver' implcitly takes care of these, 
including the
delivery address, now? or must i deal with them in some other fashion/place?

cheers,

richard


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iEUEARECAAYFAkNFWEYACgkQGnqMy4gvZ6GNFACXVdXHBng039jzAVPAlnaELBsS
LgCfWL+Az8BicEzJhUNjlypQp+Qkx0Q=
=qaGW
-----END PGP SIGNATURE-----


-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users 
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Reply via email to