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.
46
CentOS-WebPanel Bugs / Re: Cwp-Cwp migration fail
« on: March 03, 2020, 07:12:03 PM »Sandeep says I have to create a separate thread with Fail details. If it is a system Fail why do you need any more information. This is the job of developers to investigate. We identify Failures....developers maybe try to fix.
Others have reported same issue. Developers can create API key and test. Very simple. What is the problem with Sandeep? Do you deny the problem which you have already acknowledged in a previous post that migration does not work properly?
where is the log ? where it fails on your server ? if you don't know how to check then
check this topic
http://forum.centos-webpanel.com/index.php?topic=7410.msg29215;topicseen#msg29215
I am not looking for solution. I AM IDENTIFYING YOUR PROBLEM.....NOT MY PROBLEM. Developers can investigate or ignore. That is there decision.
48
CentOS-WebPanel Bugs / Re: CWP to CWP migration problem
« on: March 03, 2020, 12:28:42 PM »hi we've fixed some bugs with CWP migration module
Some bugs? Would you say that a missing wheel on your car is a "bug"?
49
CentOS-WebPanel Bugs / Cwp-Cwp migration fail
« on: March 03, 2020, 11:09:06 AM »
Sandeep says I have to create a separate thread with Fail details. If it is a system Fail why do you need any more information. This is the job of developers to investigate. We identify Failures....developers maybe try to fix.
Others have reported same issue. Developers can create API key and test. Very simple. What is the problem with Sandeep? Do you deny the problem which you have already acknowledged in a previous post that migration does not work properly?
Others have reported same issue. Developers can create API key and test. Very simple. What is the problem with Sandeep? Do you deny the problem which you have already acknowledged in a previous post that migration does not work properly?
50
CentOS-WebPanel Bugs / Re: CWP to CWP migration problem
« on: March 02, 2020, 11:48:23 PM »
Total Fail
51
CentOS-WebPanel Bugs / Re: cwp to cwp migration
« on: March 02, 2020, 11:45:10 PM »
cwp-cwp migration = system fail
52
CentOS-WebPanel Bugs / Rebuild mail server DKIM
« on: March 02, 2020, 03:06:02 PM »
I noticed that if I rebuild mailserver with checkbox for DKIM selected, process tries to update ClamAV. Then the error messages says fix Yum.
See my other post in http://forum.centos-webpanel.com/index.php?topic=8256.0
It seems that the DKIM checkbox does not correlate properly.
See my other post in http://forum.centos-webpanel.com/index.php?topic=8256.0
It seems that the DKIM checkbox does not correlate properly.
53
Postfix / Re: problem with multiple email account in centos web panel
« on: March 02, 2020, 01:51:30 PM »
Besides, where are you seeing that?
Dashboard-Email-Mailserver Manager
54
Postfix / Re: problem with multiple email account in centos web panel
« on: March 01, 2020, 05:57:12 PM »if DKIM DNS is not working then it is DNS host issue.FYI if I rebuild mailserver from cwp with ONLY DKIM box checked, this is what the results are:
Code: [Select]
Loaded plugins: fastestmirror
No Packages marked for removal
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.linode.com
* epel: dfw.mirror.rackspace.com
* extras: mirrors.linode.com
* updates: mirrors.linode.com
Resolving Dependencies
--> Running transaction check
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
---> Package clamav-server-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
---> Package clamd.x86_64 0:0.101.5-10.el7 will be obsoleting
--> Processing Dependency: clamav-filesystem = 0.101.5-10.el7 for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: clamav-lib = 0.101.5-10.el7 for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9(CLAMAV_PRIVATE)(64bit) for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9(CLAMAV_PUBLIC)(64bit) for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9()(64bit) for package: clamd-0.101.5-10.el7.x86_64
--> Running transaction check
---> Package clamav-filesystem.noarch 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-update-0.99.2-8.el7.x86_64
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-data-0.99.2-8.el7.noarch
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-filesystem.noarch 0:0.101.5-10.el7 will be an update
---> Package clamav-lib.x86_64 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-lib.x86_64 0:0.101.5-10.el7 will be an update
--> Processing Dependency: libjson-c.so.2()(64bit) for package: clamav-lib-0.101.5-10.el7.x86_64
--> Processing Dependency: libpcre2-8.so.0()(64bit) for package: clamav-lib-0.101.5-10.el7.x86_64
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
--> Running transaction check
---> Package clamav.x86_64 0:0.99.2-8.el7 will be updated
---> Package clamav.x86_64 0:0.101.5-10.el7 will be an update
---> Package clamav-data.noarch 0:0.99.2-8.el7 will be updated
---> Package clamav-data.noarch 0:0.101.5-10.el7 will be an update
---> Package clamav-filesystem.noarch 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-lib.x86_64 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
---> Package clamav-update.x86_64 0:0.99.2-8.el7 will be updated
---> Package clamav-update.x86_64 0:0.101.5-10.el7 will be an update
---> Package json-c.x86_64 0:0.11-4.el7_0 will be installed
---> Package pcre2.x86_64 0:10.23-2.el7 will be installed
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirrors.linode.com
* epel: dfw.mirror.rackspace.com
* extras: mirrors.linode.com
* updates: mirrors.linode.com
Package perl-Mail-DKIM-0.39-8.el7.noarch already installed and latest version
Package perl-Mail-SPF-2.8.0-4.el7.noarch already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
---> Package clamav-server-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
---> Package clamd.x86_64 0:0.101.5-10.el7 will be obsoleting
--> Processing Dependency: clamav-filesystem = 0.101.5-10.el7 for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: clamav-lib = 0.101.5-10.el7 for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9(CLAMAV_PRIVATE)(64bit) for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9(CLAMAV_PUBLIC)(64bit) for package: clamd-0.101.5-10.el7.x86_64
--> Processing Dependency: libclamav.so.9()(64bit) for package: clamd-0.101.5-10.el7.x86_64
---> Package libopendkim.x86_64 0:2.11.0-0.1.el7 will be installed
--> Processing Dependency: libbsd.so.0(LIBBSD_0.0)(64bit) for package: libopendkim-2.11.0-0.1.el7.x86_64
--> Processing Dependency: libbsd.so.0()(64bit) for package: libopendkim-2.11.0-0.1.el7.x86_64
---> Package opendkim.x86_64 0:2.11.0-0.1.el7 will be installed
--> Processing Dependency: libmemcached.so.11()(64bit) for package: opendkim-2.11.0-0.1.el7.x86_64
--> Processing Dependency: libmemcachedutil.so.2()(64bit) for package: opendkim-2.11.0-0.1.el7.x86_64
--> Processing Dependency: libmilter.so.1.0()(64bit) for package: opendkim-2.11.0-0.1.el7.x86_64
--> Processing Dependency: libopendbx.so.1()(64bit) for package: opendkim-2.11.0-0.1.el7.x86_64
---> Package pypolicyd-spf.noarch 0:1.3.2-5.el7 will be installed
--> Processing Dependency: python-ipaddr for package: pypolicyd-spf-1.3.2-5.el7.noarch
--> Processing Dependency: python-pyspf for package: pypolicyd-spf-1.3.2-5.el7.noarch
--> Running transaction check
---> Package clamav-filesystem.noarch 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-update-0.99.2-8.el7.x86_64
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-data-0.99.2-8.el7.noarch
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-filesystem.noarch 0:0.101.5-10.el7 will be an update
---> Package clamav-lib.x86_64 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-lib.x86_64 0:0.101.5-10.el7 will be an update
--> Processing Dependency: libjson-c.so.2()(64bit) for package: clamav-lib-0.101.5-10.el7.x86_64
--> Processing Dependency: libpcre2-8.so.0()(64bit) for package: clamav-lib-0.101.5-10.el7.x86_64
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
---> Package libbsd.x86_64 0:0.8.3-1.el7 will be installed
---> Package libmemcached.x86_64 0:1.0.16-5.el7 will be installed
---> Package opendbx.x86_64 0:1.4.6-6.el7 will be installed
---> Package python-ipaddr.noarch 0:2.1.11-2.el7 will be installed
---> Package python-pyspf.noarch 0:2.0.11-5.el7 will be installed
--> Processing Dependency: python-pydns for package: python-pyspf-2.0.11-5.el7.noarch
---> Package sendmail-milter.x86_64 0:8.14.7-5.el7 will be installed
--> Running transaction check
---> Package clamav.x86_64 0:0.99.2-8.el7 will be updated
---> Package clamav.x86_64 0:0.101.5-10.el7 will be an update
---> Package clamav-data.noarch 0:0.99.2-8.el7 will be updated
---> Package clamav-data.noarch 0:0.101.5-10.el7 will be an update
---> Package clamav-filesystem.noarch 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-filesystem = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-lib.x86_64 0:0.99.2-8.el7 will be updated
--> Processing Dependency: clamav-lib = 0.99.2-8.el7 for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7()(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PRIVATE)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
--> Processing Dependency: libclamav.so.7(CLAMAV_PUBLIC)(64bit) for package: clamav-server-0.99.2-8.el7.x86_64
---> Package clamav-scanner-systemd.noarch 0:0.99.2-8.el7 will be obsoleted
--> Processing Dependency: init(clamav-scanner) for package: clamav-scanner-0.99.2-8.el7.noarch
---> Package clamav-update.x86_64 0:0.99.2-8.el7 will be updated
---> Package clamav-update.x86_64 0:0.101.5-10.el7 will be an update
---> Package json-c.x86_64 0:0.11-4.el7_0 will be installed
---> Package pcre2.x86_64 0:10.23-2.el7 will be installed
---> Package python-pydns.noarch 0:2.3.6-2.el7 will be installed
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
You have a troubles with yum. Fix it before install!And this:
Code: [Select]
Failed to restart opendkim.service: Unit not found.I did not check the box for CLAMAV.
55
Information / Alias questions
« on: February 27, 2020, 12:40:42 AM »
I have created an email@mydomain.com in root control panel. I then created an alias email@mydomain.com (same as my email) that forwards to someother@domain.com. Is this correct? If it is not, then this could be what caused my problems in my other post about virtual mailbox errors.
Its not very clear when using the control panel.
Its not very clear when using the control panel.
56
CentOS-WebPanel Bugs / Re: Mail forwarding problem update
« on: February 27, 2020, 12:22:21 AM »
Ok. I removed rosinto from server 1 and moved it to server #2 and created the same email account.
So I tried sending an email from server#2 2019@lakeservers.com (as before) to simhof@rosinto.com (now on server #2).
Result: success. But there still seems to be a problem with server #1. This is unquestionably tied to the alias/forwarding that I created. It was only after creating and deleting the alias that the sheet hit the fan. I suppose I could recreate the same scenario now on server #2 to see if I can show that it is the problem. But I have already f'ed up server 1. So I dont think I will do that. I will leave it to the developers.
Although I couldnt not send mail from server 2 to the one domain rosinto.com on server 1, gmail could, as well as form email from server 1, which further complicates the troubleshooting.
So I tried sending an email from server#2 2019@lakeservers.com (as before) to simhof@rosinto.com (now on server #2).
Result: success. But there still seems to be a problem with server #1. This is unquestionably tied to the alias/forwarding that I created. It was only after creating and deleting the alias that the sheet hit the fan. I suppose I could recreate the same scenario now on server #2 to see if I can show that it is the problem. But I have already f'ed up server 1. So I dont think I will do that. I will leave it to the developers.
Although I couldnt not send mail from server 2 to the one domain rosinto.com on server 1, gmail could, as well as form email from server 1, which further complicates the troubleshooting.
57
CentOS-WebPanel Bugs / Re: Mail forwarding problem
« on: February 26, 2020, 08:32:36 PM »
Error message above on failed email delivery cites 192.168.0.8. Thats my local ip. Can a development lamp on my desktop be behind this?
58
CentOS-WebPanel Bugs / Re: Mail forwarding problem
« on: February 26, 2020, 07:18:50 PM »
I am going to delete the domain and add it again. That will most likely fix it. But this all started after I created a forwarding rule and then deleted it. It has to be connected to the forwarding.
update. deleted and created new domain and still the same error message. Very puzzling.
update. deleted and created new domain and still the same error message. Very puzzling.
59
CentOS-WebPanel Bugs / Re: Mail forwarding problem
« on: February 26, 2020, 07:14:21 PM »
For the rosinto.com yes.
for lakeservers. com 45.33.10.132
for lakeservers. com 45.33.10.132
60
CentOS-WebPanel Bugs / Re: Mail forwarding problem
« on: February 26, 2020, 07:07:54 PM »Code: [Select]
eb 26 14:05:01 server postfix/smtpd[29003]: warning: hostname 71-214-155-80.orlf.qwest.net does not resolve to address 71.214.155.80: Name or service not known
Feb 26 14:05:01 server postfix/smtpd[29003]: connect from unknown[71.214.155.80]
Feb 26 14:05:02 server postfix/smtpd[29003]: Anonymous TLS connection established from unknown[71.214.155.80]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Feb 26 14:05:02 server postfix/smtpd[29003]: 7644818EDC: client=unknown[71.214.155.80], sasl_method=PLAIN, sasl_username=2019@lakeservers.com
Feb 26 14:05:02 server postfix/cleanup[29012]: 7644818EDC: message-id=<0c2894ec-b866-7410-5d85-08deeb3fbc34@lakeservers.com>
Feb 26 14:05:02 server postfix/qmgr[28937]: 7644818EDC: from=<2019@lakeservers.com>, size=729, nrcpt=1 (queue active)
Feb 26 14:05:02 server postfix/smtpd[29003]: disconnect from unknown[71.214.155.80] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8
Feb 26 14:05:02 server postfix/smtp[29014]: 7644818EDC: to=, relay=libra.goldspot.us[198.58.96.204]:25, delay=0.3, delays=0.19/0.01/0.06/0.03, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as D31CCAA89)
Feb 26 14:05:02 server postfix/qmgr[28937]: 7644818EDC: removed
The above code is a successful mail delivered from the same server but to a different domain on the same server as rosinto.com. Problem is only one domain email.......rosinto.com All others work.. It is not a problem of the sender, it is a problem of the receiver.
