* Quanah Gibson-Mount <[email protected]>:
> I think the problem is, the only place it exists is in the release notes...
>
> quanah@zre-ldap001:~/p4/main/ThirdParty/amavisd/amavisd-new-2.7.0-pre14$
> find . -name "*" | xargs grep -i sa_user_config_file
> ./RELEASE_NOTES:- added a configuration variable $sa_user_config_file, also
> member of ./RELEASE_NOTES: configuration file. Setting of
> $sa_user_config_file is normally done ./RELEASE_NOTES: when switching
> users. When $sa_user_config_file changes (through exiting
>
> I.e., it doesn't seem to actually exist anywhere in the source.
Seems like the config var in RELEASE_NOTES is wrong:
p@x300:~/amavisd-new-2.7.0-pre10-patch$ grep sa_user *
amavisd: @sa_userconf_maps @sa_username_maps
amavisd: @sa_userconf_maps @sa_username_maps
amavisd: unshift(@Amavis::Conf::sa_userconf_maps,
$lf->('amavisSaUserConf', 'S-'));
amavisd: unshift(@Amavis::Conf::sa_username_maps,
$lf->('amavisSaUserName', 'S-'));
amavisd: unshift(@Amavis::Conf::sa_userconf_maps,
$nf->('sa_userconf', 'S-'));
amavisd: unshift(@Amavis::Conf::sa_username_maps,
$nf->('sa_username', 'S-'));
amavisd: my($uconf_maps_ref) = ca('sa_userconf_maps');
amavisd: my($uname_maps_ref) = ca('sa_username_maps');
amavisd.conf-default:# @sa_userconf_maps = ();
amavisd.conf-default:# @sa_username_maps = ();
amavisd.conf-default: ## @sa_userconf_maps @sa_username_maps
amavisd.patch: @sa_userconf_maps @sa_username_maps
amavisd.patch: @sa_userconf_maps @sa_username_maps
amavisd.patch: unshift(@Amavis::Conf::sa_userconf_maps,
$lf->('amavisSaUserConf', 'S-'));
amavisd.patch: unshift(@Amavis::Conf::sa_username_maps,
$lf->('amavisSaUserName', 'S-'));
amavisd.patch: unshift(@Amavis::Conf::sa_userconf_maps,
$nf->('sa_userconf', 'S-'));
amavisd.patch: unshift(@Amavis::Conf::sa_username_maps,
$nf->('sa_username', 'S-'));
amavisd.patch: my($uconf_maps_ref) = ca('sa_userconf_maps');
amavisd.patch: my($uname_maps_ref) = ca('sa_username_maps');
RELEASE_NOTES: are supported (@sa_userconf_maps), and per-recipient SQL Bayes
database
RELEASE_NOTES: usernames (@sa_username_maps);
RELEASE_NOTES:- added a configuration variable $sa_user_config_file, also
member of
RELEASE_NOTES: configuration file. Setting of $sa_user_config_file is normally
done
RELEASE_NOTES: when switching users. When $sa_user_config_file changes
(through exiting
RELEASE_NOTES: are supported (setting @sa_userconf_maps). A multi-recipient
message
RELEASE_NOTES: usernames are supported (setting @sa_username_maps). This
makes it
p@rick
--
All technical questions asked privately will be automatically answered on the
list and archived for public access unless privacy is explicitely required and
justified.
saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
Please visit http://www.ijs.si/software/amavisd/ regularly
For administrativa requests please send email to rainer at openantivirus dot
org
