(host mx.smknitwear.com.cust.a.hostedemail.com[216.40.42.4] refused to talk to me: 554 5.7.1 Service unavailable; Client host [xx.xxx.xxx.xx] blocked using urbl.hostedemail.com;
Check your IP at https://lookup.abusix.com/
Sign up free
Request delist
by dev
(host mx.smknitwear.com.cust.a.hostedemail.com[216.40.42.4] refused to talk to me: 554 5.7.1 Service unavailable; Client host [xx.xxx.xxx.xx] blocked using urbl.hostedemail.com;
Check your IP at https://lookup.abusix.com/
Sign up free
Request delist
by dev
store/, cache/, files/ and images/avatars/upload/.MAKE SURE you read Security related post-installation instructions, and also take note regarding anti-spam measures.
Once you have successfully installed phpBB you MUST ensure you remove the entire install/ directory.
Beyond this essential deletion, you may also wish to delete the docs/ directory if you wish.
With these directories deleted, you should proceed to the administration panel. Depending on how the installation completed, you may have been directed there automatically. If not, login as the administrator you specified during install/conversion and click the Administration Control Panel link at the bottom of any page. Ensure that details specified on the General tab are correct!
phpBB supports several methods for allowing users to select their own avatar (an avatar is a small image generally unique to a user and displayed just below their username in posts).
Two of these options allow users to upload an avatar from their machine or a remote location (via a URL). If you wish to enable this function you should first ensure the correct path for uploadable avatars is set in
Administration Control Panel -> General -> Board Configuration -> Avatar settings. By default this is images/avatars/uploads, but you can set it to whatever you like, just ensure the configuration setting is updated. You must also ensure this directory can be written to by the webserver. Usually this means you have to alter its permissions to allow anyone to read and write to it.
Please be aware that setting a directory’s permissions to global write access is a potential security issue. While it is unlikely that anything nasty will occur (such as all the avatars being deleted) there are always people out there to cause trouble. Therefore you should monitor this directory and if possible make regular backups.
Depending on your web server, you may have to configure your server to deny web access to the cache/, files/, includes, phpbb, store/, and vendor directories. This is to prevent users from accessing sensitive files.
For Apache there are .htaccess files already in place to do this for the most sensitive files and folders. We do however recommend to completely deny all access to the aforementioned folders and their respective subfolders in your Apache configuration.
On Apache 2.4, denying access to the phpbb folder in a phpBB instance located at /var/www/html/ would be accomplished by adding the following access rules to the Apache configuration file (typically apache.conf):
<Directory /var/www/html/phpbb/*> Require all denied </Directory> <Directory /var/www/html/phpbb> Require all denied </Directory>
The same settings can be applied to the other mentioned directories by replacing phpbb by the respective directory name. Please note that there are differences in syntax between Apache version 2.2 and 2.4.
For Windows based servers using IIS there are web.config files already in place to do this for you. For other webservers, you will have to adjust the configuration yourself. Sample files for nginx and lighttpd to help you get started may be found in the docs/ directory.
Like any online site that allows user input, your board could be subject to unwanted posts; often referred to as forum spam. The vast majority of these attacks will be from automated computer programs known as spambots. The attacks, generally, are not personal as the spammers are just trying to find accessible targets. phpBB has a number of anti-spam measures built in, including a range of CAPTCHAs. However, administrators are strongly urged to read and follow the advice for Preventing Spam in phpBB as soon as possible after completing the installation of your board.
by dev
Solution: Check whether the dot files are hidden. Make the dot files to show.
Horde
Roundcube
Windows Mail
Thunderbird
Microsoft Outlook Express
by dev
Generally, the size of the swap file depends on how much RAM your system has:
Only root or user with sudo privileges can activate the swap file.
1). First, create a file that will be used as swap:
sudo fallocate -l 2G /swapfile
2). Set the file permissions to 600 to prevent regular users to write and read the file:
sudo chmod 600 /swapfile
3. Create a Linux swap area on the file:
sudo mkswap /swapfile
4). Activate the swap file by running the following command:
sudo swapon /swapfile
5). To make the change permanent open the /etc/fstab file:
sudo vi /etc/fstab
and paste the following line:
/swapfile swap swap defaults 0 0
6). Verify that the swap is active by using either the swapon or the free command, as shown below:
sudo swapon --show
and
sudo free -h
Adjusting the Swappiness Value
On Ubuntu, the default swappiness value is set to 60. You can check the current value by typing the following command:
cat /proc/sys/vm/swappiness
While the swappiness value of 60 is OK for most Linux systems, for production servers, you may need to set a lower value.
sudo sysctl vm.swappiness=10
To make this parameter persistent across reboots, append the following line to the /etc/sysctl.conf file:
vm.swappiness=10
Removing a Swap File
To deactivate and delete the swap file, follow these steps:
1). First, deactivate the swap space:
sudo swapoff -v /swapfile
2). Next, remove the swap file entry from the /etc/fstab file.
/swapfile swap swap defaults 0 0
3). Finally, remove the actual swapfile file using the rm command:
sudo rm /swapfile
by dev
Solution
Go into the sshd_config file
vi /etc/ssh/sshd_config
Search and remove the # sign at the beginning of the 3 lines
X11Forwarding yes X11DisplayOffset 10 X11UseLocalhost yes
Then restart sshd
systemctl restart sshd
Exit and login again. You will not get the error.
Or
Create n new file: touch ~/.Xauthority
Log out and login in again.