Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
one of the group of addresses is unsuitable for it. Bug 1874
Broken-by: 3070ceeeed05, fa41615da702.
|
|
address give by routing
|
|
|
|
|
|
policy. Bug 1846
|
|
|
|
|
|
data-go-ahead and data-ack.
Bug 1872
|
|
Bug 1870
|
|
Bug 1870
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Broken-by: fb6833e0a559
|
|
|
|
This reverts commit dea4897244b409bf91dc60a7e5e4b3d06f123dd6.
It appears to induce spurious behaviour, seen in the testsuite. Possibly
the sha_hash update calls think the memory they are passed will still
be around later (eg. at sha_finish time)? A pity, since currently
we are allocating for the entire message body - which could easily
be MB or (future) GB.
|
|
When the buffer used for SMTP commands and message headers filled to flush
point, protocol sequencing was wrong.
|
|
|
|
record. Bug 1867
|
|
includes.
Broken-by: 44bc8f0c2f35
|
|
|
|
|