Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 281554 - Virtual Mailhosting guide: suggested syrus_sasl configuration produces unneccessary log entries
Summary: Virtual Mailhosting guide: suggested syrus_sasl configuration produces unnecc...
Status: RESOLVED WONTFIX
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Other documents (show other bugs)
Hardware: All Linux
: Low minor (vote)
Assignee: Docs Team
URL: http://www.gentoo.org/doc/en/virt-mai...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-15 08:35 UTC by Bernhard Kühnel
Modified: 2009-08-16 05:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Kühnel 2009-08-15 08:35:54 UTC
The problem and solution are also described in this forum thread I've found: http://forums.gentoo.org/viewtopic-t-502523.html

The USE flags mysql and ldap are selected by default from the ".../server" profile, therefore dev-libs/cyrus-sasl is usually emerged with them set.

With the suggested /etc/sasl2/smtpd.conf from the guide, the following entries are produced in /var/log/auth.log on incoming mail:

> Aug 10 07:39:37 x postfix/smtpd[9800]: sql_select option missing
> Aug 10 07:39:37 x postfix/smtpd[9800]: auxpropfunc error no mechanism > available
> Aug 10 07:39:37 x postfix/smtpd[9800]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: sql
> Aug 10 07:58:18 x postfix/smtpd[9839]: auxpropfunc error invalid parameter supplied
> Aug 10 07:58:18 x postfix/smtpd[9839]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: ldapdb


This is fixed for me by adding

sql_select: dummy
ldapdb_select: dummy

to /etc/sasl2/smtpd.conf. IMHO, either the guide or the default config file should be updated to reflect this.
Comment 1 nm (RETIRED) gentoo-dev 2009-08-16 05:11:37 UTC
We're not going to cover log entries in the guide, so you might want to see about either 1) fixing your USE flags at emerge time, or see if upstream's willing to change what they want logged by default.

You may also want to first file a bug about the logging issues and assigning it to the ebuild maintainers; you can find their info in the "metadata.xml" file in the /usr/portage/app-category/package/ directory.