bmwrapper broadcasts

[chan] bitmessage
Jul 8 04:34

I am trying to send a broadcast with bmwrapper. The messages send but they are neither broadcasted nor do they show up in the bm qt sent list. I have tried numerous configs. I have prefixed the to address with 'broadcast@' I have tried prefixing broadcast@ to the smtp username. Does anyone know why this might not work?

[chan] bitmessage
Jul 8 13:07

There have been no changes to bmwrapper in 3 years, meanwhile there have been significant changes to PyBitmessage which may have caused an incompatibilty.

[chan] bitmessage
Jul 8 13:13

Has the API implementation changed that drastically over time? If you have specific knowledge where it is likely to break please share it. It works great as an interface to various email clients, and also mailing list manager types. Up to and including the May/June early asyncore inclusion as a network access alternative. chan / PMLs so far seem OK with it in addition to regulare p-p BMs I'd hate it if that changed and I need to reconfigure stuff that have been routinely deployed to non-tech test users since 2014Q4

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Jul 8 13:54

> Has the API implementation changed that drastically over time? There was refactoring and new parameters added, but as far as I know all is backwards compatible. > It works great as an interface to various email clients, PyBitmessage has had a SMTP client/server interface for a while, maybe you can try that instead, but it doesn't have a broadcast interface and you still need a separate IMAP server. Peter Surda Bitmessage core developer

[chan] bitmessage
Jul 10 14:27

Just tested bmwrapper and broadcasting works perfectly. I think the problem you experienced is that PyBitmessage does not have proper pipelining - it doesn't catch broadcasts it sends as a subscribed broadcast. The broadcast shows up in the sent folder in the Messages tab but does not show up in the inbox folder of the Subscriptions tab if you subscribe to your own address.

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
BitMessage crash Nov 18 14:28 2
Tor replacement Nov 18 13:10 4
Alternative Bitmessage port for official assignment with IANA? Nov 18 02:20 1
codewordtest2 Nov 17 21:52 1
bitmessage history Nov 15 08:43 28
stream and pool diagram Nov 12 12:05 21
( ͠° ͟ ʖ ͡°) Nov 10 09:51 2
I'm back. Nov 9 17:55 1
streams and pools Nov 7 01:37 1
How to examine bitmessage objects Nov 7 00:45 5
Tor curve vs bm curve Nov 7 00:45 4
keys.dat values Nov 6 23:16 2
Bitmessage history Nov 6 08:08 9
Pseudo-mailinglist vs chans? Nov 5 21:47 2
bitmessage node rating? Nov 5 21:32 2
can I connect to both onions and standard? Nov 5 19:33 11
Bitmessage won't exit cleanly Nov 4 18:06 2
keys.dat must be encrypted Nov 4 12:09 12
Question Nov 3 20:09 5
It's actually not that hard to de-anonymize someone on bitmessage. Nov 3 19:49 8
It's actually not that hard to de-anonymize someone on Nov 2 14:18 1
Bitmessage snapshots Nov 2 13:14 3
Why chan address? Nov 1 06:26 2
HASH Q Oct 31 21:16 1
bitpetite scam Oct 31 08:34 2
GitHub Supports Islamic Clitoris Removal Oct 31 01:02 14
What exactly is the address of [chan] general? Oct 30 05:29 7
MiNode addr bug Oct 27 11:53 1
Hi, users ! Oct 27 07:18 5
No incoming connections now Oct 26 09:40 33
RE: bitmessage implementation in any other programming language Oct 23 17:01 1
disabled address still working Oct 23 12:47 8
apinotifypath Oct 22 01:11 1
checkdeps.py error Oct 21 22:04 3