Mechiel Lukkien 79e522887e change error value "fatal io error" to just "io error" ...

"fatal" was meant as "we need fatal for the connection, it will be dropped".
but it sounds more serious, as if something needs to be fixed.

hopefully enough for issue #39 by ArnoSen

2023-11-02 15:56:01 +01:00

..

alignment.go

mox!

2023-01-30 14:27:06 +01:00

analyze.go

implement outgoing dmarc aggregate reporting

2023-11-02 09:12:30 +01:00

dnsbl.go

mox!

2023-01-30 14:27:06 +01:00

dsn.go

refactor common pattern of close & remove temporary file into calling the new store.CloseRemoveTempFile

2023-11-02 09:12:46 +01:00

error.go

for imap/smtp syntax errors, only echo the remaining buffer if the connection is authenticated

2023-03-10 11:32:34 +01:00

fuzz_test.go

implement "requiretls", rfc 8689

2023-10-24 10:10:46 +02:00

limitwriter.go

mox!

2023-01-30 14:27:06 +01:00

mx.go

implement dnssec-awareness throughout code, and dane for incoming/outgoing mail delivery

2023-10-10 12:09:35 +02:00

parse_test.go

mox!

2023-01-30 14:27:06 +01:00

parse.go

for submission over IPv6, allow missing "IPv6" tag in ip address (unless in pedantic mode)

2023-07-22 14:20:50 +02:00

rejects.go

implement message threading in backend and webmail

2023-09-13 15:44:57 +02:00

reputation_test.go

make mox compile on windows, without "mox serve" but with working "mox localserve"

2023-10-14 10:54:07 +02:00

reputation.go

add flag to ruleset that indicates a message is forwarded, slightly modifying how junk analysis is done

2023-08-09 22:31:37 +02:00

server_test.go

implement outgoing dmarc aggregate reporting

2023-11-02 09:12:30 +01:00

server.go

change error value "fatal io error" to just "io error"

2023-11-02 15:56:01 +01:00