Daily Shaarli
November 6, 2026
Romance pour alto et orchestre op.85
Max Bruch
L'œuvre
Romance pour alto et orchestre, en fa majeur (Op. 85)
Plesk administrator can specify a custom email address to be used as a mail relay. The email address will be used as the sender address for all Plesk email notifications enabled in the Tools & Settings > Notifications menu.
To adjust the settings, perform the following:
- Log into Plesk
- Edit the Plesk panel.ini file by adding the lines below there:
[notification] senderAddress=<custom email address>
Tailscale’s download page doesn’t list if it’s available for FreeBSD. But it does work on FreeBSD (tested on Release 14). Here’s how:
Install the package:
pkg install tailscale
Edit /etc/rc.conf to add tailscaled_enable="YES"
or
service tailscaled enable
Run service tailscaled start. If you get an error, reboot.
After reboot, run tailscale login.
Copy the url, copy paste in a browser and approve the connection. ////
XigmaNAS:
Copy /usr/local/bin/tailscale, /usr/local/bin/tailscaled and /usr/local/etc/rc.d/tailscaled to local storage from working full version of FreeBSD.
Use script to copy symlinks into /usr/local/bin and /usr/local/etc/rc.d/ after bootup.
Configuration and State Storage
| Directory Path | Purpose |
|---|---|
/usr/local/bin/ |
Tailscale CLI & Daemon |
/usr/local/etc/rc.d/ |
Tailscale Service/Daemon script |
/var/db/tailscale/ |
Stores state data for Tailscale |
The default configuration file locations for Tailscale on FreeBSD is /var/db/tailscale/ for state files and configuration settings. Additionally, logs can be found in /var/log/tailscale.
Tempo di Mazurka
Alexander Müller
L'œuvre
Tempo di Mazurka, pour piano
Open the panel.ini editor using the command:
plesk conf panel.ini
Using the Plesk Panel Interface:
- Install the Panel.ini Editor from the Extensions menu in Plesk.
- Open Panel.ini Editor at Extensions > My Extensions.
- In Panel.ini Editor, switch to the Editor tab. If the editor is empty, do the following...
- Edit the content and click Save
Balada d floripondios du Concierto de Otoño
Arturo Márquez
L'œuvre
Concierto de Otoño. Concerto pour trompette et orchestre
System mails generated by your Plesk server, such as bounce notices from MAILER-DAEMON@hostname.example.com, cron output from root@hostname.example.com, or Plesk notifications, often land in the spam folder, even though normal user mailboxes (e.g. info@example.com) deliver fine.
This happens because your server’s hostname is a subdomain of your main domain, and your main domain’s DMARC policy is silently inherited by every subdomain that does not publish its own. Without dedicated authentication for the hostname, self-generated system mail fails DMARC alignment and is quarantined by your own authentication stack.
This article walks through the root cause, the one-DNS-record fix that solves the visible symptom for most admins, and the full authentication setup for getting non-bounce system mail to genuinely pass DMARC.
The quick fix: override subdomain inheritance
Add a dedicated DMARC record for your server hostname with p=none:
_dmarc.hostname.example.com. IN TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
This overrides apex inheritance for the hostname subdomain only. Your main domain DMARC policy stays strict, your user mailboxes stay protected, but system mail from the hostname stops being quarantined.
This single record solves the symptom for most admins. No Plesk changes are required. No server configuration is required. //
If you also want cron output and Plesk notifications (not just bounces) to genuinely pass DMARC, continue to the complete fix below. If you just want your system mail out of spam, you can stop here.