Package naming advice requested

Hello,

This is pushing the OT boundary, but Dan exhorted us to make an effort
at naming our packages well, so...

I'm building a package which implements a "zero-overhead whitelist" by
extracting cookies from sender addresses, similarly to qdated. The
cookie will be made by hashing the sender address and a local secret,
possibly using surf; if the sender's address hashes to match the
cookie, then the email is accepted.

The intent of this package is to provide working email addresses for
use in vendor accounts, or accounts at PayPal, which can't be used by
third parties even if they are leaked to spammers. This also allows
users of CR or other whitelisting systems to leave high-profile
senders like PayPal out of their whitelists, reducing false negatives.

Such an address would be usable if the spammer claims to be the sender
allowed by the cookie, but that information is not part of the cookie,
so this can be regarded as a low-probability event.

I've considered the name qsender, but that appears to be used for
something else. It seems to me that qcookie is too vague, and qfromok
doesn't have a ring to it.

Any suggestions?

Thanks!
Len.