Updated accordingly in CVS, test and advise. The change does the following: - Message will only expire once expiry date is reached - Once the max allowed number of notifications has been sent, mbuni will stop sending notifications until the message expires.
On May 29, 2006, at 11:29, Deon van der Merwe wrote: > Hi Paul, > > On 5/29/06, Paul Bagyenda <[EMAIL PROTECTED]> wrote: >> It does actually expire after the 3 attempts. Perhaps its shouldn't >> and only wait for message expiry (but stop sending notifications)? >> > > You see, if the subscribers handset is set to *not* automatically > retreive the message (like mine is) the message will expire after the > notifications. But I have the notification on my phone, so there is > no problem with the actual delivery of that. But Mbuni has no way of > knowing this, right? > > >> On May 25, 2006, at 20:43, Deon van der Merwe wrote: >> >>> Hi, >>> >>> I am a little confused about the way in which the message expiry >>> works: >>> - default expiry set to 7 days on server >>> - number of notifications: 3 >>> - backoff: 300 >>> >>> A subscriber now sends a message to another subscriber (with default >>> expiry). The destination subscriber does not retreive the message >>> right away. All 3 notifications is sent. Subscriber still does not >>> retreive it. >>> >>> Question then: >>> - does the message expire at the end of those 3 attempts? >>> - does the message expire after 7 days? >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://mbuni.org/mailman/listinfo/users_mbuni.org >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://mbuni.org/mailman/listinfo/users_mbuni.org >> > > _______________________________________________ > Users mailing list > [email protected] > http://mbuni.org/mailman/listinfo/users_mbuni.org _______________________________________________ Users mailing list [email protected] http://mbuni.org/mailman/listinfo/users_mbuni.org
