If it's your application principle, that there must not be identical queue entries, why not add a unique constraint (on member_email, member_id or whatever the identifier might be) to your queue table?
You can then insert your data with REPLACE INTO ... which in fact means:
If there's an existing value with the same primary key or unique key, it will be deleted before inserting the new one.
REPLACE INTO queue (member_email, queue_detail)
VALUES ('already_existing_email', 'some_data');
This would virtually UPDATE the entry of already_existing_email with 'some_data'.
If there's no entry *already_existing_email*, data will be inserted.