Hello,
The read receipt function in RC does not seem to work. I had put in a query for confirmation in the forum, but nobody could confirm.
Could anybody confirm whether the read receipt is working. If so, RC1 or RC2.
Thanks and regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
I cannot confirm this. Sending a message that asks for a read receipt works correctly with RoundCube.
But if you mean opening a message that requires a confirmation with RoundCube, this is not implemented yet. The difficulty here is to remember that we already sent a receipt and not asking the user every time he/she opens the message.
~Thomas
kmnair wrote:
Hello,
The read receipt function in RC does not seem to work. I had put in a query for confirmation in the forum, but nobody could confirm.
Could anybody confirm whether the read receipt is working. If so, RC1 or RC2.
Thanks and regards
kmn
List info: http://lists.roundcube.net/users/
On 11/29/07, Thomas Bruederli roundcube@gmail.com wrote:
I cannot confirm this. Sending a message that asks for a read receipt works correctly with RoundCube.
But if you mean opening a message that requires a confirmation with RoundCube, this is not implemented yet. The difficulty here is to remember that we already sent a receipt and not asking the user every time he/she opens the message.
~Thomas
Thanks Thomas for the clarification.
I naturally thought that since there is a read receipt button, the mail when opened in RC will also have this acknowledgement facility.
I checked up from a squirrelmail client and confirmed this. Yes, it works.
But do you have any plans to implement this at the recipient (opening) side too. Without this, this has much limited use, especially in offical use, where this can used as an official confirmation mechanism.
There are some posts in the forum requesting for this feature. Perhaps you could take a look at the squirrelmail plugin for this for a starter.
And Thomas, RC is such a nice software. Thank you SO much for contributing this to the world.
Best regards.
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
kmnair wrote:
But do you have any plans to implement this at the recipient (opening) side too. Without this, this has much limited use, especially in offical use, where this can used as an official confirmation mechanism.
I see the importance if this feature. After looking at the specification, the status is saved as message flag and is therefore independent of the mail client. If you confirm the message in one client, another one should not ask again for it. I just started to implement some IMAP basics to support this in RoundCube but it'll take a while.
Feel free to open a feature request ticket for this in order to remind the developers to finish it.
~Thomas _______________________________________________ List info: http://lists.roundcube.net/users/
Without this, this has much limited use, especially in offical use, where this can used as an official confirmation mechanism.
Since this can be disabled in most MUAs, I would not recommend using
this for "official" use.
IMHO it can never be counted on to work 100% of the time.
Some people like it, but most have a higher expectation than what it
really provides.
Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265
List info: http://lists.roundcube.net/users/
On 11/29/07, Thomas Bruederli roundcube@gmail.com wrote:
kmnair wrote:
But do you have any plans to implement this at the recipient (opening) side too. Without this, this has much limited use, especially in offical use, where this can used as an official confirmation mechanism.
I see the importance if this feature. After looking at the specification, the status is saved as message flag and is therefore independent of the mail client. If you confirm the message in one client, another one should not ask again for it. I just started to implement some IMAP basics to support this in RoundCube but it'll take a while.
Feel free to open a feature request ticket for this in order to remind the developers to finish it.
~Thomas
Thank you very much Thomas.
I am much concerned because I am running RC on an official network on an experimental basis and such features count a lot.
I will file a feature request in trac. But the features for V.1 are frozen it seems.
Best regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
On 11/30/07, chasd chasd@silveroaks.com wrote:
Without this, this has much limited use, especially in offical use, where this can used as an official confirmation mechanism.
Since this can be disabled in most MUAs, I would not recommend using this for "official" use. IMHO it can never be counted on to work 100% of the time.
Some people like it, but most have a higher expectation than what it really provides.
Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265
Yes Charles, there are shortcomings. But something is still better than nothing.
It is true that this can be disabled in MUA, but perhaps this can be set at the adminstrator level to be a forced preference, which the user cannot turn off.
In squirrelmail, a flag stating that the return receipt has been requested will be there until you send the receipt.
When you open the mail, there is a button asking for sending the receipt. You can click "cancel" and go into the message, but then the above flag remains.
Perhaps the"cancel" feature can be disabled at the admin level or the sender level.
Regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
On 11/29/07, Thomas Bruederli roundcube@gmail.com wrote:
I see the importance if this feature. After looking at the specification, the status is saved as message flag and is therefore independent of the mail client. If you confirm the message in one client, another one should not ask again for it. I just started to implement some IMAP basics to support this in RoundCube but it'll take a while.
Feel free to open a feature request ticket for this in order to remind the developers to finish it.
~Thomas
Thank you very much Thomas.
I am much concerned because I am running RC on an official network on an experimental basis and such features count a lot.
I will file a feature request in trac. But the features for V.1 are frozen it seems.
Best regards
kmn
Hello Thomas,
On going through the trac, I find a feature request already made one year ago by somebody else.
Ticket #1483963
Could you update the priority.
Thanks and regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
I just commited a first implementation of this feature. You can check it out from SVN or download it from http://nightly.roundcube.net/trunk/roundcubemail-trunk-r938-20071210.tgz
Please try it out and post errors as comments to http://trac.roundcube.net/ticket/1483963
~Thomas
kmnair wrote:
On 11/29/07, Thomas Bruederli roundcube@gmail.com wrote:
I see the importance if this feature. After looking at the specification, the status is saved as message flag and is therefore independent of the mail client. If you confirm the message in one client, another one should not ask again for it. I just started to implement some IMAP basics to support this in RoundCube but it'll take a while.
I am much concerned because I am running RC on an official network on an experimental basis and such features count a lot.
Hello Thomas,
On going through the trac, I find a feature request already made one year ago by somebody else.
Ticket #1483963
List info: http://lists.roundcube.net/users/
On 12/10/07, Thomas Bruederli roundcube@gmail.com wrote:
I just commited a first implementation of this feature. You can check it out from SVN or download it from http://nightly.roundcube.net/trunk/roundcubemail-trunk-r938-20071210.tgz
Please try it out and post errors as comments to http://trac.roundcube.net/ticket/1483963
~Thomas
Thank you Thomas for the VERY prompt action.
I will check it up and post comments.
Best regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
On 12/10/07, kmnair kmnair@gmail.com wrote:
On 12/10/07, Thomas Bruederli roundcube@gmail.com wrote:
I just commited a first implementation of this feature. You can check it out from SVN or download it from http://nightly.roundcube.net/trunk/roundcubemail-trunk-r938-20071210.tgz
Please try it out and post errors as comments to http://trac.roundcube.net/ticket/1483963
~Thomas
Thank you Thomas for the VERY prompt action.
I will check it up and post comments.
Best regards
kmn
Hello Thomas,
That is a good implementation. I have posted some desirable modifications in the trac.
I need to disable (remove) the "cancel" button in the send confirmation request pop up screen. Could you please tell me how this can be done?
Thanks and regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
kmnair wrote:
That is a good implementation. I have posted some desirable modifications in the trac.
And here are the answers: http://trac.roundcube.net/ticket/1483963#comment:5
I need to disable (remove) the "cancel" button in the send confirmation request pop up screen. Could you please tell me how this can be done?
We use the javascript confirm() function which comes up with two buttons. You can replace it with an alert() call. But as already commented in trac, I don't see the reason why to do this. The user should always have the choice.
~Thomas _______________________________________________ List info: http://lists.roundcube.net/users/
On 12/13/07, Thomas Bruederli roundcube@gmail.com wrote:
kmnair wrote:
That is a good implementation. I have posted some desirable modifications in the trac.
And here are the answers: http://trac.roundcube.net/ticket/1483963#comment:5
I need to disable (remove) the "cancel" button in the send confirmation request pop up screen. Could you please tell me how this can be done?
We use the javascript confirm() function which comes up with two buttons. You can replace it with an alert() call. But as already commented in trac, I don't see the reason why to do this. The user should always have the choice.
~Thomas
Thank you very much Thomas. I sent the mail before I checked the trac.
I will check up on the caching problem and let you know.
Regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
kmnair wrote:
Thank you very much Thomas. I sent the mail before I checked the trac.
I will check up on the caching problem and let you know.
I just committed some changes that should fix the caching issues. See http://trac.roundcube.net/changeset/942
~Thomas _______________________________________________ List info: http://lists.roundcube.net/users/
On 12/13/07, Thomas Bruederli roundcube@gmail.com wrote:
kmnair wrote:
Thank you very much Thomas. I sent the mail before I checked the trac.
I will check up on the caching problem and let you know.
I just committed some changes that should fix the caching issues. See http://trac.roundcube.net/changeset/942
~Thomas
Thank you SO much, Thomas.
Regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/
On 12/13/07, Thomas Bruederli roundcube@gmail.com wrote:
I just committed some changes that should fix the caching issues. See http://trac.roundcube.net/changeset/942
~Thomas
Thanks Thomas.
I applied the diff. But the issue seems to remain.
<snip from earlier post>
I need to disable (remove) the "cancel" button in the send confirmation request pop up screen. Could you please tell me how this can be done?
We use the javascript confirm() function which comes up with two buttons. You can replace it with an alert() call. But as already commented in trac, I don't see the reason why to do this. The user should always have the choice.
Thanks and regards
kmn _______________________________________________ List info: http://lists.roundcube.net/users/