What steps will reproduce the problem?
1. Client A send a message to Client B after that disconnect the Lan / Wifi Connection
2. Wait sometime to let the hibernation time tick out default 300sec
3. reconnect with Client A
4. Client B get the Error that recipient is unavailable
What is the expected output? What do you see instead?
Mod Smacks in Corporation with smacks offline should store the message in the offline storage if the Client is unavailable. If the message is received correctly Client B should not recieve a transmission failed error.
What version of the product are you using? On what operating system?
prosody-0.10 1nightly405-1~stretch
Debian 9 stretch
Please provide any additional information below.
This error is most persistent with mobile phones connected eg connection aborts and bad connections.
MattJ
on
Use mod_smacks_offline and a shorter read timeout (0.10+) to improve this behaviour somewhat. However the issue is complicated, it's the nature of how TCP works.
An alternative to mod_smacks is in the pipeline, which aims to solve problems like this and others.
I'm going to close this issue as "Won't Fix", not because there aren't improvements to make, but because those improvements won't be in the form of fixes to mod_smacks (instead a totally new approach).
What steps will reproduce the problem? 1. Client A send a message to Client B after that disconnect the Lan / Wifi Connection 2. Wait sometime to let the hibernation time tick out default 300sec 3. reconnect with Client A 4. Client B get the Error that recipient is unavailable What is the expected output? What do you see instead? Mod Smacks in Corporation with smacks offline should store the message in the offline storage if the Client is unavailable. If the message is received correctly Client B should not recieve a transmission failed error. What version of the product are you using? On what operating system? prosody-0.10 1nightly405-1~stretch Debian 9 stretch Please provide any additional information below. This error is most persistent with mobile phones connected eg connection aborts and bad connections.
Use mod_smacks_offline and a shorter read timeout (0.10+) to improve this behaviour somewhat. However the issue is complicated, it's the nature of how TCP works. An alternative to mod_smacks is in the pipeline, which aims to solve problems like this and others. I'm going to close this issue as "Won't Fix", not because there aren't improvements to make, but because those improvements won't be in the form of fixes to mod_smacks (instead a totally new approach).
Changes