[GH-ISSUE #58] message_id #51

New issue

Closed

opened 2026-02-28 01:22:56 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 01:22:56 +03:00

Owner

Originally created by @alissonlinneker on GitHub (Nov 13, 2012).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/58

The message_id just returns 0

Originally created by @alissonlinneker on GitHub (Nov 13, 2012). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/58 The message_id just returns 0

kerem closed this issue

2026-02-28 01:22:56 +03:00

kerem commented

2026-02-28 01:22:56 +03:00

Author

Owner

@eyedol commented on GitHub (Nov 15, 2012):

@alissonlinneker I'll look into this

@eyedol commented on GitHub (Nov 15, 2012): @alissonlinneker I'll look into this

kerem commented

2026-02-28 01:22:56 +03:00

Author

Owner

@saratovout commented on GitHub (Jan 22, 2013):

message-id = 0 always, only if user defined auto-delete. If the message remains, the counter increases.

@saratovout commented on GitHub (Jan 22, 2013): message-id = 0 always, only if user defined auto-delete. If the message remains, the counter increases.

kerem commented

2026-02-28 01:22:56 +03:00

Author

Owner

@ghost commented on GitHub (Jan 25, 2013):

That is bad. Now, because this supposedly unique message id is anything but unique, I have to perform all kinds of checks on the server side to determine if a message is something we have already seen or not. (If connection to server times out before SMSSync gets the "ok" reply from server, SMSSync will try to send it again later. A few times this has resulted for me in batches of a few hundred multipart messages being sent out several times, totalling a few thousand extra messages. Lucky me I have a 12000 message package so I didn't go over the quota, but without the said server side checks I added that could well happen. Also, duplicates are irritating to recipients.)

@ghost commented on GitHub (Jan 25, 2013): That is bad. Now, because this supposedly unique message id is anything but unique, I have to perform all kinds of checks on the server side to determine if a message is something we have already seen or not. (If connection to server times out before SMSSync gets the "ok" reply from server, SMSSync will try to send it again later. A few times this has resulted for me in batches of a few hundred multipart messages being sent out several times, totalling a few thousand extra messages. Lucky me I have a 12000 message package so I didn't go over the quota, but without the said server side checks I added that could well happen. Also, duplicates are irritating to recipients.)

kerem commented

2026-02-28 01:22:56 +03:00

Author

Owner

@saratovout commented on GitHub (Jan 25, 2013):

@agenttihirvinen imho you have to check it at the Web server, you can do so
$uid = md5($_POST["from"].$_POST["message"].$_POST["sent_timestamp"]);

@saratovout commented on GitHub (Jan 25, 2013): @agenttihirvinen imho you have to check it at the Web server, you can do so <code>$uid = md5($_POST["from"].$_POST["message"].$_POST["sent_timestamp"]);</code>

kerem commented

2026-02-28 01:22:56 +03:00

Author

Owner

@eyedol commented on GitHub (Feb 11, 2013):

This is related to #60 I'm going to close this.

@eyedol commented on GitHub (Feb 11, 2013): This is related to #60 I'm going to close this.