https://bugs.exim.org/show_bug.cgi?id=2390
--- Comment #2 from Heiko Schlittermann <h...@schlittermann.de> ---
No mail is lost. Exim detects the spool file problem (mostly when renaming the
file, that was already renamed by an instance running on another host),
sometimes because of mangled spool file content. If Exim detects such problem,
it 4xx the message. Mangled spool files (if any) are autoremoved after 4 days.
So, the chance is quite high, that nobody ever notices such problems. I
reproduced it fairly reliable with 32 parallel senders dumping messages to 3
instances on a shared spool directory.
yes | head -n 1000 \
| parallel -j 32 --progress swaks -S -f <sender> -t <recipient> -s <server>
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
