Am 19.12.2015 um 16:52 schrieb [email protected]:
On Dec 19, 2015, at 04.35, Reindl Harald <[email protected]> wrote: Am 19.12.2015 um 04:08 schrieb [email protected]:On Dec 17, 2015, at 13.16, Alfredo Saldanha <[email protected]> wrote:My second SA is a Zimbra server. I use Zimbra SA only to drop the message in junk folder. I don't want to clean at the Zimbra server, it is default behavior.for what it's worth, if you were to use amavis rather than a milter, you could just deliver mail directly from amavis to the zimbra mailbox server [bypassing the zimbra mta which you don't need in term of this] via lmtp [typically port 7025]how does a transport "lmtp:[host]:7025" depend on "use amavis rather than a milter"you're making assumptions. no one said it did. zimbra's mailbox server depends upon use of amavis for "it just works" integration.
what assumptions do i make?the goal would be to skip the complete amavis scanning on the zimbra host because that's what the inbound MX does and should do
you skip that implicit by deliver via LTMP and it don't matter what is used for scanning on the first machine or if it don't bypass the scan on the zimbra machine it's pointless
milter rejects high scored spam and the rest takes the configured transport which exists anyways and points now to the zimbra mtacorrect, that is how a milter works, be it irrelevant to the point
no - because the point is that the zimbra server runs on a different machine after the MX and hence has no business with the scan itself
signature.asc
Description: OpenPGP digital signature
