Mechiel Lukkien 5c33640aea consistently use log.Check for logging errors that "should not happen", don't influence application flow ... sooner or later, someone will notice one of these messages, which will lead us to a bug.		2023-02-16 13:22:00 +01:00
..
alignment.go	mox!	2023-01-30 14:27:06 +01:00
analyze.go	consistently use log.Check for logging errors that "should not happen", don't influence application flow	2023-02-16 13:22:00 +01:00
authresults.go	mox!	2023-01-30 14:27:06 +01:00
authresults_test.go	mox!	2023-01-30 14:27:06 +01:00
dnsbl.go	mox!	2023-01-30 14:27:06 +01:00
dsn.go	consistently use log.Check for logging errors that "should not happen", don't influence application flow	2023-02-16 13:22:00 +01:00
error.go	mox!	2023-01-30 14:27:06 +01:00
fuzz_test.go	mox!	2023-01-30 14:27:06 +01:00
limitwriter.go	mox!	2023-01-30 14:27:06 +01:00
mx.go	mox!	2023-01-30 14:27:06 +01:00
parse.go	add scram-sha-256 for smtp	2023-01-31 00:22:26 +01:00
parse_test.go	mox!	2023-01-30 14:27:06 +01:00
rejects.go	mox!	2023-01-30 14:27:06 +01:00
reputation.go	improve training of junk filter	2023-02-11 23:00:12 +01:00
reputation_test.go	improve training of junk filter	2023-02-11 23:00:12 +01:00
server.go	consistently use log.Check for logging errors that "should not happen", don't influence application flow	2023-02-16 13:22:00 +01:00
server_test.go	improve training of junk filter	2023-02-11 23:00:12 +01:00