Control Web Panel
WebPanel => Installation => Topic started by: venty on June 23, 2025, 06:09:43 PM
-
Hi,
in the settings I have "root forwarder file detected, all root emails are forwarded to: test@mydomain.com", but I don't receive a single message from root..??
Distro Name: AlmaLinux release 9.6 (Sage Margay). PHP version 7.4.33
BR
Venty
-
Why don't you just set the destination e-mail under CWP Settings > Edit Settings?
-
Why don't you just set the destination e-mail under CWP Settings > Edit Settings?
Hi,
I set the email address in CWP Settings > Edit Settings..., but now I notice that on the main Dashboard screen --->> https://prnt.sc/VyPVfAh6UwRW
However, when I select it ---->>>https://prnt.sc/dJ3-jVjipz-X
When I select details for a specific message, there is not much information... What should I check or do?
BR
Venty
-
Root is sending OK.
Monitored Mail Queue, nothing stuck there.
Also check your SPAM folder.
-
Yea, gmail isn't receiving emails from the server, but other domains are.
This could have to do with rDNS/PTR still not being updated around the world.
There not on the servers queue, so that part is good.
-
Something weird is afoot...
CLI email from our server to our internal email isn't working either.
-
Something weird is afoot...
CLI email from our server to our internal email isn't working either.
Hi,
to understand that the thing is not only with me ...?
BR
Venty
-
Check some of your DNS entries for the new server, and also your SPAM folder at Gmail.
-
Hi,
Thank you very much for the answers, I only no receive messages that are sent from root (from the panel - ldf, csf, backup...) to the email address that I have set in the CWP Settings > Edit Settings... (this address is on this server office@mydomain.com)...:
1. I have no problem sending messages from email accounts on the server to Gmail...
2. There are no messages in the SPAM folder...
3. The DNS... .I think it's fine, I have SPF and DKIM...
What else should I check?
And I would like to ask if it matters whether I installed and configured the firewall CSF before creating the first user in CWP?
BR
Venty
-
Hi,
Thank you very much for the answers...
Solved - I restored the original main.cf
Thanks...
BR
Venty
-
Postfix?
-
Postfix?
Yes....
-
Glad you got it working.
I received the CLI tests and so did mail-tester.com
But that is odd, only things that where added to main.cf where:
UNDER (# rules restrictions):
smtp_helo_name = $myhostname
Step 4 of https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/dkim-not-working-on-almalinux-9-with-cwp (https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/dkim-not-working-on-almalinux-9-with-cwp)/
Was also added to the bottom:
milter_default_action = accept
milter_protocol = 6
smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891
Those are the same as our servers. ???
-
Hi,
The thing apparently happened when adding the code from step 4 - apparently I copied this code between the main one and the original file by mistake and I wasn't getting the messages...
I put the code back in the original file and then added the code from step 4 and now everything is fine...
BR
Venty
-
Hi,
In step 4 of https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/dkim-not-working-on-almalinux-9-with-cwp /
you say to add the code:
milter_default_action = accept
milter_protocol = 6
smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891
Now in the same article, you say that if we have problems to add the following code :
smtpd_milters = inet:127.0.0.1:8891
non_smtpd_milters = $smtpd_milters
milter_default_action = accept
What is the difference and which is better?
BR
Venty
-
If you system has a problem with localhost, you force it with 127.0.0.1
It's says, "If you are having problem with Step 4, change the ending to:"
I'll update that to say REPLACE the 4 lines in Step4 with.
milter_protocol = 6, is the default. So where it's there or not doesn't matter, it's just to make sure.
non_smtpd_milters = $smtpd_milters, just redirects it to look at $smtpd_milters, or to be safe you can specify that line again. Just like milter_protocol.
--
I looked at Postfix.
CWP put the line in main.cf under #network settings, when it builds/re-builds the mail server.
Checked all of our servers, and it says "mydestination = $myhostname = name.hostname.com'
Not sure why CWP does that, as it's redundant, and just replaces $myhostname on that line.
While the line smtp_helo_name = $myhostname, I had entered manually.
@overseer, what does your servers look like for that line?
-
CWP systems are as you described, mydestination = $myhostname = name.hostname.com
On a dedicated server I maintain (non-CWP), it is more clasically set:
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain, mail.$mydomain, host.domain.com, mail.domain.com
-
Hi,
for me :
mydestination = $myhostname = name.hostname.com
where name.hostname.com is replaced with my ...
and no record smtp_helo_name = $myhostname
and as far as I can tell and test, DKIM works with localhost...
BR
Venty
-
Hi,
for me :
mydestination = $myhostname = name.hostname.com
where name.hostname.com is replaced with my ...
and no record smtp_helo_name = $myhostname
and as far as I can tell and test, DKIM works with localhost...
BR
Venty
and in fail main.cf no record: "smtp_helo_name"
-
Hi,
for me :
mydestination = $myhostname = name.hostname.com
where name.hostname.com is replaced with my ...
and no record smtp_helo_name = $myhostname
and as far as I can tell and test, DKIM works with localhost...
BR
Venty
and in fail main.cf no record: "smtp_helo_name"
-
I don't have the directive on my CWP servers, nor on a dedicated server I maintain. These are the closest I have:
# smtpd_helo_restrictions
smtpd_helo_restrictions =
reject_invalid_helo_hostname,
reject_non_fqdn_helo_hostname
smtpd_helo_required = yes
-
Hi,
Is it necessary to add a record to the file main.cf and what is it for:
smtp_helo_name = $myhostname
Thanks in advance!
BR
Venty
-
You are specifying your server's hostname to announce it in the HELO exchange when it is talking to other mail servers. As you could see by my code block above, I (and many other mail admins) reject mail from servers that don't have their HELO hostname set (as many spammers don't use proper protocol and give proper HELO greetings. So for best mail delivery results and to avoid bounced mails, you should set your helo hostname as Starburst recommended.
-
Hi,
Thank you very much, I understood everything, just one last thing to clarify :)
When going through CWP, I go to the Postfix Mail Server Manager, and check the box where it is shown in the picture:
https://prnt.sc/TXLDNMUAot9p
In this case, when building the mail server, what exactly add or change in the entries in the main.cf file ?
Many thanks in advance!
BR
Venty
-
CWP put the line in main.cf under #network settings, when it builds/re-builds the mail server.
Checked all of our servers, and it says "mydestination = $myhostname = name.hostname.com'
Not sure why CWP does that, as it's redundant, and just replaces $myhostname on that line.
Wow, on a new Alma install using CWP's re-build mail server function, it must've buggered up the mydestination BAD with the duplicative line. So another postfix instance rejected it. Study the 5.5.2 Helo rejection:
<overseer@domain.net>: host mail.domain.com[111.111.111.111] said: 501
5.5.2 <srv1.domain.net?=?srv1.domain.net>: Helo command
rejected: Invalid name (in reply to RCPT TO command)Hard setting it to mydestination = srv1.domain.net was far more acceptable to the other postfix server!
-
Hi,
Thank you very much, I understood everything, just one last thing to clarify :)
When going through CWP, I go to the Postfix Mail Server Manager, and check the box where it is shown in the picture:
https://prnt.sc/TXLDNMUAot9p
In this case, when building the mail server, what exactly add or change in the entries in the main.cf file ?
Many thanks in advance!
BR
Venty
Hi,
My question is whether when rebuilding the mail server, will everything we added or changed in the main.cf file be saved or deleted?
Thank you very much!
BR
Venty
-
Keep backups of your main config files (postfix, dovecot, apache, nginx) and vhost definition files. Assume that rebuilding mail & web servers will nuke your changes -- so have a backup to replace the default or merge back in your changes. But you shouldn't ever have to change those once the server is set up.
-
Hi,
Ok, lastly, for this topic, the following remains as a summary:
1.In main.cf under #network settings, replace:
"mydestination = $myhostname = name.hostname.com'
with "mydestination = srv1.domain.net"
????
2. To the main.cf file, add:
UNDER (# rules restrictions):
smtp_helo_name = $myhostname
????
BR
Venty
-
mydestination = $myhostnameis most canonical, then you only have to change it once at the top of the file if the hostname needs to change. But for any of the main directives (mydestination, smtp_helo_hostname, smtpd_sasl_local_domain), you can hardcode the hostname if you want. Just get rid of CWP's buggy double equals on a line (interpreted as setting a string, then a variable).