That would make sense. The domains on this server were transferred from other servers using Transfer Virtual Server in Virtualmin when I migrated from Vultr to SSD Nodes. That calls Webmin's backup and restore scripts, right? On 2022-05-14 00:00, Jamie Cameron wrote: Looks like this can happen if a domain was backed up and restored, as this will lead to incorrect ownership of the key files. This will be fixed in the next release of Virtualmin. [bugs:#5555] https://sourceforge.net/p/webadmin/bugs/5555/...
Okay, yesterday it happened again, on a different server. I've checked that there are no .key or .private ownership problems. It looks like it was associated with a Let's Encrypt renewal. The domain was not due for re-signing, but RRSIG and NSEC3 records changed. Fixed by manual "Sign Zone". Sending you a private message with the details.
Okay, yesterday it happened again, on a different server. I've checked that there are no .key or .private ownership problems. It looks like it was associated with a Let's Encrypt renewal. The domain was not due for re-signing, but RRSIG and NSEC3 records changed. Fixed by manual "Sign Zone". DNSSEC results: andycrooksyyc.com: ; fully validated andycrooksyyc.com. 300 IN SOA vivaldi.keenmouse.com. admin.keenmouse.com. 1636397181 3600 600 1209600 3600 andycrooksyyc.com. 300 IN RRSIG SOA 14 2 300 20220611145106...
That would make sense. The domains on this server were transferred from other servers using Transfer Virtual Server in Virtualmin when I migrated from Vultr to SSD Nodes. That calls Webmin's backup and restore scripts, right? Jim Grusendorf President Keen Mouse Productions Inc. https://keenmouse.com jgrusendorf@keenmouse.com Keen Mouse Productions Inc. <http://keenmouse.com> On 2022-05-14 00:00, Jamie Cameron wrote: Looks like this can happen if a domain was backed up and restored, as this will lead...
I've had this happen again. Sent you a private message with the details. The re-signing itself seems to be fine, but DNSSEC becomes invalid later, and I don't understand why. It happens sporadically with multiple domains on multiple Webmin servers.
Okay, I found that I can get output with resign.pl --debug. I just shortened my period between re-signs to force re-signing and all zones were re-signed successfully. I don't know what's causing the problem, but UptimeRobot keeps telling me occasionally that a site is down. When I check it, the DNSSEC/DANE Validator Firefox extension tells me that DNSSEC is failing. I manually re-sign the zone and then DNSSEC passes and UptimeRobot says the site is up again. I will add the --debug flag to the cron...
DNSSEC key re-signing not happening
Okay, I have ManageSieve working, so I'll try that.
When I have a mailbox forwarded automatically (in Virtualmin Users), the forwarding apparently happens before SpamAssassin sees the message. I'm worried about my server reputation, because I'm seeing other servers—especially Gmail—refusing delivery. Spam messages are getting stuck in the queue. Is there a way to have messages scanned first and spam dropped instead of forwarded? I guess I'm really asking how to filter all outgoing email with SpamAssassin, because there's always a chance my users could...
When I have a mailbox forwarded automatically (in Virtualmin Users), the forwarding apparently happens before SpamAssassin sees the message. I'm worried about my server reputation, because I'm seeing other servers—especially Gmail—refusing delivery. Spam messages are getting stuck in the queue. Is there a way to have messages scanned first and spam dropped instead of forwarded?
Yes, that worked for me.
I'm using ECDSAP384SHA384. Not sure if the others who have encountered the issue are using the same.
Fatal error signing DNS zone
I edit the procmail config in Servers > Procmail Mail Filter, but the warning should actually go in Servers > SpamAssassin Mail Filter > Procmail Spam Delivery. There's already a warning there that procmail has not been set up for server-wide operation; I think the best approach would be: The current warning should only be displayed if no modification of procmailrc by Virtualmin has been detected. Also add to the current warning that you should not configure procmail for SpamAssassin here if you...
Sorry, I've been chasing ghosts because I was trying to use Webmin's server-wide SpamAssasin procmail settings along with Virtualmin's per-virtual server settings. When sticking with just the latter, everything works. The one thing I'd like to request is what would have saved me from my own stupidity: A warning from Webmin when Virtualmin has already changed /etc/procmailrc. Thanks for indulging me.
Sorry, I've been chasing ghosts because I was trying to use Webmin's server-wide SpamAssasin procmail settings along with Virtualmin's per-virtual server settings. When sticking with just the latter, everything works. You can close this ticket. Sorry about that.
Or are the VIRUSMODE and SPAMMODE variables meant to indicate something else, like whether the delivery recipe ran? Just wondering because of where the assignments were placed in the original buggy file.
Actually, it appears that the variable assignments VIRUSMODE and SPAMMODE are not needed at all, because this file handles final delivery; it doesn't rely on /etc/procmailrc to deliver based on the status variables it sets. Or are those variables available to and used by something else? I won't propose removing them, just in case. Is this a Virtualmin bug, or does Virtualmin just tell Webmin to create a virtual server and then Webmin writes this file?
So this appears to be a problem with trying to use both Webmin's Procmail Spam Delivery and Virtualmin's spam settings. I thought you could use both and one or the other was intended to take precedence, but that's not the case. Virtualmin doesn't want you to use Webmin's Procmail Spam Delivery. It complains if you've done so when you run Re-Check Configuration. Virtualmin wants to manage procmail per virtual server. When you create the first virtual server with email, Virtualmin rewrites /etc/procmailrc...
So this appears to be a problem with trying to use both Webmin's Procmail Spam Delivery and Virtualmin's spam settings. I thought you could use both and one or the other was intended to take precedence, but that's not the case. Virtualmin doesn't want you to use Webmin's Procmail Spam Delivery. It complains if you've done so when you run Re-Check Configuration. Virtualmin wants to manage procmail per virtual server. When you create the first virtual server with email, Virtualmin rewrites /etc/procmailrc...
Just created a virtual server from Virtualmin. In the Spam and Virus Delivery Virtualmin module, Destination for virus emails was set to Throw away by default, and the code under "As written" in my original report is what I found in /etc/webmin/virtual-server/procmail/[server id] when I started troubleshooting. Interestingly, now that I have corrected the syntax in that file, Destination for virus emails shows as having Write to other file selected, with the associated field empty.
Yes, according to this: Default mailbox file (if not told otherwise, procmail will dump mail in this mailbox). Procmail will automatically use $DEFAULT$LOCKEXT as lockfile prior to writing to this mailbox. You do not need to set this variable, since it already points to the standard system mailbox. I don't know what the "standard system mailbox" is set to or how it's determined, but moving DEFAULT=$HOME/Maildir/ right after DROPPRIVS=YES fixed the problem for me.
Yes, according to this: Default mailbox file (if not told otherwise, procmail will dump mail in this mailbox). Procmail will automatically use $DEFAULT$LOCKEXT as lockfile prior to writing to this mailbox. You do not need to set this variable, since it already points to the standard system mailbox. I don't know what the "default mailbox file" is set to or how it's determined, but moving DEFAULT=$HOME/Maildir/ right after DROPPRIVS=YES fixed the problem for me.
I was not wrong about the e flag, but the syntax has other problems. Each recipe can have only one action line. In order to have more than one action line executed, you have to put them in braces, each with its own colon line, which may be unconditional. The VIRUSMODE variable assignments must be enclosed in braces in order to not be interpreted as folder names. Tested and working: DROPPRIVS=yes :0cw | /etc/webmin/virtual-server/clam-wrapper.pl /bin/clamdscan :0e { :0 { VIRUSMODE=1 } :0 /dev/null...
I may be misunderstanding the operation of the e flag, as with the lines reordered, I'm still not seeing viruses blocked. I'm looking into it further.
Virtual server procmail lines out of order, viruses not blocked
SpamAssassin Procmail config does not keep variables at top of procmailrc
I have five Debian 10 servers. One of them updated to Webmin 1.974 a while back, but the others see no update available and the Upgrade Webmin module is not visible. Is there a way to force an update?
Thank you!
Ubuntu 20.04.1, Webmin 1.962, Virtualmin 6.13 When the canonical hostname Let's Encrypt certificate is renewed on one of my servers, the certificate is copied to Postfix and Webmin, but not to Dovecot. I remember when I first installed this server, the Copy to Dovecot button disappeared in Virtualmin > Server Configuration > SSL Certificate when I clicked the Copy to Postfix button, so it appears that whatever configuration flag that's supposed to set never got set. Is there a way to set it manu...
Will doxfer.webmin.com ever come back? Is the documentation available somewhere else now?
Still down. Will the docs ever be available again?
This is the second day in a row that doxfer.webmin.com has been down. Will it be back soon?
Yes and yes.
Postfix Server monitor shows service down on remote servers when it's not
Ah! Thank you!
Disabling disk quotas does not survive reboot
Never mind, I just got it working! Thanks for this tool, and please close this t...
Basic usage example
I've just installed SemanticScuttle 0.98.5. When I attempt to register a user, I...
I've just installed SemanticScuttle 0.98.5. When I attempt to register a user, I...