[Kolab-devel] Kolab 3.0beta: Problems with kolab_smtp_access_policy

ITSEF Admin itsef-admin at brightsight.com
Mon Dec 3 18:51:21 CET 2012


Hi *!

After figuring out that there is a wrong path to kolab_smtp_access_policy 
in /etc/postfix/master.cf (https://issues.kolab.org/show_bug.cgi?id=1423 - 
saw too late that there was an update already, so that report may be 
obsolete), I still keep having errors with kolab_smtp_access_policy:

From mail.log:
Dec  3 18:37:50 SERVER postfix/spawn[3404]: warning: 
command /usr/lib/postfix/kolab_smtp_access_policy exit status 1
Dec  3 18:37:50 SERVER postfix/smtpd[3400]: warning: premature end-of-input on 
private/sender_policy_incoming while reading input attribute name
Dec  3 18:37:50 SERVER postfix/smtpd[3400]: warning: problem talking to server 
private/sender_policy_incoming: Connection reset by peer
Dec  3 18:37:50 SERVER postfix/smtpd[3400]: NOQUEUE: reject: RCPT from 
CLIENT[192.168.123.45]: 451 4.3.5 Server configuration problem; 
from=<USER at DOMAIN.1> to=<testuser at SERVER> proto=ESMTP helo=<CLIENT>
D

When I run kolab_smtp_access_policy manually, I get:

# /usr/lib/postfix/kolab_smtp_access_policy 
Traceback (most recent call last):
  File "/usr/lib/postfix/kolab_smtp_access_policy", line 1374, in <module>
    cache = cache_init()
  File "/usr/lib/postfix/kolab_smtp_access_policy", line 1093, in cache_init
    engine = create_engine(cache_uri, echo=False)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/__init__.py", line 
338, in create_engine
    return strategy.create(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py", 
line 64, in create
    dbapi = dialect_cls.dbapi(**dbapi_args)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/connectors/mysqldb.py", 
line 52, in dbapi
    return __import__('MySQLdb')
ImportError: No module named MySQLdb

Any idea what could have gone wrong here?

Fresh install on Debian Wheezy/Kolab 3.0beta with latest updates.

Cheerio,

Thomas
-- 
------------------------------------------------------------------------------
           Thomas Ribbrock, IT-Team brightsight




More information about the devel mailing list