Changelog for qmail-toaster-1.03.6-lp153.11.2.x86_64.rpm :

* Mon Jan 31 2022 Johannes Weberhofer - Reformatted spec- Removed gentestcrt.sh - creation of certificates is no longer tested- Applied qmailtoaster-openssl_1_1.patch. Thanks to the contributors- Unpacked all patches
* Fri Mar 29 2019 Johannes Weberhofer - Cleaned up spec file- Fixed license- Switch to older, compatible openssl version- Include insserv-compat for opensuse 15+
* Fri Apr 06 2018 jweberhoferAATTweberhofer.at- Enable + and # characters in addresses used by SRS: qmail-chkuser-enable-srs.patch
* Sat Feb 17 2018 jweberhoferAATTweberhofer.at- Removed DK patch
* Fri Dec 15 2017 jweberhoferAATTweberhofer.at- Removed mandrake support- Removed openSUSE < 11.4 support- Added patch qmail-dns-no-any-queries.diff to prevent all ANY DNS queries
* Thu Dec 04 2014 jweberhoferAATTweberhofer.at- Updated chkuser to 2.0.9
* New features - New variable for accepting only authorized senders: [#]define CHKUSER_EXTRA_MUSTAUTH_VARIABLE \"CHKUSER_MUSTAUTH\" if the variable exists, then messages are accepted only if RELAYCLIENT is set If defined, it works always despite CHKUSER being ON/OFF This feature can be used for a \"submission port\" (see RFC 2476) - Improved checking of MySQL server availability (if MySQL is used as vpopmail user\'s DB) - Introduction of a new variable for disabling chkuser on the fly: CHKUSER_DISABLE_VARIABLE (can be used for single IP or defined as \"RELAYCLIENT\" for all authorized e-mail clients) - Improved starting variables checking sequence CHKUSER_ALWAYS_ON and CHKUSER_STARTING_VARIABLE cannot be defined together and in such a case a fatal error is displayed; (in previous versions CHKUSER_ALWAYS_ON would automatically disable CHKUSER_STARTING_VARIABLE definition). CHKUSER_DISABLE_VARIABLE is always evaluated after CHKUSER_ALWAYS_ON is set or CHKUSER_STARTING_VARIABLE is evaluated, so CHKUSER_ALWAYS_ON or CHKUSER_STARTING_VARIABLE can set the general behaviour, while CHKUSER_DISABLE_VARIABLE should be invoked to handle exceptions. - New variable for accepting qmail doublebounces: CHKUSER_ENABLE_DOUBLEBOUNCE_VARIABLE Sender \"#AATT[]\" will be accepted. It is used by qmail for doublebounces, and should be enabled for selected IP senders. - define CHKUSER_ENABLE_VAUTH_OPEN has been substituted by CHKUSER_VAUTH_OPEN_CALL: this new define must contain the name of the call used to open the auth DB Updated features - checking for ezmlm mailing list is now done looking for file \"editor\" within mailing-list directory - defines for allowed character within sender and rcpt addresses increased up to CHKUSER_ALLOW_SENDER_CHAR_10 and CHKUSER_ALLOW_RCPT_CHAR_10 - updated SMTP error strings; more exact and detailed error codes (thanks to Olivier Dony and Dane Thorsen) - logging of valid rcpt. If CHKUSER_LOG_VALID_RCPT is defined then all valid recipients are logged, even if domain does not want bouncing or chkuser is disabled Bugs corrected - negative checking of backend DB connection did not report DB unavailability in some situations (thanks to Matt Brookings of Inter7) - in check_rcpt_address_format format checking was done using defines reserved for senders- allow more characters as defined in upstream qmailtoaster- unpacked several patches
* Wed Aug 20 2014 jweberhoferAATTweberhofer.at- Fixed a TLS bug
* Tue Sep 10 2013 jweberhoferAATTweberhofer.at- Removed pop3d support- Disabled CRAM-MD5 explicitly
* Wed May 29 2013 jweberhoferAATTweberhofer.at- Allow non fhs-compliant installation- Add groff as dependency to allow building on newer oss releases- Set non-position-independent-executable Badness to 0; Removing that again is on my to-do list
* Tue Jan 17 2012 jweberhoferAATTweberhofer.at- Created a new startup-script for suse vairants- Simplified and cleaned up spec file