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
..
account.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
account_test.go	add funtionality to import zip/tgz with maildirs/mboxes to account page	2023-02-16 09:57:27 +01:00
export.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
export_test.go	export more imap flags (eg $Junk/$NotJunk/$Forwarded) with maildirs, in dovecot-keywords file	2023-02-13 22:37:25 +01:00
import.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
import_test.go	add funtionality to import zip/tgz with maildirs/mboxes to account page	2023-02-16 09:57:27 +01:00
msgreader.go	mox!	2023-01-30 14:27:06 +01:00
msgreader_test.go	mox!	2023-01-30 14:27:06 +01:00
state.go	mox!	2023-01-30 14:27:06 +01:00
tmp.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
train.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
transact.go	mox!	2023-01-30 14:27:06 +01:00
validation.go	mox!	2023-01-30 14:27:06 +01:00