Page MenuHomekolab.org

Unable to send mail after upgrade from 3.4 to 16 - SMTP access policy issue?
Closed, ResolvedPublic

Description

After upgrading from Kolab 3.4 to Kolab 16 according to the upgrade notes, it was no longer possible to send any mail. I'm now running pykolab-0.8.3-3.1.el7.kolab_16.noarch.

The following was seen on Postfix logs:

Aug  8 19:21:07 posti postfix/submission/smtpd[13011]: C4B9D40934C6: client=localhost[::1], sasl_method=LOGIN, sasl_username=username@domain.tld
Aug  8 19:21:07 posti postfix/submission/smtpd[13011]: C4B9D40934C6: reject: DATA from localhost[::1]: 554 5.7.1 <DATA>: Data command rejected: Sender access denied; from=<username@domain.tld> to=<externaluser@otherdomain.tld> proto=ESMTP helo=<server.domain.tld>

I was able to work around the issue by replacing the /usr/libexec/postfix/kolab_smtp_access_policy file from an earlier version, but I don't think this is a preferred solution :) (both versions attached, ...34 works, ...16 doesn't).

In addition, the following is logged in pykolab.log periodically, no idea if it has anything to do with this issue:

2016-08-09 14:04:14,678 pykolab.auth ERROR An error occured using _persistent_search: TIMEOUT()
2016-08-09 14:04:14,680 pykolab.auth ERROR Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 3059, in _search
    secondary_domains
  File "<string>", line 10, in <module>
  File "/usr/lib/python2.7/site-packages/pykolab/auth/ldap/__init__.py", line 2738, in _persistent_search
    resp_ctrl_classes={ecnc.controlType:ecnc}
  File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 476, in result4
    ldap_result = self._ldap_call(self._l.result4,msgid,all,timeout,add_ctrls,add_intermediates,add_extop)
  File "/usr/lib64/python2.7/site-packages/ldap/ldapobject.py", line 99, in _ldap_call
    result = func(*args,**kwargs)
TIMEOUT

Event Timeline

teemup created this task.Aug 9 2016, 1:15 PM

Could you try if dropping policy_result table in kolab database fixes the issue. The table will be re-created automatically.

I restored the non-working kolab_smtp_access_policy, confirmed that the issue returned, dropped the policy_result table, et voilà! The issue is fixed. Thanks a lot for the quick help!

Perhaps this should be automated somehow, it would seem that I'm not the only one experiencing the issue.

thozie added a subscriber: thozie.Aug 10 2016, 7:52 PM

I'm getting the same error message with current Winterfell, but it does not stop on dropping the table. On the other Hand I have no mail submit issues.
Dirsrv logs this errors:
[10/Aug/2016:19:39:09 +0200] connection - conn=3666 fd=64 Attempt to release connection that is not acquired
[10/Aug/2016:19:42:43 +0200] connection - conn=3682 fd=65 Attempt to release connection that is not acquired
[10/Aug/2016:19:44:09 +0200] connection - conn=0 fd=0 Attempt to release connection that is not acquired
[

Rick_L added a subscriber: Rick_L.Aug 14 2016, 11:51 AM

Could you try if dropping policy_result table in kolab database fixes the issue. The table will be re-created automatically.

This temporary fix worked for me.
Thanks!

Had the same issue, workaround worked.

This should be documented here, shouldn't it?
https://docs.kolab.org/upgrade-guide/kolab-16.html

vanmeeuwen closed this task as Resolved.Dec 2 2016, 3:33 PM
vanmeeuwen claimed this task.
tku added a subscriber: tku.May 7 2017, 12:54 PM

I am getting this issue on vanilla Kolab 16 installation but after dropping the policy_result table it gets recreated.

Do I also need to use the Kolab 3.4 kolab_smtp_policy?

Konrad added a subscriber: Konrad.Dec 10 2018, 1:26 AM

This should be documented here, shouldn't it?
https://docs.kolab.org/upgrade-guide/kolab-16.html

Also necessary when upgrading from KOLAB 14 to KOLAB 16 ...