Do now allow messages to be their own parents in threading
A message may send its own ID in the `references` header. In that case
the threading algorithm must ignore the closed loop and not set the
message as its own parent, to prevent an infinite loop later when
checking for anchestors.
Signed-off-by:
Christoph Wurst <christoph@winzerhof-wurst.at>
Loading
Please register or sign in to comment