| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
* first `+` splits local part from sub-address
* prioritize plus addressing over domain wildcards
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds compatibility for OpenSSL 1.1
Since renegotiation is removed from TLS 1.3 we also removed support for
authentication via client certificates (control/tlsclients). In general
this is still supported by TLS 1.3 however I'm just lazy and we don't
need this feature anyway.
This also adds optional support for OpenSSL configuration commands for
qmail-smtpd and qmail-remote. Commands are loaded from control/opensslconf.
For a list of supported commands see
https://www.openssl.org/docs/man1.0.2/ssl/SSL_CONF_cmd.html#SUPPORTED-CONFIGURATION-FILE-COMMANDS
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
qmail-remote assumes host is not null terminated. IDN requires null termination
so subtract the trailing NULL after appending.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This isn't entirely correct according to RFC 6531 as it's better to not
convert at all. However this would require we additionally add the UTF-8
form to qmails local recipient users/domains.
Plus our SMTPUTF8 implementation doesn't convert outgoing UTF-8 mails if
receiving MTA doesn't support SMTPUTF8. So mail forwarding might generate
a bounce the user very likely doesn't understand.
As MTAs who support SMTPUTF8 most likely also support the IDNA form,
always converting is probably a good trade-off.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
see google qmail-queue-custom-error-v2.patch
|
| | |
|
| |
|
|
|
| |
libval returns VAL_DANE_NOERROR if domain is insecure and no TLSA RR
exists. we should stop all further dane handling in this case
|
| | |
|
| | |
|
| |
|
|
| |
When the TLS handshake fails, retry delivery with TLS disabled
|
| | |
|
| |
|
|
| |
This adds support for DH parameters from 1024 to 8192 bits.
|
| |
|
|
|
|
|
|
| |
After an SMTP connection attempt times out, qmail-remote records
the relevant IP address. If the same address fails again (after
at least two minutes with no intervening successful connections),
qmail-remote assumes that further attempts will fail for at least
another hour.
|
| |
|
|
|
|
| |
...to work around a bug in BIND versions earlier than version 4.9.4
We don't use the code any more but it does no harm.
|
| |
|
|
|
|
|
|
| |
This patch increases the size of the memory buffer that qmail uses when
querying the system for a list of all local IP addresses. This mailing
list message describes the problem and includes the patch file.
see http://www.mail-archive.com/qmail@id.wustl.edu/msg20935.html
|
| |
|
|
|
|
|
|
| |
This patch changes qmail-remote to skip over MX servers that greet with
codes 400 to 499 and to bounce mail when any MX server that qmail tries
greets with a code 500 to 599.
see http://www-dt.e-technik.uni-dortmund.de/~ma/qmail/patch-qmail-1.03-rfc2821.diff
|
| |
|
|
|
|
|
|
| |
UltraDNS started blocking UDP-ANY queries so this is a problem.
This will disable domain canonicalization of the envelope address
of outgoing messages. This is as specified by RFC 1123 section 5.2.2.
However this requirement is obsolete and modern MTAs have disabled it
too.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
-t, -Ffullname, -i, -o<whatever>
additional support -f<> for null envelope mails
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch corrects a small programming error in
the blast() routine of qmail-smtpd.c. This is
sometimes referred to as the "Guninski" bug,
in reference to its discoverer.
see
* http://www.guninski.com/qmailcrash.html
* http://thedjbway.b0llix.net/qmail/patches/qmail-1.03.smtpd-blast.patch
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
check introduced by ee944357ee374402f20eb1297a0b596f7ef4ea8d
(qmail-smtpd-relay-reject.gentoo)
|
| | |
|