mirror of
https://github.com/mjl-/mox.git
synced 2024-12-26 08:23:48 +03:00
9e7d6b85b7
transferring the data only once. we only do this when the recipient domains are the same. when queuing, we now take care to set the same NextAttempt timestamp, so queued messages are actually eligable for combined delivery. this adds a DeliverMultiple to the smtp client. for pipelined requests, it will send all RCPT TO (and MAIL and DATA) in one go, and handles the various responses and error conditions, returning either an overal error, or per recipient smtp responses. the results of the smtp LIMITS extension are also available in the smtp client now. this also takes the "LIMITS RCPTMAX" smtp extension into account: if the server only accepts a single recipient, we won't send multiple. if a server doesn't announce a RCPTMAX limit, but still has one (like mox does for non-spf-verified transactions), we'll recognize code 452 and 552 (for historic reasons) as temporary error, and try again in a separate transaction immediately after. we don't yet implement "LIMITS MAILMAX", doesn't seem likely in practice. |
||
|---|---|---|
| .. | ||
| packages.txt | ||
| README.txt | ||
| v0.0.9.txt | ||
| v0.0.10.txt | ||
This directory lists incompatible changes between released versions for packages intended for reuse by third party projects, as listed in packages.txt. These files are generated using golang.org/x/exp/cmd/apidiff (see https://pkg.go.dev/golang.org/x/exp/apidiff) and ../apidiff.sh. There is no guarantee that there will be no breaking changes. With Go's dependency versioning approach (minimal version selection), Go code will never unexpectedly stop compiling. Incompatibilities will show when explicitly updating a dependency. Making the required changes is typically fairly straightforward.