Mechiel Lukkien 8affa12c39 prevent panic when starting with a mox.conf that references an ACME provider that isn't configured ... the error handling code attempts to collect all error messages it encounters, to print them all at the end, so you can fix them all before trying again. so we try to continue preparing the config after an error. in this case, we continued as if acme.Manager was properly set and nil-dereferenced it. for issue #2, from hismailbulut		2023-02-21 23:06:11 +01:00
..
admin.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
cid.go	mox!	2023-01-30 14:27:06 +01:00
config.go	prevent panic when starting with a mox.conf that references an ACME provider that isn't configured	2023-02-21 23:06:11 +01:00
dir.go	mox!	2023-01-30 14:27:06 +01:00
doc.go	mox!	2023-01-30 14:27:06 +01:00
ip.go	mox!	2023-01-30 14:27:06 +01:00
lastknown.go	mox!	2023-01-30 14:27:06 +01:00
lifecycle.go	add funtionality to import zip/tgz with maildirs/mboxes to account page	2023-02-16 09:57:27 +01:00
lifecycle_test.go	add funtionality to import zip/tgz with maildirs/mboxes to account page	2023-02-16 09:57:27 +01:00
limitauth.go	add basic rate limiters	2023-02-07 23:18:15 +01:00
lookup.go	mox!	2023-01-30 14:27:06 +01:00
msgid.go	mox!	2023-01-30 14:27:06 +01:00
rand.go	support cram-md5 authentication for imap and smtp	2023-02-05 16:29:03 +01:00
recvid.go	mox!	2023-01-30 14:27:06 +01:00
setcaphint.go	mox!	2023-01-30 14:27:06 +01:00
sleep.go	mox!	2023-01-30 14:27:06 +01:00
tlsinfo.go	mox!	2023-01-30 14:27:06 +01:00