Search the Community

αν δεν σας αρεσει η μουσική κλείστε τον ηχο

by Arunlal Ashok · May 24, 2015 Is it possible? A back-end option to enable SPF and DKIM for already created cPanel accounts? In cPanel, backend scripts are available to enable SPF and DKIM for all accounts that are already created without enabling email authentications, SPF and DKIM. We have already discussed “How to enable SPF and DKIM automatically for all newly creating accounts?“. That’s simple, right! Enabling this features in the DNS will increase the reputation of all emails sent out from that account (domain). SPF stands for “Sender Policy Framework”, it’s a TXT record to the domain DNS. DKIM stands for “Domain Keys Identified Mail”, DKIM is an authentication protocol that is used by email receivers to determine original ownership of that email. In a DKIM enabled domain, an encrypted digital signature will add to all emails sent out from that domain which will help to identify the originality of that email. cPanel script to enable SPF via commandline: Syntax # /usr/local/cpanel/bin/spf_installer $username Where, $username is the cPanel user name. cPanel script to enable DKIM via commandline: Syntax # /usr/local/cpanel/bin/dkim_keys_install $username Replace $username with the actual cPanel username. The above commands will help you to enable email authentications for single cPanel users. If you have hundreds of accounts and you want to enable SPF and DKIM for all accounts, please follow the simple for loop. Here we can get the cPanel usernames from “/var/cpanel/users”. Then give that to installations scripts. Please see the sample script below: Script for username in `ls -A /var/cpanel/users` ; do /usr/local/cpanel/bin/dkim_keys_install $username && /usr/local/cpanel/bin/spf_installer $username ; done That’s it! wait for a while, it’ll set all. https://crybit.com/enabling-email-authentication/

Σημερα ειχα ενα θεμα με WebMail όπου όλα τα αρχεία είχαν σωστά perms / ownership αλλά σε WebMail ο χρηστης δεν εβλεπε πια τα email του παρά μονο: "mail server closed the connection unexpectedly" Το περίεργο αλλά και θετικό ήταν πως δεν είχε σχέση με την IP ανα session, ούτε με άλλο email account ακόμη και στο ίδιο Package ( σε addon domain ) Παντα μιλάμε για cPanel box Την λύση την έδωσαν οι ίδιοι με ενα απο τα δικά τους scripts /scripts/remove_dovecot_index_files --user {user} --verbose ενδιαφερον fix [*] (1/1) Processing cPanel user: '{user}' … Unlinking '/home/{user}/mail/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/dovecot.index.log.2' … Unlinking '/home/{user}/mail/{domain}/{user}/dovecot.index.cache' … Unlinking '/home/{user}/mail/{domain}/{user}/dovecot.index' … Unlinking '/home/{user}/mail/{domain}/{user}/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.Sent/dovecot.index.cache' … Unlinking '/home/{user}/mail/{domain}/{user}/.Sent/dovecot.index' … Unlinking '/home/{user}/mail/{domain}/{user}/.Sent/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.Drafts/dovecot.index.cache' … Unlinking '/home/{user}/mail/{domain}/{user}/.Drafts/dovecot.index' … Unlinking '/home/{user}/mail/{domain}/{user}/.Drafts/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.Trash/dovecot.index.cache' … Unlinking '/home/{user}/mail/{domain}/{user}/.Trash/dovecot.index' … Unlinking '/home/{user}/mail/{domain}/{user}/.Trash/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.spam/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.Junk/dovecot.index.log' … Unlinking '/home/{user}/mail/{domain}/{user}/.Archive/dovecot.index.log' … [+] '{user}' processed. To script το βρηκα και εδω http://www.batangrande.com/fotos/sym/root/scripts/remove_dovecot_index_files #!/usr/local/cpanel/3rdparty/bin/perl # cpanel - scripts/remove_dovecot_index_files # Copyright 2015 cPanel, Inc. # All rights Reserved. # copyright@cpanel.net http://cpanel.net # This code is subject to the cPanel license. Unauthorized copying is prohibited package scripts::remove_dovecot_index_files; use strict; use File::Find (); use File::Spec (); use Getopt::Long (); use Cpanel::Config::LoadCpConf (); use Cpanel::PwCache (); use Cpanel::Reseller (); use Cpanel::Config::Users (); use Cpanel::Config::LoadUserOwners (); use Cpanel::AccessIds::ReducedPrivileges (); exit run(@ARGV) unless caller(); my $verbose = 0; sub run { my @cmdline_args = @_; return usage(1) if !@cmdline_args; unless ( $> == 0 && $< == 0 ) { return usage( 1, "[!] This program can only be run by root!\n" ); } my $opts = {}; Getopt::Long::GetOptionsFromArray( \@cmdline_args, 'all' => \$opts->{'all'}, 'reseller=s@' => \$opts->{'reseller'}, 'user=s@' => \$opts->{'user'}, 'verbose' => \$verbose, 'help|h' => \$opts->{'help'}, ); return usage(0) if $opts->{'help'}; my $cpconf_ref = Cpanel::Config::LoadCpConf::loadcpconf(); if ( $cpconf_ref->{'mailserver'} ne 'dovecot' ) { return usage( 1, "[!] The configured mailserver is not Dovecot. Action aborted.\n" ); } return process_all_users_on_server() if $opts->{'all'}; process_reseller( $opts->{'reseller'} ) if $opts->{'reseller'} && scalar @{ $opts->{'reseller'} }; process_cpanel_user( $opts->{'user'} ) if $opts->{'user'} && scalar @{ $opts->{'user'} }; return 0; } sub process_cpanel_user { my $cpusers_to_process = shift; my ( $index, $total ) = ( 1, scalar @{$cpusers_to_process} ); foreach my $cpuser ( @{$cpusers_to_process} ) { print "[*] ($index/$total) Processing cPanel user: '$cpuser' …\n"; $index++; my $homedir = Cpanel::PwCache::gethomedir($cpuser); my $maildir = File::Spec->catfile( $homedir, 'mail' ); if ( !-d $maildir ) { print "[!] User's maildir was not found: $maildir - $!\n"; next; } my $maxdepth = File::Spec->splitdir($maildir) + 4; my $purge_index_files_codref = sub { File::Find::find( { 'wanted' => sub { # Dovecot index files are in "$homedir/mail/domain.tld/emailuser/<dirname>". # So we limit the depth here to what was determined above. return if File::Spec->splitdir($File::Find::name) > $maxdepth; # Remove files that match: # dovecot.index # dovecot.index.cache # dovecot.index.log # dovecot.index.log.\d+ (rotated log files) return if $_ !~ m/^dovecot\.index(\.cache|\.log(\.\d+)?)?$/; print "Unlinking '$File::Find::name' …\n" if $verbose; if ( -e $File::Find::name && -f $File::Find::name ) { unlink $File::Find::name or print "Failed to unlink '$File::Find::name': $!\n"; } }, 'no_chdir' => 0, # default, but setting to be explicit about the usage. 'follow_skip' => 2, # ignore any duplicate files and directories }, $maildir ); }; eval { Cpanel::AccessIds::ReducedPrivileges::call_as_user( $purge_index_files_codref, $cpuser ) }; print "[+] '$cpuser' processed.\n"; } return; } sub process_reseller { my $resellers_to_process = shift; foreach my $reseller ( @{$resellers_to_process} ) { print "[*] Processing Reseller: '$reseller' …\n"; if ( !Cpanel::Reseller::isreseller($reseller) ) { print "[!] '$reseller' is not reseller.\n\n"; next; } my $owners_hr = Cpanel::Config::LoadUserOwners::loadtrueuserowners( {} ); if ( !( $owners_hr->{$reseller} && 'ARRAY' eq ref $owners_hr->{$reseller} ) ) { print "[!] Failed to fetch list of accounts owned by reseller, '$reseller'.\n\n"; return; } print "\n"; process_cpanel_user( $owners_hr->{$reseller} ); print "\n"; } return; } sub process_all_users_on_server { my $cpusers = Cpanel::Config::Users::getcpusers(); if ( !( $cpusers && 'ARRAY' eq ref $cpusers ) ) { print "[!] Failed to fetch list of cPanel accounts on server.\n"; return; } print "[*] Processing all cPanel users on the server …\n\n"; process_cpanel_user($cpusers); print "\n[+] Finished processing all cPanel users on the server.\n"; return 0; } sub usage { my ( $retval, $msg ) = @_; my $fh = $retval ? \*STDERR : \*STDOUT; if ( !defined $msg ) { $msg = <<USAGE; $0 Utility to remove Dovecot index files. Available options: --user [cPanel username] Remove Dovecot index files from all email accounts setup under the specified cPanel user. Can be specified more than once, to process multiple users at once. --reseller [reseller username] Remove Dovecot index files from all email accounts setup under all the cPanel accounts owned by the specified Reseller. Can be specified more than once, to process multiple resellers at once. --all Remove Dovecot index files from all email accounts setup on the server. --verbose Prints the full paths of the files being removed. --help Prints this help text. USAGE } print {$fh} $msg; return $retval; } 1;

This video walks you through the SSL TLS Wizard to obtain a certificate for an arrangement of addon, subdomains, and parked/aliased domains. Music by bensound.com We filmed this tutorial with cPanel & WHM version 60 and the Paper Lantern theme, so the interface and features may differ from the current version. We'll produce newer tutorials as the feature evolves and improves. You can find documentation about the main cPanel interface at https://documentation.cpanel.net/disp... Please let us know if there are additional features or procedures that you would like for us to demonstrate with a walkthrough in video format.

benny Vasquez / Apr 21st, 2016 / Products March 31st, 2017: The Day the Sun Sets on CentOS 5 CentOS 5 will reach end of life officially on March 31st of 2017, but as an industry we are already feeling the pain of people still using the out of date OS. Trying to support a system on an aging Operating System is not that far from trying to live in an aging apartment building. Ill-fitting fixtures, flickering electricity, and malfunctioning plumbing are just some of the daily struggles in those old buildings. Similarly, when the basic requirements of modern hosting are a struggle to maintain it has a severe and direct impact on every webhost’s quality of life. cPanel & WHM version 56 (in the CURRENT tier as of April 11th, 2016, with an expected End of Life of May of 2017) will be the last version of cPanel to support CentOS 5, and 32bit Architecture. We have considered this heavily, and have decided to drop support for those things for two primary reasons: As a software provider, the opportunity cost of continuing to support the oldest infrastructure is too high, and it severely limits the amount of new things we can deliver to our users. As an industry, cPanel believes making it easier for people to continue to host on old, insecure, out of date software ultimately hurts us all. Deprecating support for older systems and older software is necessary for the over-all health of the hosting industry. cPanel is keeping its eye on the future, and letting the old software go. But we know how hard it traditionally is to migrate from an old server to a new one. To help with that we developed the Server Configuration addition to the transfer tool. The Server Configuration Additions to the Transfer Tool In version 11.44 we introduced the Transfer Tool, and it has proved a reliable tool to migrate accounts and packages between servers. As of v56 you can use it to transfer server configurations between servers as well. Note: This is intended to be used to transfer configurations from an existing v56 server to a new server. No attempt is made to back up configurations on the destination server. Additionally, this tool is not intended to be used to migrate configurations from compromised servers. If you’re familiar with the transfer tool, you will find that the additions we’ve made are incredibly simple to use. Once you authenticate to the origin server, you’ll see an expandable section called “Service Configurations”. Click the ‘Show’ button: Choose the configurations you want to transfer, and go through the Transfer Tool like you normally would: The configurations are moved to the new server, any relevant services are restarted, and you’re all set! The same team that built this interface also expanded the functionality of the cpconftool, to help you complete a similar migration on the command line. The cpconftool a command line utility that operates in a very similar way to pkgacct. You can read more about it on our documentation site. You can find the full documentation about the additions to the Transfer Tool in the Transfer Tool Documentation for v56. Note: Due to the potential complications involved, currently MySQL is not included in the WHM Transfer Tool interface. You can still copy your MySQL configuration using the command line tool cpconftool, you can still back up and manually copy your MySQL configuration v56 will be the last version of cPanel to support CentOS 5, the last version to support 32bit architecture. Just in case it wasn’t obvious yet, we want you to upgrade, to migrate, and to keep using and providing new and better software. If you still have any hesitation about the Transfer Tool’s additions, I’d love to hear about it! Email me or tweet me, and let me know! https://blog.cpanel.com/end-of-life-for-centos5/

Apache by default logs data directly to log files. While this isn’t a bad thing, it is not your only option. Both Apache 1.x and Apache 2.x bring with them the option of enabling something called “Piped Logging”, though cPanel will only allow you to enable it for version 2.x. Piped logging is extremely powerful when used correctly, and has far more flexibility than what we are using here. The way it is described here, we will be attempting to negate the memory hungry apache processes that creep up when a server is hosting very low traffic websites (less than 1 request per second) with traditional Apache log configurations. The symptom: Apache processes using a lot of memory. You will see Apache using a large percent of the memory (MEM) when running a ‘top’, such as what you see below (when sorted by memory use) and you’ll also note that the root Apache process has been running for a long time: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15733 root 15 0 554m 541m 5752 S 0.0 52.9 851:59.84 httpd 17790 www 15 0 556m 544m 5408 S 0.0 53.1 0:02.77 httpd 17616 www 16 0 555m 543m 5440 S 0.0 53.1 0:04.69 httpd 18368 www 15 0 555m 543m 5396 S 0.0 53.1 0:01.05 httpd 29924 www 16 0 555m 543m 5548 S 0.0 53.1 0:08.91 httpd 18363 www 15 0 555m 542m 5352 S 0.0 53.0 0:00.55 httpd 22294 www 15 0 554m 542m 5376 S 3.9 53.0 0:00.27 httpd 22093 www 15 0 555m 541m 4556 S 0.0 52.9 0:00.33 httpd 22232 www 15 0 554m 541m 4552 S 0.0 52.9 0:00.27 httpd To see if traditional logging is enabled, check your Apache error log for messages that show Apache being restarted around every 2 hours: [host - root]: grep Graceful /usr/local/apache/logs/error_log You will see something like this: [Mon May 31 14:29:55 2010] [notice] Graceful restart requested, doing restart [Mon May 31 16:43:37 2010] [notice] Graceful restart requested, doing restart [Mon May 31 18:57:19 2010] [notice] Graceful restart requested, doing restart [Mon May 31 21:11:02 2010] [notice] Graceful restart requested, doing restart The Fix! Enter Piped logging. Enabling piped logging in this way has a few different effects, but the one we are primarily concerned with is preventing Apache from initiating that graceful restart request every two hours. WARNING: By following these directions your Apache configuration is rebuilt from the existing cPanel templates (the last distilled configuration), so you will lose anything that was not added or configured through cPanel/WHM. The directions below explain how to make a backup of the configuration before rebuilding it. Pre-implementation: Note: You will need to have root access to the server in order to implement piped logging. Software Requirements: Cpanel Version: 11.25.0-R43471 or later Apache Version 2 or later You can check your versions with the following commands: cPanel: [host - root]: cat /usr/local/cpanel/version For Apache: [host - root]: /usr/local/apache/bin/httpd -v Implementation There are two possible ways to implement this fix, one is via the command line, the other is through the WHM. Method 1: All Command Line Make a backup of the Apache config: [host:root]: cp /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.prepipedlogging Edit /var/cpanel/cpanel.config: [host:root]: vi /var/cpanel/cpanel.config Add the following enable_piped_logs=1 Make cPanel aware of the change: [host:root]: /usr/local/cpanel/whostmgr/bin/whostmgr2 --updatetweaksettings Rebuild the Apache config: [host:root]: /scripts/rebuildhttpdconf Stop and Start Apache: /etc/init.d/httpd stop /etc/init.d/httpd start Method 2: Allow cPanel/WHM to do the hard parts Make a backup of the Apache config: [host:root]: cp /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.prepipedlogging Log into WHM, and follow this sequence to the right place: Service Configuration >> Apache Configuration >> Piped Log Configuration Enable piped Apache logging, save it and let it rebuild the configuration. Finishing up After making any changes that involve your Apache configuration it is a very good idea to test all your hosted sites to make sure they still work. If it’s not practical to check all of your sites check as many different sites as you can. You should see a difference in your memory use and your service stability nearly immediately, and it should be long term.

Class is in Session: The New cPanel University Thousands of corporations and companies, and even more individuals, use the suite of tools loaded inside of cPanel & WHM to power their business and manage their online presence. From mail and spam filtering, to database storage and security, to simply just launching a website, cPanel and WHM offers a wealth of technical offerings. That being said, we’ve heard from our customers for years that they’d like a resource; a place where they can get comprehensive training on how to use cPanel and/ or WebHost Manager. After 14 months of testing, item analysis, and curriculum building, we’re happy to announce that the resource you’ve been asking for now exists. Welcome to cPanel University. Modeled after traditional online training programs, cPanel University marries reading material, benchmark quizzing, and even a final cumulative exam to ensure that students are not only learning the ins and outs of the tool but also that their completion of the program comes with the tangible pedigree of becoming a certified cPanel & WHM pro. (You can even add it to your LinkedIn profile!) The wizards on our technical training team have put countless hours into this program, carefully assessing the most popular tools and features, the most common types of issues, and ultimately, the most sought after technical knowledge that our customers and clients needed at their fingertips. The result is a program that allows anyone with access to the internet the chance to dive into four different course tracks that build into becoming a licensed cPanel professional. With databases (MySQL), DNS, Mail, and the web comprising our core training module, the team has packaged the perfect benchmarks for new enrollees and are already at work on additional enrichment modules for students who have already graduated. If you don’t currently have a cPanel & WHM certification, head over to cPanel University and start working on getting yours today. And don’t worry, for those of you who have already been certified, your certificate is still valid through its indicated expiration date. Let us know what you think about the brand new cPanel University or email professor@cpanel.net if you have ideas on future courses you’d like to see cPanel University offering. Be sure to stay tuned on future announcements as we continue to add courses, training modules, and learning opportunities to this exciting new cPanel offering. Course Goals Databases in WHM • Demonstrate competency utilizing the database management screens in WHM • Showcase ways to backup and restore databases • Define the major terms in relational database structure • Explain common causes of database corruption and ways to handle it DNS in WHM • Demonstrate knowledge of the benefits and limitations of MyDNS and BIND • Showcase knowledge on managing DNS from WHM • Illustrate knowledge of cPanel DNS clustering Mail in WHM • Demonstrate ways to set up mail system preferences • Explain how to use the Exim configuration manager • Identify and explain solutions for common delivery issues EasyApache 4 in WHM (Web) • Explain EasyApache 4 and how to use it • Demonstrate competency on configuring PHP https://university.cpanel.net/

Free SSL certificates Since the latest release of cPanel and WHM 58.0.x, a new AutoSSl feature is available. AutoSSL auto provisions domain validated Comodo SSL certificates. If your website (whether it is a domain, sub-domain, add-on domain or alias) never had a SSL certificate or it has expired, a new (and most importantly FREE) SSL certificate will be generated and installed. This makes any of your websites hosted in any of our cPanel hosting plans having free SSL certificate for life (with automated renewals).