I guess some of this stuff is general, some should be in bugs section and some other stuff in to do area. So, I'll simply put it here, with the announcment about these new features.
1. Confirmation message layout
Acception confirmation information should be in BEGINNING of message, not at the end.
If email is long, then it's very unclear to (busy) user what happened. Suggested form:
2. Feedback messages
*Trashmail stuff here*
-- Sent message follows --
* Original sent message *
IMHO! I wouldnt sent out those confirmation messages. I mean accepted or deleted at all. There is simply no point of doing that. And in some cases it might actually create a problem. If messages is ignored (expire or delete), then it is. If it's confirmed by recepient or send then it is. No need to send crap.
3. Reply masking
It seems that reply masking is broken when using whitelisting. So if I reply to message that came trough whitelisting then I can't reply to it using my trashmail.net address (using reply masking).
4. Confirmtion by email
I know lot of users that have access to email, but they don't have access to web. Due corporate restrictions or other reasons. Like using simple PDA email. If there could be some way to confirm messages using email only? I could suggest several methods, but I guess it's out of scope for this comment list.
5. Possible loop problem
I tried if you have a looping problem. Confirm, confirmation message by confirming confirmation message. You dont seem to be having this problem. I was already laughing that I'll crash the system. I have seen too many times "moronic" problems. But I'm very happy that you didnt have this problem.
6. Manage mail queue
Doesnt work now for some reason:
Internal error: Invalid trashmail username format in trashmail_getuid(...) call. Please contact the system administrator.
Btw. It did work in the morning with Firefox, it might be URL or server related. Didnt have time to check it completely out.
Url: https://ssl.trashmail.net/?login=1&auth ... _mailqueue
I might know the reason. I ignore all non-session cookies. Do you use those? I changed some settings, no help. So I guess its not about this, there is some another reason. I think it's funny that login is 1 and auth is 1. I'll try to enter key information to url and see what happens. Nope, didnt help either.
Managing WL mail queue and addresses work for another account and wont work for another. So it doesn't have anything to do with web browser.
Afaik whitelisting works now very well.
7. Disable confirmation
Seems to be working as I expected. But in this case, should we create bounce or not? It seems that no bounce is being generated. My opinion is that in this special case there should be bounce message. So sender knows that message was rejected. So they can try another way contacting recipient.
Update: Bounce was generated, I didn't receive it in time due slow email systems.
8. Whitelist when sending
This should work, it's important. When I send email, rules allowing reply to be sent back without confirmation is important. Every message confirmation is exception. But this can create dead lock kind of situation like loop. Both are waiting for confirmation which is waiting for confirmation.
9. Confirmation message from address
That's though question too. I think it should be the recipient address instead of email@example.com
. Think about that deadlock situation. And think about general email "street wise rules". I'll get email from some robot that asks me to confirm my email. Afaik, it would be much nicer to get it from the address that I sent my email to. Because then it would be immediately clear that it's about my email. Not about "confirming my email" for "some reason". Or do you now automaticly process any bounces to robot address? Fixing issue 1. might solve this. I guess you'll user robot address to prevent looping?
10. Black listing?
If there are problems, there might be requirement to add blacklisting which prevents from whitelisting. I guess there might be abuse cases where some user (sender) whitelists all messages even confirmation for every message is required. Then black listing would help.
End of summary
These are my first impressions, comments and thoughts.
I tried to eliminate a maximum of bugs!
- That's very nice...
I think this is good discussion opening... Lets hear other comments!