Issue Bug Closed

#92934Mail FileSpool and MemorySpool toString() wrong

Markus Gerdes 11/25/20, 16:43 updated 12/22/20, 11:02

Description

Both spools iterate over all currently queued mails and concatenate these.

Using a spool because of async sending and the resulting performance is not good.

Using the FileSpool and sending mails to 1000+ recipients results most of the time in a browser timeout. The toString is called indirectly through the AbstractTransport class as a representation for the transports name.

To regain performance and be compatible we need to cleanup toString() to just return an identifier instead of the whole queue.

Reviews 2