The whole point of a calendar program, at least for me, is the alarms. Sunbird has them, but they don't go off unless the calendar is open. This means you can (for example) have Thunderbird open with the calendar plugin, but if you don't have the calendar window open, you won't be reminded about anything. Sunbird won't be useful to me until this is fixed.
See requirements here and the tracker bug here. At the tracker bug, you can add your email to the CC, and put in a comment to let the developer's know that it is important to you!
The biggest weakness of this system is that it doesn't protect against some user's system sitting on a broadband DSL/Modem line that has a Trojan Horse used to e-mail the spam. AOL's system probably would only encourage more viruses/worm designed to make computers email relays.
Actually, that's not the point. Yes, a compromised AOL system could still send SPAM through AOL relays, but every spammer and his brother can't send emails from China pretending to be from AOL email addresses. That is, they can't if the receiver of the email checks this new protocol.
Obviously, this isn't going to do much, right now. But it could in the future. And if an ISP does this, and then also makes sure that people only send email with user IDs that match their account, we start to get traceability to SPAM email messages. But for this to be effective, people need to use it on both sides.
I'm a little nervous that this might make it more difficult to own your own domain and use it to send/receive email. Right now this is pretty easy with domain services that forward email to any other email address, partially because people can use their regular ISP SMTP server. With this kind of protocol, that might go away, or at least be more problematic for a non technical person.
I'm also uncomfortable with privacy issues with all of this. Making each email more traceable than it is now makes it harder to have anonymous email. But I have to say that the way things are right now, we need to do something. And since anonymous email has been abused by spammers so much, it might just not be practical while keeping email useful for the rest of us.
Slashdot Mirror
See requirements here
and the tracker bug here. At the tracker bug, you can add your email to the CC, and put in a comment to let the developer's know that it is important to you!
In order for this
Actually, that's not the point. Yes, a compromised AOL system could still send SPAM through AOL relays, but every spammer and his brother can't send emails from China pretending to be from AOL email addresses. That is, they can't if the receiver of the email checks this new protocol.
Obviously, this isn't going to do much, right now. But it could in the future. And if an ISP does this, and then also makes sure that people only send email with user IDs that match their account, we start to get traceability to SPAM email messages. But for this to be effective, people need to use it on both sides.
I'm a little nervous that this might make it more difficult to own your own domain and use it to send/receive email. Right now this is pretty easy with domain services that forward email to any other email address, partially because people can use their regular ISP SMTP server. With this kind of protocol, that might go away, or at least be more problematic for a non technical person.
I'm also uncomfortable with privacy issues with all of this. Making each email more traceable than it is now makes it harder to have anonymous email. But I have to say that the way things are right now, we need to do something. And since anonymous email has been abused by spammers so much, it might just not be practical while keeping email useful for the rest of us.