MeTA1 1.1.Alpha9.0

MeTA1 Source Code

The source code distribution and the PGP signature are available at:

http://www.MeTA1.org/download/.alpha/smtps/meta1-1.1.Alpha9.0.tar.gz
http://www.MeTA1.org/download/.alpha/smtps/meta1-1.1.Alpha9.0.tar.gz.sig

checksums:

SHA256 (meta1-1.1.Alpha9.0.tar.gz) = a52d2a0974d5835334d6dbb41a018234cfbe8ecdf5c5350d76ab41296a82c529
SHA256 (meta1-1.1.Alpha9.0.tar.gz.sig) = dec935cbc18c204ec5db3ad493ee1c35c34d5cafeea36e89ab1819c730e33a7d

Changes compared to MeTA1 1.1.Alpha8.0

• 2018-02-14 New smtps flag: "smtps": to enable "smtps" submission service, i.e., implicit TLS handshake, as described in RFC 8314.
• 2018-01-04 If MTA_NO_DNS_TEST is not set to false then most tests which perform DNS lookups are disabled; previously setting it to any value would disable DNS tests, now those tests are disabled by default as DNS lookups are not reliable enough and may cause misleading test failures.
• 2018-01-01 If createmap(8) finds a duplicate key it will report the key too.
• 2017-11-03 New DKIM option over_sign_headers specifies a list of header names which will be over-signed by DKIM, i.e., each specified header name will be listed in the header list (h=) one more time than it is specified in the header of the mail itself, thus preventing an attacker to add another header of the same name (without breaking the DKIM signature).
• 2017-09-21 Provide more information in a DSN about the encountered problem if connect(2) failed or tls_requirements were not met in smtpc.
• 2017-04-16 In tls_requirements the keyword requirements_violation has been shortened to violation, i.e. the extra "requirements" has been dropped; the former keyword is deprecated but still allowed.

MeTA1 Feedback

< MeTA1 + feedback (at) MeTA1 . org >