--On Tuesday, October 12, 2004 23:41:34 +0200 Marc-Christian Petersen <[EMAIL PROTECTED]> wrote:

Hi all,

I am using Cyrus since ages, today I did an upgrade from 2.1.16 to 2.2.8
and I  am missing some example configuration files. Am I blind and they
are  somewhere in the source tree or are they simply not there?

I have some troubles with lmtpunix working correctly, or to be more
exact, to  shut up lmtpunix in my syslog. I get things like:

Oct 12 23:37:43 alice lmtpunix[23386]: executed
Oct 12 23:37:43 alice lmtpunix[23386]: sql_select option missing
Oct 12 23:37:43 alice lmtpunix[23386]: auxpropfunc error no mechanism
available
Oct 12 23:37:43 alice lmtpunix[23386]: _sasl_plugin_load failed on
sasl_auxprop_plug_init for plugin: sql
Oct 12 23:37:43 alice lmtpunix[23386]: accepted connection
Oct 12 23:37:43 alice lmtpunix[23386]: lmtp connection preauth'd as
postman Oct 12 23:37:43 alice lmtpunix[23386]: IOERROR: fstating sieve
script /opt/cyrus/var/spool/sieve/U/mcp/defaultbc: No such file or
directory Oct 12 23:37:43 alice lmtpunix[23386]: duplicate_check:
<[EMAIL PROTECTED]>                user.mcp             0
Oct 12 23:37:43 alice notify[7186]: accepted connection


Those errors weren't there with my 2.1.16 :) Anyway, mail is delivered, so the problem it seems are just those errors.

I hope someone can help me out here. Many thanks.

--
ciao, Marc
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Marc,

I had this problem, too, after I upgraded. I can't say exactly the best way to deal with the sieve script error, except to say that, if the 'mcp' account has an existing sieve script, it needs to be byte compiled into the new format. The man pages should have more information on that.

Regarding the sasl errors, specifically the sql error, just move the sasl mechanism .so object files in /usr/lib/sasl2 or /usr/local/lib/sasl2 that you are _not_ using to some other place (or delete them). SASL is attempting to load those libraries and use them in the chain of available authentication mechanisms. I created a sub-directory named /usr/lib/sasl2/not_used and put them all in there, so I would have them if needed in the future, but they wouldn't generate spurious log messages or be used when I did not want them to be used.

Hope this helps,
Will

--
----------------------------------------------------------------------------
William K. Hardeman
[EMAIL PROTECTED]
http://www.wkh.org

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Reply via email to