Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version 9.5.1
- Distro version bookworm
- Kernel version Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
- Architecture arm64
- SBC model RPi 3 Model B (aarch64)
Additional Information (if applicable)
- Software title DMA (Dragon Mail Agent)
Actual behaviour
I installed DietPi from scratch and a few dietpi-software titles. Afterwards I manually installed DMA (dragon mail agent) using apt install dma for mail sending purposes. During that dpkg-recofigure dma automatically kicked in and I provided the needed data. All fine.
After that I copied my working DMA config from another DietPi system, i.e. I copied both dma.conf and auth.conf to /etc/dma/ It’s just those two files that contain the mail configuration. Here my dma.conf:
SMARTHOST in-v3.mailjet.com
PORT 587
SPOOLDIR /var/spool/dma
AUTHPATH /etc/dma/auth.conf
SECURETRANSFER
FULLBOUNCE
MAILNAME /etc/mailname
MASQUERADE somemail@somedomain.com
But sending mails fails with a SSL handshake error, here are the log entries:
DietPi dma[2955]: new mail from user=root uid=8 envelope_from=something@mymail.com
DietPi dma[2955]: mail to=something@mymail.com queued as 21799.55ac8e3c40
DietPi dma[2956]: something@mymail.com trying delivery
DietPi dma[2956]: using smarthost (in-v3.mailjet.com:587)
DietPi dma[2956]: trying remote delivery to in-v3.mailjet.com [104.199.96.85] pref 0
DietPi dma[2956]: remote delivery deferred: SSL handshake failed fatally: error:0A00010B:SSL routines::wrong version number
I don’t assume DMA is the culprit - the same mail config works on another system -, but rather the victim of some SSL certificate or SSL config problem of the newly intalled DietPi. What can I do to solve that issue?