I think this is because mail is handed to sendmail when SMTPFILTER is set to TRUE so milters like spammassassin can be run. Once the milter is complete, sendmail queries LDAP to make sure the user exists before sending it back to Scalix. I think (from logs) that when sendmail checks for users that it is only looking for scalixPerson and ScalixDistributionList objectClasses and NOT scalixResource. As a result, anything sent to a resource gets bounced if SMTPFILTER is TRUE.
Here is the bit from the log that I'm basing this on (fc@gallowayfore.com is a scalixResource)...
Code: Select all
REPORT LDAP Daemon (LDAP Engine ) 08.29.07 00:50:27
[OM 16093] Performing DB get with following attributes:
KeyName: 168
KeyValue: FC@GALLOWAYFORE.COM
Filter: ( (1004=* & !1003=mail.gallowayfore.com ) | ( ( ( ( ( (1100=scalixPerson ) ) | ( (1=* ) & (422= ) & (620= ) ) ) & (433=* ) ) | ( ( (1100=scalixDistributionList ) ) | ( (1=* ) & (422=* ) ) ) | ( (1=+bb ) | (51=+bb ) ) ) & (168=fc@gallowayfore.com ) ) )
Anyone agree or disagree? How can I configure sendmail's LDAP query to include the scalixResource objectClass? If this is hard coded then I think it is a bug!
Thanks,
-Matt