>Publishing this info just to know how to deal with it. >I know, this isn't normal situation but I was a little surprised with behavior.
Which behavior of assp do you expect? ASSP not expects to get BATV-tagged mails from a local MTA - strictly not, if 'DoBATV' is enabled (this is nonsense!) - it will possibly work, if 'DoBATV' is disabled, but this was never tested. Solution - if BATV-tagging is wanted: - switch off all BATV-tagging on local MTA's (Exchange Edge (with ForeFront) - in your case) - configure the ASSP BATV options and enable 'DoBATV' (already done in your case) recommendation: Do not use BATV - used 'Do Message-ID Tagging and Validation (FBMTV) (DoMSGIDsig)' instead. Thomas Von: "Shabalin, Alexander" <[email protected]> An: "[email protected]" <[email protected]> Datum: 30.10.2018 15:07 Betreff: [Assp-test] Dual BATV sign with LDAP - user not found Hello! I've started a new installation of ASSP an found strange behavior. After I inserted ASSP to mailflow like this Exchange - Exchange Edge (with ForeFront) - ASSP - Relay - Internet. I've got two BATV sings (one from ForeFront and one from ASSP). And LDAP query for local user fails if it wasn't in ldaplistdb. 2018-10-30 13:50:25 m1-96625-11339 [Worker_2] 192.168.10.4 <[email protected]> info: BATV - changed sender from [email protected] to [email protected] 2018-10-30 13:50:26 [Worker_2] Info: LDAP - [email protected] not found in LDAP-cache (ldaplistdb) 2018-10-30 13:50:26 [Worker_2] Info: LDAP - [email protected] not found in LDAP-cache (ldaplistdb) 2018-10-30 13:50:26 [Worker_2] Info: LDAP Results (&(|(|(|(|(&(objectclass=user)(objectcategory=person))(objectcategory=group))(objectclass=publicfolder))(!(objectclass=contact)))(objectclass=msExchDynamicDistributionList))(proxyaddresses=smtp:[email protected])(!(msExchHideFromAddressLists=TRUE))): 0 : 2018-10-30 13:50:26 [Worker_2] Info: caching result for [email protected] in LDAPNotFound 2018-10-30 13:50:26 m1-96625-11339 [Worker_2] [RelayAttempt] 192.168.10.4 <[email protected]> to: [email protected] relay attempt blocked for: [email protected] - because RelayOnlyLocalSender is set to ON 2018-10-30 13:50:26 m1-96625-11339 [Worker_2] 192.168.10.4 <[email protected]> to: [email protected] [SMTP Error] 530 Relaying not allowed I know, this isn't normal situation but I was a little surprised with behavior. Publishing this info just to know how to deal with it. Best regards Alexander Shabalin _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! *******************************************************
_______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
