I just realized that on Github the Spamassassin Version 2.1.0 was released. Im mising it in the Forum Plugin Store though.
Regards
Pimbo
I just realized that on Github the Spamassassin Version 2.1.0 was released. Im mising it in the Forum Plugin Store though.
Regards
Pimbo
ciscllc yeah good guess I had the same idea, it just doesnt work to accept the new certfificate, cause it wont get accepted. you have to delete readd the account
Nuxwin standard ios mail app, error code is not present right now, i will try to create a mail account and renew the certificate and upload the error message. The certificicate just cannot be trusted after the renew.
Yes and no because its in both standard mail account apps for ios and android
Dovecot, while receiving. But doenst make a difference cause the error is the same for sendung as well. You can resolve the issue by deleting the account from your mobile an readding it, until the next certificate renew
Dear all,
when my Mail-Service Lets Encrypt Certificates are renewed I always get a problem on Andorid or iOS because the new certficate is not directly accepted. I have to delete the mail account and add it again. The certificate itself was renewed correctly.
Do you know why?
Debian 9 64bit
Imscp 1.5.x
Lets encrypt 3.5.0
Proxmox 5.2
Debian 9.4
LXC
I-MSCP 1.5.3
no logs
Although I used this how to: i-MSCP inside a LXC container (Managed by Proxmox 4.x)
My mounted logs have read an write permission. What can I do about it?
/dev/mapper/pve-vm--100--disk--1 on /var/www/virtual/icynet.de/logs/xxx.de type ext4 (rw,relatime,stripe=16,data=ordered)
Same issue here.
Fixed the problem
Hallo zusammen,
ich würde gerne einzelne Absenderadressen nur an bestimmte Empfänger weiterleite (postfix). Aktuell nutze ich nur ne alias Liste die alle ankommenden mails ungefiltert weiterleitet.
Danke für jedwede hilfe!
meine idee bisher: header_checks mit
/^From: *xxx@xxx.de*/ REDIRECT xxx@gmail.com
aber dann passiert einfach nix
Guten Tag,
IMSCP 1.4.6
Debian Jessie
LetsEncrypt 3.3.0
Bei mir zeigt Filezilla (ftp port 21) einen Fehler an, dass mein Zertifikat bereit am 2.11.17 abgelaufen wäre, obwohl es laut IMSCP Admin Panel noch bis 2018 gültig ist. Woran könnte das liegen?
Thank you!