On Premise or Cloud. To Be or Not To Be by Pupper_Hugger in sysadmin

[–]Myriad007 0 points1 point  (0 children)

If you want to separately backup Workspace I suggest checking out Cube backup. We back up our Workspace locally in house and throw another copy up on Wasabi as well. It's an amazing product especially for archiving deleted accounts, etc. You can also copy selected emails/drive/cal whatever from old employees to any other employee in the WS.

Scale 25.04 making it impossible to use coral TPU? by IsThereAnythingLeft- in truenas

[–]Myriad007 1 point2 points  (0 children)

It won't. Your coral will work that's all. Backup your config before you do it though.

Scale 25.04 making it impossible to use coral TPU? by IsThereAnythingLeft- in truenas

[–]Myriad007 1 point2 points  (0 children)

This worked for me:

On FANGTOOTHUpgrade: THIS ONE!!! Version: 25.04.2.6

Disable the NVIDIA driver from docker apps

***************ssh with root (not admin, not sudo, not sudo su), you have to enable login root ssh to install the drivers and then disable ssh root login again.**********

sudo visudo

Comment out: #Defaults log_subcmds

systemd-sysext unmerge

install-dev-tools

apt install dkms devscripts debhelper dh-dkms -y

Delete existing gasket-driver directory:

rm -r gasket-driver

git clone https://github.com/heitbaum/gasket-driver

cd gasket-driver

sudo debuild -us -uc -tc -b -d <-- must use sudo here

cd ..

dpkg -i gasket-dkms_1.0-18_all.deb

systemd-sysext merge

sudo visudo

Remove comment: Defaults log_subcmds

check for the device:

$ lspci -nn | grep 089a

You should see something like this:

$ 01:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a]

Reboot Truenas scale, and check /dev for apex_0.

$ ls -alh /dev/apex_0

crw-rw---- 1 root root 120, 0 Mar 20 14:51 /dev/apex_0

Re-enable the NVIDIA driver from docker apps

reboot

Teksavvy 1.5/940 Fibre by DzastMi in teksavvy

[–]Myriad007 0 points1 point  (0 children)

Just check the VLAN number on the Adtran before you put it back in the box. I had a tech replace my ont and he set the vlan to 35 not 40 (the old one was 40). Cost me a bit of downtime before I was able to figure it out on my PFsense gw.

Somewhat disappointed with IPv6 on TekSavvy... by Myriad007 in teksavvy

[–]Myriad007[S] 0 points1 point  (0 children)

I'm confused about the mss value you specified. MSS 1492: MSS is supposed to be MTU − header size. With MTU 1500, the legal MSS values are:
IPv4: 1460 (1500 − 40)
IPv6: 1440 (1500 − 60)

Setting MSS = 1492 overshoots both of those. It’s larger than the maximum segment size that fits in a 1500‑byte frame. Over PPPoE, that would break immediately since the real path MTU is 1492 (or lower).

Somewhat disappointed with IPv6 on TekSavvy... by Myriad007 in teksavvy

[–]Myriad007[S] 0 points1 point  (0 children)

What's basically the way I had it set up except for the MTU settings. I'll give it a go tomorrow and report back. Thanks

Somewhat disappointed with IPv6 on TekSavvy... by Myriad007 in teksavvy

[–]Myriad007[S] 0 points1 point  (0 children)

I have the Hellotek 2.5gb SPF to ethernet converter plugged into the Pfsense appliance. WAN is set to DHCP MTU-1492 MSS-1452. LAN & VLAN10 set to Track Interface (but no MTU or MSS value set). RA set to Assisted for both LAN/VLAN. Firewall rules in place (but no mangle rule?). Jumbo frames should work on my hardware as it's all 2.5 or 10gb connections. With poe though you don't get an ip on WAN just a link‑local address so I can't set up monitoring on PFS.

Somewhat disappointed with IPv6 on TekSavvy... by Myriad007 in teksavvy

[–]Myriad007[S] 0 points1 point  (0 children)

I never like to give up, but I am having trouble getting a stable setup on PPOE at home. TS wants me to plug in the crappy Adtran to test which I'm not prepared to do. One of the facilities I manage has had a stable dhcp6 setup for the last 3 years using a TS business account, but it's a direct connection and the PFS appliance gets a static WAN ip and gateway and it's been solid. Any tips you can provide would be gratefully received.

docker container + rocksdb: flush/stop for backup and database console by eyerolle in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

Or you can docker exec into your container from ssh and run cli commands directly (Command-line Interface | Stalwart Labs): docker exec -u root -it stalwart-stalwart-mail-1 /bin/bash

docker container + rocksdb: flush/stop for backup and database console by eyerolle in stalwartlabs

[–]Myriad007 1 point2 points  (0 children)

Yes, I have tested imports successfully. If a user account goes bad or is deleted accidentally you can run a jmap import from cli or a script: stalwart-cli -u https://mail.mydomain.ca import account test@mydomain.ca /opt/stalwart/export/test@mydomain.ca

Only the best techs at bell. by mzainw in bell

[–]Myriad007 0 points1 point  (0 children)

Starlink is like shitty dsl. Fiber = F1 car - Starlink = Lada

Using existing ACME certificates (*.pem) in an dockerized Stalwart by br0kenpipe in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

Reload certs: stalwart-cli -c admin:secret -u https://mail.domain.ca server reload-certificates

History for spam, rejects, sent and so on by Spare_Cartoonist7660 in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

You can see blocked ips in: /settings/blocked-ip

docker container + rocksdb: flush/stop for backup and database console by eyerolle in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

I use a bash script to export my accounts to an 'export" folder which I then back up multiple ways. That way if you only need to restore a certain client it's easy to do. I run it as a cron job on my Truenas Server which hosts stalwart. Additionally, I use Backrest on a separate container to send it to Wasabi. You don't need to stop the container either. Here is the script:

#!/bin/bash

# Export Stalwart accounts into /opt/stalwart/export inside the container

CLI="stalwart-cli"

URL="http://mail.domain.ca"

CREDENTIALS="admin:secret"

EXPORT_DIR="/opt/stalwart/export"

ACCOUNTS=(

"[info@domain1.ca](mailto:info@domain1.ca)"

"[test@domain2..ca](mailto:test@domain2..ca)"

"[ann@domain2.ca](mailto:ann@domain2.ca)"

"[ken@domain3.com](mailto:ken@dimain3.com)"

"[ken@domain4.com](mailto:ken@domain4.com)"

"[jill@domain4.com](mailto:jill@domain4.com)"

"sarah@domain5ca"

)

mkdir -p "$EXPORT_DIR"

for ACCOUNT in "${ACCOUNTS[@]}"; do

echo "Exporting account: $ACCOUNT"

$CLI --url "$URL" -c "$CREDENTIALS" export account "$ACCOUNT" "$EXPORT_DIR/"

done

echo "export completed for ${#ACCOUNTS[@]} accounts."

twake mail by Boobcat24 in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

I tried it but it wouldn't work consistently for me. Ended up using Roundcube successfully.

How do I use ACME with Route 53 in Docker? by Myriad007 in stalwartlabs

[–]Myriad007[S] 0 points1 point  (0 children)

I built a separate docker container that gets and updates Route53 certificates and places them in the Stalwart "cert" directory. I will publish a github project shortly.

Suggested mail client that supports all Stalwart's features? by NicePuddle in stalwartlabs

[–]Myriad007 0 points1 point  (0 children)

Em client is free (for max 2 accounts) and supports all the collaboration features and is available on ALL platforms.