# lxmf: propagation and receiving works but no message

_Help · started by Rudi Mentaire on Mon, Sep 7, 2026 5:07 AM_

---

## Original post

**Rudi Mentaire** · Mon, Sep 7, 2026 5:07 AM

Hello,

today the following happened to me: I (again) sent a short lxmf message to myself (for testing: same computer, different addresses).  Propagating the messages worked, getting (synchronizing) worked, but the messages were not received. Hmm?

All programs used the same propagation node.  I then switched to a different node, and it worked again as expected. Does that mean that the respective node was disfunctional, or are there other possible reasons?

I would want to try to find a more reliable setup.  Does it make sense to use the node behind the progagation address also as an interface - would this improve reliability?  Although I can't imagine that it would have made a difference in this case - connectivity doesn't seem to have been an issue.

I also wonder whether I should just use my own propagation node...

---

## Reply 1

**Rudi Mentaire** · Mon, Sep 7, 2026 5:10 AM

Wow, and I can now edit and delete my message. And what you now see under my name, the "65e0..." hex code, is now really my lxmf address, not my identity. Very cool!

---

## Reply 2

**Rudi Mentaire** · Tue, Sep 8, 2026 2:05 PM

A little update: while sideband and meshchatx are actually working relatively seamlessly as messengers, nomadnet very often fails to send to the propagation node. I'm using 1.4.0 at this moment. Sometimes a stamp is created, but then sending just gets stalled. The same propagation node ids are working well in other programs.

---