Sebb

Given that these mostly come from generated files, it might be better to just ignore them as suggested here: https://dev.to/qortex/ruby-suppress-those-warnings-you-can-t-do-anything-about-6ie

This appears to be working OK now

I think the problem here is that the subject should be provided as an original UTF-8 string, not already encoded for transmission as shown.

See PR #1570

If both messages have ids, the == method invokes encoded without first creating a copy. This changes the original instance, which does not seem right. It would be better to...

There are currently two tests which check that a provided message-id compares equal with nil. These would need to be changed: https://github.com/mikel/mail/blob/bf02b6772e4df20e165c008f595f4eadb8c595a7/spec/mail/message_spec.rb#L1719 and https://github.com/mikel/mail/blob/bf02b6772e4df20e165c008f595f4eadb8c595a7/spec/mail/message_spec.rb#L1730

Allowing Message-Id to match against nil causes unexpected behaviour for the == operator See https://github.com/mikel/mail/pull/1540 At present, Message equality (==) is not transitive.

Seems to be all OK

I think GSOC should have its own list. I suggest: general@ for community discussion tools@ for projects/reporter etc gsoc@ for all things GSOC issues@ for COMDEV Jiras I think it...

The list needs to be created first