diff options
author | Daniel Gultsch <daniel@gultsch.de> | 2016-03-10 14:47:55 +0100 |
---|---|---|
committer | Daniel Gultsch <daniel@gultsch.de> | 2016-03-10 14:47:55 +0100 |
commit | 7eb736227e63985e163bd9ef08a71d8b78c4d3bf (patch) | |
tree | e9bc936e224f816c4879a076b6a5d293506d4162 /README.md | |
parent | 1e75283250aee20b0fd2a73b7b3407801391f953 (diff) |
mention mod_smacks_offline and ejabberds settings in readme
Diffstat (limited to '')
-rw-r--r-- | README.md | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -197,6 +197,12 @@ connection again. When the client fails to do so because the network connectivity is out for longer than that all messages sent to that client will be returned to the sender resulting in a delivery failed. +Instead of returning a message to the sender both ejabberd and prosody have the +ability to store messages in offline storage when the disconnecting client is +the only client. In prosody this is available via an extra module called +```mod_smacks_offline```. In ejabberd this is available via some configuration +settings. + Other less common reasons are that the message you sent didn't meet some criteria enforced by the server (too large, too many). Another reason could be that the recipient is offline and the server doesn't provide offline storage. |