Matus UHLAR - fantomas writes:
Hello,We are providing our users SMTP submission service at port 587 via esmtpd-msa and on port 465 via esmtpd-ssl. However, neither the esmtpd-ssl script, nor config file are configured to provide this kind of service - the esmtpd-ssl script sources esmtpd and esmtpd-ssl configs, but there's no option for BLACKLISTS and ACCESSFILE that are e.g. redefined in esmtpd-msa config.
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.
As such, no action is necessary. Once they authenticate, they have relaying privileges, no ACCESSFILE is required for that.
pgp01aH3r4Rrn.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
