close
  • chevron_right

    How to use Jabber from SMS

    Stephen Paul Weber · Monday, 10 January - 08:30 · 1 minute

The Soprani.ca project, and Cheogram in particular, is pretty big on bidirectional gateways.  The most popular Cheogram-hosted instance, so popular that it gets to own Jabber IDs on cheogram.com, is a bidirectional gateway to the telephone network.  How is it bidirectional?  Don’t you need a Jabber ID to use it?  Of course not!

Sending a Message

From any SMS-enabled device, add +12266669977, which is the gateway’s phone number.  Send the following SMS:

/msg someone@server.tld Hello!

The user with Jabber ID someone@server.tld should shortly receive your message.  If they reply, what you see will depend on their relationship to the gateway.  If they have a backend route set (such as JMP, Vonage, or Twilio) then you will get an SMS from their associated phone number.  If not, you will get a message from the gateway’s number like this:

<someone@server.tld says> Oh, fun!

Joining a Chatroom

An SMS user can also join exactly one chatroom at a time.  Send this to the gateway’s number:

/join someroom@conference.server.tld

You should receive a message with the current list of participants, after which you will start seeing messages sent to the room.  After this point, any SMS send to the gateway’s number that is not a valid command (such as /msg) will be sent to your joined room as a message.  You can send /help at any time to get a list of other commands for leaving, setting your nickname, etc.

Making a Voice Call

To call a Jabber ID, first enter it into this form then dial one of the access numbers and follow it up with the extension generated by the form.

The extensions are often very long, so the easiest way to dial them on Android is to create a contact with a phone number of the form:

+access_number,*10816etc

If you have trouble with one access number, try another one.  If the Jabber ID you wish to call is very long some access numbers may time-out waiting for you to dial all the digits.

  • Ga chevron_right

    Docker Containers and Images explained Simply

    Danie van der Merwe · news.movim.eu / gadgeteerza-tech-blog · Sunday, 28 November - 19:22 · 1 minute

OK, this can be a rather technical subject, but give this video a chance without worrying too much about the details. Hopefully it conveys the concepts, because for me, it certainly slotted a few missing pieces together and the light started to shine. I was not clear on why and how volumes worked, and this cleared it up for me (to create persistent data to survive the container being recreated).

With Docker, you can, in theory, create a web application ready for use with just one or two commands. It is easy to update an application by re-pulling the latest image, or even move your apps and data to another server. This channel also has an excellent video unpacking how the docker-compose file actually works.

Using the command line is often the most precise way of doing this, but there are also graphical UI's like Portainer that will achieve the same container creation and management.

I'm using this, and a few other videos, to prepare to migrate my whole web hosting away from legacy installs, to all being docker containers on a different hosting platform. This will also make it easier to move again in the future if I need to.

See https://youtu.be/_trJf3GbZXg

#technology #docker #containers #selfhosting #howto

  • chevron_right

    Wolfenstein: Enemy Territory Single-Player mod is out now

    news.movim.eu / GamingOnLinux · Monday, 22 November, 2021 - 14:48 · 1 minute

While the actual single-player campaign of Wolfenstein: Enemy Territory never officially happened, a modder has now released their attempt to bring it back with Wolfenstein: Enemy Territory Single-Player.

Originally the official game was going to be an expansion to Return to Castle Wolfenstein and a standalone game, however it was cancelled and then released as a free to play online game, that lives on as ET: Legacy . At least now we can see some of what it might have become! This mod takes the online maps and sticks them together, to turn them all into a connected single-player and co-op campaign.

youtube video thumbnail
Watch video on YouTube.com

One of the ways which you can play it on Linux is to use iortcw , a free and open source game engine that's a ioquake3 features and fixes into RTCW code bases. If you wish to try it out, you can do so reasonably easily thanks to Luxtorpeda . Since it needs that, first up you need to get Luxtorpeda:

  1. Close Steam. Important, as Steam will not update the Steam Play compatibility tools list while open.
  2. Download latest version at https://github.com/luxtorpeda-dev/luxtorpeda/releases .
  3. Move and extract the contents of the downloaded archive to the compatibilitytools.d directory (create it if it does not exist) at ~/.steam/root/compatibilitytools.d/
  4. Start Steam.

Now to get Wolfenstein: Enemy Territory Single-Player sorted:

  1. Download Return to Castle Wolfenstein from Steam, with Luxtorpeda set as your compatibility tool. Right click the game on Steam, go to Compatibility and select the checkbox for "Force the use of a specific Steam Play compatibility tool" and select "Luxtorpeda".
  2. Once that's done, download the mod from Mod DB .
  3. Install it using Wine into the Return to Castle Wolfenstein directory. Somewhere like: /steamapps/common/Return to Castle Wolfenstein/ (exact path depends on what drive you install Steam games on). Making sure to pick the option that has "iortcw" in brackets. You should get a folder named "ET" in the main RTCW install location with all the mod contents.
  4. Add this Steam launch option to Return to Castle Wolfenstein by doing right click -> properties and then enter it into the launch options box: +set fs_game ET and then launch.

Once done, you then have Wolfenstein: Enemy Territory Single-Player setup and running with iortcw.

Article from GamingOnLinux.com taken from the RSS feed.
  • chevron_right

    SteamVR Overlay not working on Arch or Manjaro Linux? Here's a fix

    news.movim.eu / GamingOnLinux · Wednesday, 17 November, 2021 - 15:48 · 1 minute

Sadly, SteamVR on Linux continues to have quite a lot of quirks and over time it's gotten a little rough, here's a way to fix the SteamVR Overlay not working.

One of the most annoying bugs right now is how the SteamVR Overlay doesn't seem to work. Not just that, but even the settings menu from the main SteamVR menu doesn't seem to work either. This appears to be a problem on any Arch-like Linux distribution (EndeavourOS, Manjaro etc) and seems to originate with the vrwebhelper.

Thankfully, some clever people on the official Valve GitHub found a way to get it all working again and it's pretty simple.

First, find where SteamVR is installed, somewhere like this:

~/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/

Open the file "vrwebhelper.sh" and replace this line:

export LD_LIBRARY_PATH="${STEAM_RUNTIME_HEAVY}${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"

With this:

export LD_LIBRARY_PATH="${DIR}:${STEAM_RUNTIME_HEAVY}${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"

Now you need to download an older version of freetype2, which another helpful user put up on a download link ( web archive in case it vanishes) and then extract the files from the archive into the "vrwebhelper/linux64/" folder. After that, it all works just as expected again. Nice!

3249511061637164084gol1.jpg

Hopefully Valve will get around to solving this soon, perhaps once they've got a few hands free after the Steam Deck ships, which they're clearly putting a lot of their effort into right now.

Article from GamingOnLinux.com taken from the RSS feed.
  • chevron_right

    How to Subscribe to This Blog Using Movim

    Stephen Paul Weber · Friday, 5 November, 2021 - 00:00

This blog is powered by XMPP. That means it is federated over the Jabber network, it has a Jabber ID, and you can subscribe to it using a supporting Jabber client. One such client with support for subscribing, liking, and commenting is Movim. There are several public Movim instances including one hosted by upstream and one by chatterboxtown. Once you are logged in with a Movim instance, you can follow these steps to discover this blog and subscribe.

  1. Click Explore

    in the left navigation menu
  2. Click

    Communitites Servers
  3. If blog.jmp.chat is not yet known to this instance, you can use the search box to add it

    Search for a new server
  4. After entering blog.jmp.chat in the search box and hitting enter, you may need to click away to any other Movim page and then come back to the Communities Servers area as before.
  5. Click

    blog.jmp.chat
  6. Click

    JMP Blog
  7. Click

    subscribe
  8. New posts from the blog will now show up under News

    in the left navigation menu 

  • Sp chevron_right

    HOWTO: Query Spamhaus Safely

    pubsub.slavino.sk / spam_resource · Wednesday, 3 November, 2021 - 12:00 · 2 minutes

spamhaus.jpg
You'll recall me warning recently that using Spamhaus data to protect your mail server is a bad idea if you're using open or public DNS resolvers . TL;DR? Spamhaus is worried about too much traffic via public channels but blocking is implemented in a way that makes it effectively intermittent and potentially confusing. You could be fine for weeks and then suddenly you start bouncing all inbound mail accidentally. Or you could be querying a resolver that never shows ANY bad IPs to block, losing you out on the good spam filtering benefit that you were hoping for.

Here's what to do about that.
  1. No matter how you implement DNSBL usage, check your logs periodically. In the case of Spamhaus, look for the "127.255.255" response codes. That will indicate that your attempt to query Spamhaus data is being blocked , so you've got a problem. That problem is probably interfering with the delivery of legitimate mail.
  2. Test and make sure you are getting a response proving use of Spamhaus data. If you're a unix nerd, type "host 2.0.0.127.zen.spamhaus.org [IP address of your DNS server]" from the command line on your mail server. Make sure you get responses that say 127.0.0.2, 127.0.0.4, 127.0.0.10. That shows that your DNS resolver can get through to Spamhaus (at least for test entries). If you never get any response other than NXDOMAIN, it means your resolver isn't able to get data from Spamhaus and you'll never block a single piece of spam that way. Either the DNS server is not able to connect where it needs to, or you've typo'd something in your configuration. (Google Public DNS seems to only give NXDOMAIN responses to Spamhaus query attempts, for example.)
  3. Install and run your own DNS resolver (server) locally. This used to be a bit sketch back in the day. The common DNS software "bind" was such a magnet for exploits in the past that it drove me to stop hosting my own DNS. Things are slightly better today. There's a great caching DNS resolver called Unbound that will do exactly what you need. I've had smart friends like Tim Wicinski and John Levine tell me it is safe and that it works well, and I'm happily using it myself nowadays.
  4. Sign up for the Spamhaus Data Query service. They provide you with what amounts to an API key (a little short bit of text that will be unique to your queries) and you query the DNSBL via "[key].zen.dq.spamhaus.net" instead of "zen.spamhaus.org" --  allowing Spamhaus to see this traffic as you and you alone, not grouping any usage data together with that of a whole ISP or all users of a public resolver. Spamhaus offers a 30 day free trial of DQS access and say that an annual subscription to the Spamhaus data for commercial use starts at $250/year. Spamhaus also clarified for me that they provide free access for lower volume non-commercial use.
The point of this is so that Spamhaus sees your query traffic as from you and not all grouped together with all the traffic from your ISP or from a public DNS resolver. This makes you less likely to hit their unpublished query traffic limits through no fault of your own. (It does not, however, provide a free license to query Spamhaus millions of times a day.)

Which of these steps should you follow? All of them.

Značky: #howto, #spamhaus, #dnsbls, #Network

  • Sp chevron_right

    OpenDKIM and Postfix: Signing DKIM for multiple domains

    pubsub.slavino.sk / spam_resource · Tuesday, 2 November, 2021 - 12:00 · 1 minute

How do I use OpenDKIM with multiple domain names on a single postfix server? That's a question I myself had when I first set up my current VPS to host my current email system. So I searched around a bit. I found this guide , but it's kind of a pain in. Too much heavy lifting.

So I tried this instead. It's a bit of a hacker trick nobody seems to mention online: In your opendkim.conf file, where you specify the domain, you can just include multiple domains here, separated by commas.

Instead of
domain example.com
Just put
domain example.com,example.org,mydomain3.com
In your opendkim.conf file.

Upside : Super easy.
Downside : All domains have to share the same DKIM key, because there's only one DKIM key setting in opendkim.conf.

It works fine. Though you specify the domain name when creating a DKIM key, there's nothing in the key that is actually domain-specific. At scale, this is insecure. At the hobbyist level, where I've got three domains running on my one server that send a grand total of 150 emails a day, it's not a concern.

You can also put an asterisk (*) to wildcard the domain setting in opendkim.conf. However, I don't recommend this, because it will try to sign all mail for any domain, without checking to see if a DKIM public key actually exists for that domain. So if you send or forward any mail at all for any other domain, that mail will end up with a broken DKIM signature attached to it. An example where this will happen and be very bad for you is mailing lists. Some mailing lists rewrite the from address to use their own domain to bypass DMARC concerns, but not all do, and some only do it sometimes. So I strongly recommend against using a wildcard here, unless you know what you're doing.


Značky: #opendkim, #llinux, #dkim, #howto, #postfix, #Network

  • Sp chevron_right

    HOWTO: Create a BIMI logo file

    pubsub.slavino.sk / spam_resource · Monday, 1 November, 2021 - 12:00 · 1 minute

Looking for guidance on how to create your BIMI logo file? Valimail has a pretty good guide that explains the requirements and they also explain what to keep in mind when creating your BIMI graphic SVG file. Starting with:

  • Square
  • SVG Tiny Portable/Secure format
  • Solid background
  • Published via HTTPS

SVG meaning a Scalable Vector Graphics file, and particular type of SVG called SVG Tiny Portable/Secure (SVG P/S) . The image has to truly be a vector graphic ; the overall SVG spec does allow you to embed a bitmap in a file but this isn't allowed for SVG P/S or BIMI usage.

The Valimail guide goes on to explain how to manually edit the SVG file to convert it to the SVG P/S spec. But if you don't feel like editing XML files by hand, download this converter application that the BIMI (AuthIndicators) Working Group has shared here. I've used the Macintosh version and it works fine. (You may need to tell your Mac that it's OK to run this application.)

I used the tool to create a BIMI logo for XNND.com , just to see if I could do it. I don't have a VMC and I send a very low volume of mail, so I don't expect it to show up anywhere, but at least it was pretty easy to do.


Značky: #bimi, #xnnd, #valimail, #howto, #Network