------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=411
------- Comment #1 from exim-dev@??? 2006-11-14 12:49 -------
I strongly disagree.
There is an application name and a service name. Service name is used by SASL
so that things like GSSAPI can ensure that the right Kerberos service
credential is used (the first "smtp" in: smtp/smtp.spodhuis.org@???).
The application name is used for finding the optional config for SASL
initialisation. It is not the same as the service and should not be. Multiple
software products can implement a service and an administrator should be able
to configure them independently (either on different ports or trying them out
individually without having them stomp on each other).
If you have a need to change this then it needs to be a different Exim config.
Every piece of software I've seen has always hard-coded the appname, though.
It keeps things simple -- global SASL config for app "Foo" is in "Foo.conf" in
the sasl2 directory.
It would be good to know what problem you're trying to solve, that this is
necessary.
It might be that the correct resolution for this is to have the Spec explicitly
mention in section 36 that the application name is set to "exim" -- it probably
should be noted, so that people don't have to try "exim.conf", "Exim.conf" or
other combinations or check the source to see which capitalisation is needed.
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
