>> On 30.11.10 23:50, Sam Varshavchik wrote:
>>> By definition, port 587, and port 465, is to be used for
>>> authenticated SMTP only. So only clients that succesfully
>>> authenticate, using standard authenticated SMTP, have any beeswax
>>> connecting to these ports.
[...]
> Matus UHLAR - fantomas writes:
>> That's it - I defined ACCESSFILE in esmtpd, since I use it for port 25
>> clients. I want to have it empty for esmtpd-msa, but the ACCESSFILE isn't
>> defined there, but it is in esmtpd-msa config.
>>
>> The same applies for BLACKLISTS - I don't need blacklists for port 465 thus
>> I want to undefine them.
>>
>> Of course I can just put ACCESSFILE="" and BLACKLISTS="" at the end of
>> esmtpd-msa config but I wonder if I could do it more universally.
>>
>> I see that many of settings that are in esmtpd-msa can be used in esmtpd-ssl
>> thus I think sourcing esmtpd-msa config (in addition to esmtpd and
>> esmtpd-ssl) would make things easier.
>>
>> Otherwise, the sections where these variables are defined should be put into
>> esmtpd-msa.dist file.
On 01.12.10 06:52, Sam Varshavchik wrote:
> That's why the configuration files are, essentially, shell scripts. No
> one size fits all, everyone have their own requirements. Having them as
> shell scripts gives everyone the ability to do whatever they want.
>
> And given how sysconftool gets used to update the configuration files, as
> long as the magical comments don't get clobbered, you have a high degree
> of assurance that custom logic won't get nuked when upgrading; in the
> worst case you'll be able to fish it out from a .bak file.
Sam,
if you agree that both 465 and 587 are designed to do the same job, don't
you think they should have (nearly) the same config options in the default
config or source the same config file?
Note that there are no magical comments about ACCESSFILE and BLACKLISTS in
esmtpd-ssl and there's no ". ${sysconfdir}/esmtpd-msa" in esmtpd-ssl.
So, with current "default" configuration, esmtpd-ssl behaves much
differently than esmtpd-msa and it takes more work for admins to maintain
those configs.
Currently, the esmtpd-msa.dist looks more like ssl'ed alternative of esmtpd
(port 25) than MSA port with explicit SSL enabled. Do you want me to provide
patch(es) for .dist so it would look more like MSA with explicit SSL enabled
(for older version of M$ mail clients)?
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
- Have you got anything without Spam in it?
- Well, there's Spam egg sausage and Spam, that's not got much Spam in it.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
