Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
901
Dovecot / Re: Mail accounts management Spinning
« on: October 17, 2021, 08:34:38 PM »
Did I read that right?
2,200 (two thousand 2 hundred) SUB-Domains?
An option you might try is just do a domain forward thru the registrar.
2,200 (two thousand 2 hundred) SUB-Domains?
An option you might try is just do a domain forward thru the registrar.
902
Information / Re: CWP Pro paid invoice
« on: October 17, 2021, 08:31:49 PM »
Are you trying to pay with Skrill or PayPal?
903
How to / Re: Cluster
« on: October 02, 2021, 05:29:43 PM »
I just looked, didn't see this Option under User Accounts -> CWP -> CWP Migration 
Server is running latest 0.9.8.1084
I wish this was an option.
Server is running latest 0.9.8.1084
I wish this was an option.
904
SSL / Re: All domains getting ssl error
« on: October 02, 2021, 05:25:06 PM »facing the same problem couldnt find the error in error log too...
apache/domlogs/smithikamobiles.in error log also not showing anything
domain name : http://smithikamobiles.in without ssl working fine
https://smithikamobiles.in not working getting ERR_SSL_PROTOCOL_ERROR
any one help me to fix more than 5 days searching for solution...
Check NAT mode that @PargonianKnight mentioned.
Your domain comes up pointing to 192.168.1.1 when you view it.
905
Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.
« on: October 02, 2021, 05:22:41 PM »
Check with CloudFlare.
If you setup the outgoing mail server as the FQDN of your server, it will use that be default, not another domain.
And should work without problem.
But I've seen some weird stuff when using cloudflare.
Because you are using their DNS.
If you setup the outgoing mail server as the FQDN of your server, it will use that be default, not another domain.
And should work without problem.
But I've seen some weird stuff when using cloudflare.
Because you are using their DNS.
906
SSL / Re: Lets Encrypt ROOT CA Expired
« on: October 01, 2021, 06:03:43 AM »
Only the DST Root CA X3 certificate expired on 30 September 2021.
The certificates are now using the ISRG Root X1 certificate automatically.
So there is nothing that needs to be done to "fix".
They only talk about older devices which may not get security updates anymore.
If you have your encryptions stings setup correctly this shouldn't be a problem.
The certificates are now using the ISRG Root X1 certificate automatically.
So there is nothing that needs to be done to "fix".
They only talk about older devices which may not get security updates anymore.
If you have your encryptions stings setup correctly this shouldn't be a problem.
907
Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.
« on: September 30, 2021, 09:21:28 PM »
This might sound like a stupid question, but need to make sure there is a SSL certificate for the server.
The server does have a FQDN pointed to its IP?
Have you run the (Server Settings -> Change Hostname) to get the servers SSL certificate?
The server does have a FQDN pointed to its IP?
Have you run the (Server Settings -> Change Hostname) to get the servers SSL certificate?
908
Information / Re: CWP Pro paid invoice
« on: September 29, 2021, 06:38:01 PM »
Have you submitted a Billing support ticket?
We use PayPal when paying our invoices without problems.
We use PayPal when paying our invoices without problems.
909
Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.
« on: September 29, 2021, 06:34:48 PM »
Postfix is your SMTP (Outgoing)
Dovecot is your IMAP/POP3 (Incoming)
Are you having problems with outbound emails (postfix) or incoming emails (dovecot)?
In your email client, temporarily change you incoming email server name to your server FQDN.
That will troubleshoot if your MX has a problem.
Dovecot is your IMAP/POP3 (Incoming)
Are you having problems with outbound emails (postfix) or incoming emails (dovecot)?
In your email client, temporarily change you incoming email server name to your server FQDN.
That will troubleshoot if your MX has a problem.
910
Postfix / Re: Postfix not allowing inbound email. Outbound is working fine.
« on: September 27, 2021, 05:29:17 PM »Sep 25 02:40:54 host1 postfix/master[802591]: terminating on signal 15
Sep 25 02:40:54 host1 postfix[803347]: Postfix is running with backwards-compatible default settings
Sep 25 02:40:54 host1 postfix[803347]: See http://www.postfix.org/COMPATIBILITY_README.html for details
Sep 25 02:40:54 host1 postfix[803347]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
Sep 25 02:40:54 host1 postfix/postfix-script[803402]: warning: not owned by root: /etc/postfix/./mysql-virtual_vacation.cf
Sep 25 02:40:54 host1 postfix/postfix-script[803415]: starting the Postfix mail system
Sep 25 02:40:54 host1 postfix/master[803417]: daemon started -- version 3.4.8, configuration /etc/postfix
Sep 25 02:40:54 host1 postfix/qmgr[803419]: 47E0B65D4B5: from=<billscott92787@gmail.com>, size=3953, nrcpt=1 (queue active)
Sep 25 02:40:54 host1 postfix/lmtp[803422]: 47E0B65D4B5: to=<kelly@familymaidservices.com>, relay=host1.wvwgssolutions.com[private/dovecot-lmtp], delay=2194, delays=2194/0.02/0/0, dsn=4.2.0, status=deferred (host host1.wvwgssolutions.com[private/dovecot-lmtp] said: 451 4.2.0 <kelly@familymaidservices.com> Internal error occurred. Refer to server log for more information. [2021-09-25 02:40:54] (in reply to end of DATA command))
Sep 25 02:41:04 host1 postfix/smtpd[803432]: connect from c-73-135-99-232.hsd1.md.comcast.net[73.135.99.232]
Sep 25 02:41:17 host1 postfix/smtpd[803442]: connect from mail-oo1-f42.google.com[209.85.161.42]
Sep 25 02:41:17 host1 postfix/smtpd[803442]: warning: loading SNI data for mail.familymaidservices.com: ignoring PEM type: CERTIFICATE REQUEST
Sep 25 02:41:17 host1 postfix/smtpd[803442]: Anonymous TLS connection established from mail-oo1-f42.google.com[209.85.161.42] to mail.familymaidservices.com: TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
Sep 25 02:41:17 host1 postfix/smtpd[803442]: NOQUEUE: reject: RCPT from mail-oo1-f42.google.com[209.85.161.42]: 450 4.7.0 <Kelly@familymaidservices.com>: Recipient address rejected: defer_if_permit requested; from=<billscott92787@gmail.com> to=<Kelly@familymaidservices.com> proto=ESMTP helo=<mail-oo1-f42.google.com>
Sep 25 02:41:18 host1 postfix/smtpd[803442]: disconnect from mail-oo1-f42.google.com[209.85.161.42] ehlo=2 starttls=1 mail=1 rcpt=0/1 bdat=0/1 quit=1 commands=5/7
e.com[209.85.210.41] ehlo=2 starttls=1 mail=1 rcpt=1 bdat=1 quit=1 commands=7
Sep 25 00:43:07 host1 postfix/pipe[665998]: 2BBA4FC1B7: to=<kelly@familymaidservices.com>, relay=dovecot, delay=0.09, delays=0.06/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: lda(kelly@familymaidservices.com): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied
I don't know what I'm not doing right or what needs changed to get this working. A buddy of mine setup CWP, and everything, and email just worked, but mine I've had nothing but issues getting to get it working. Any tips? I got this far tailing the log and playing around with settings until I got email to go outbound and not hit spam box.
Something happened in the last update to 0.9.8.1084.
Rebuild your mail server from inside CWP, like @studio4host suggested, and you should be good to go.
911
Installation / Re: clarification with thunderbird setings
« on: September 24, 2021, 07:28:52 PM »I don't know. Google is sending everything to spam on different severs. I am using tbird client. When I set up an account I normally use mail.mydomain.com for smtp and imap. But when I do that, tbird throws an error saying certificates dont match. When I view the certificate from letsencrypt it says server.mydomain.com and not mail.mydomain.com
Can someone help me stratighten this mess out.?
Now I just tried sending from a different domain and the LE cert says common name is www.mydomain.com
Thanks.
Under your SSL Certificates, make you you have the Mail service added.
Then in your DNS:
Create MX record: mail MX 0 mail.domain.com
Then create an A record for mail 1.2.3.4
SMTP should use StartTLS, while incoming should use SSL/TLS
We currently use Thunderbird 91.1.1
912
Installation / Re: clarification with thunderbird setings
« on: September 24, 2021, 07:25:11 PM »I am also getting this error message in tbird when I send mail.
Unable to communicate securely with peer: requested domain name does not match the server’s certificate.
Just got that also after the update today to 0.9.8.1084
Rebuild your Postfix configuration and that should go away.
913
Updates / Re: Why not implement TLS 1.3 support per default
« on: September 24, 2021, 07:22:49 PM »Hi, i just received the new Update CWPpro version: 0.9.8.1081 and was a bit disappointed to see a bunch of new Webserver templates but still no TLS 1.3 implementation per default.
It would be very cool if you could implement TLS 1.3 out of the Box in CWP or is there a Reason why you still doesn't have implemented it yet?
thanks
There is a simple way to enable this, along with HTTP/2.0 & ALPN:
https://www.mysterydata.com/how-to-enable-tls-1-3-in-apache-on-cwp-control-web-panel-centos-7-centos-8-el7-el8/
914
Updates / Re: 0.9.8.1084 Bug
« on: September 24, 2021, 07:20:12 PM »
Rebuilt the Postfix configuration and all seems to be working again.
915
Updates / 0.9.8.1084 Bug
« on: September 24, 2021, 07:15:06 PM »
When 0.9.8.1084 auto installed today, there is a bug with sending emails now using the domain name:
Sending of the message failed.
Unable to communicate securely with peer: requested domain name does not match the server's certificate.
The configuration related to [domain name] must be corrected.
Everything was working fine before the update.
SSL certificate is still vaild.
Sending of the message failed.
Unable to communicate securely with peer: requested domain name does not match the server's certificate.
The configuration related to [domain name] must be corrected.
Everything was working fine before the update.
SSL certificate is still vaild.
