intention of the code is to store original value
in the results, but it was stored incorrectly, so we
end up with two records in results: first with success
and ISO date, second with value only that is treated
as failure.

If the cpan shell tries to run these, they'll connect to your live
database and webserver and start making tickets by invoking mailgate

This means any data cat'ed onto a tempfile actually goes to /dev/null
We should fix this when we switch to RT::Test

RT-Authen-ExternalAuth can block user creation in the mailgate by
returning 0 from CanonicalizeUserInfo if the user doesn't exist in the
external system.  RT blindly assumes that
RT::Interface::Email::CreateUser will return a user, so it returns the
CurrentUser and 1 without checking to see if the creation was
successful.

This results in CommandByMail getting a defined but unloaded CurrentUser

Checking for the Id prevents later failures

Before, we would use the Queue passed to rt-mailgate --queue
but we might be modifying a ticket in a completely different queue,
which would affect which CFs are available

Previously, CustomField.{Foo Bar} wouldn't be matched