The Plesk panel indicates that the Spam folder can be retrieved using an email client. We are using Outlook 2013 and can not figure out a way to make this happen. We can see the Spam folder using Webmail, but the contents never shows up in Outlook...
View 1 RepliesWhen I set up spamassassin to store spam in the spam folder of my mailbox, it doesn't add any X-Sapm headers nor tags the subject. All I found so far was an old thread where a plesk employee stated that it will be fixed in 'a' future version.
I am on 11.5.30 Update #47.
The problem is that all the mail that exits my VPS server (OVH) is going to the spam folders of Gmail, Outlook, etc accounts.
I've tried to connect my Gmail account to check via POP3 my inbox on my VPS, and all I get is an SSL error.
Mail in the spam folder is supposed to be deleted after 30 days.
I have some mail that has been in the Spam folder for 40 days. Why hasn't it been auto-deleted?
I have completed email set up on my server and have checked that email ports are open, but for some reason outlook keeps returning : "Outlook cannot find the server. Verify the server information is entered correctly in the Account Settings, and that you DNS settings in the Network pane of System Preferences are correct."
The odd thing is that outlook still picks up emails if I receive any, but keeps returning above error every minute.
In plesk9 my customers had the option to send daily usage reports by e-mail. Only certain clients like this option. Using plesk11 I cannot find this option if I log in as a client. Has this feature been removed? And if so, can the administrator enable this option only for 1 or 2 clients?
View 2 Replies View RelatedMicrosoft Windows Server 2008 R2 Service Pack 1
Panel version 11.0.9 Update #59, last updated at Oct 3, 2013 02:06 AM
MailEnable version 5
I see in the plesk documentation that the screen to enable SPAM filtering for an individual there is an option to "Move spam to the Spam folder". I don't see that option so I am wondering if it is only available on some versions of Plesk, or in combination with certain mail servers. How to make that option available?
Domain abc.com is hosted on our server, it has a hosted e-mail 123@abc.com. This e-mail adress keeps getting SPAM messages from an address abc@srv2.xyz.com (where srv2.xyz.com is our server FQDN). What we understood by reading the headers (posted below) is that someone is sending an e-mail to support@abc.com. This e-mail adress, as configured in Plesk, redirects e-mails to 123@abc.com. But we don't understand how someone managed to send an e-mail from an unexistent abc@srv2.xyz.com to it.
Here are the headers:
DomainKey-Status: no signature
Return-Path: <Coulter_Faustinoa1@aspli.com>
X-Original-To: 123@abc.com
[Code].....
I have a problem with my server. If you send any message to any gmail account, that message will only arrive in spam/bulk folder. I tried changing subjects, and no use any message that you send only goes to the bulk folder. Ip of the server is not blocked in any know database, I checked.
View 2 Replies View RelatedAlmost all mail adresses on my server is getting a spam mail from same mail marketing company everyday and i want to block them... Normally i just add the mail address to blacklist from "Spam Filter Settings" but this company is opening new addresses everyday and it is impossible to add all of them to blacklist so i need adding it as a regex to the blacklist...
The company i am talking about is opening mail addresses every day like below...
nrt150401@hotmail.com
nrt150402@gmail.com
nrt150403@yandex.com
nrt150404@mynet.com
As you can see all mail addresses begin with "nrt"+"6 digits of day"+"free mail provider", so right now i am using the regex below and it is already added to the blacklist but they are still able to send me... What can i do now?
Initially I was able to connect via FTP. Then all of a sudden I started getting 550 SSL/TLS required on the control channel. Why did it suddenly required SSL/TLS when I did not do anything extra?
Now when I'm trying to connect via FTPES using FileZilla (tried both active and passive) on Linux Mint Debian, I'm getting the error below. I'm really stumped. I have tried to Allow incoming from all on port 49152-65534/tcp via Plesk firewall, but still no go.
The worst thing now is, I can't even get FTP to work anymore. Of course I would prefer to have TLS working.
Status:Connection established, waiting for welcome message...
Response:220 ProFTPD 1.3.5 Server (ProFTPD) [206.106.213.243]
Command:AUTH TLS
[Code]....
I enabled plesk firewall to my ip now I cant seem retrieve directory listing. I've done the same with ssh that works fine.
Response:230 User logged in
Command:OPTS UTF8 ON
Response:200 UTF8 set to on
Status:Connected
Status:Retrieving directory listing...
Command:PWD
Response:257 "/" is the current directory
Command:TYPE I
Response:200 Type set to I
Command:PASV
Response:227 Entering Passive Mode
Command:MLSD
Error:Connection timed out
Error:Failed to retrieve directory listing
I have a problem with Parallels Plesk 12 Web Host Edition. In the dashboard, Plesk tells me that Spamassassin service is not running and not installed.
How to setting up it ? Is there a component, a service to buy, or do i have to configure it through SSH ?
We are using Plesk 11.5 with postfix MTA. Spamassassin is working fine for incoming mails and leaves outbound mails unchecked - as it should.
Now there is one of my domains whose mails are relayed to another server (using postfix transport tab; mail support for this domain is disabled in plesk). For the moment, these mails arrive without beeing checked and marked by spamassassin. How could I change this? I have tried to register an additional mail-handler like
Code:
/usr/local/psa/admin/sbin/mail_handlers_control --add --priority=10 --executable=/usr/local/psa/handlers/hooks/spam --name=spam --enabled --queue=before-remote --mailname=relaydomain.de --type=recipient-domain --dont-preserve-on-restore --context=text
but this didn't have any effect so far.
If there is a direct way to enable spam-control for relay domains, Otherwise I could still access spamassassin via postfix' config-files, but how to use two different implementation of spamassassin at the same time.
The SpamAssassin bayes database has become ineffective on one of our servers and we want to wipe it and start fresh - how to do this on Plesk 11.5.30?
View 1 Replies View RelatedWhat steps can we take to improve SpamAssassin performance? I know this was talked about in older Plesk versions, but we may be able to do more now. What configurations can I do to stop more spam?
View 1 Replies View RelatedIt seems that SA is not using bayes on the incoming messages. How to get bayes to work?
I have trained with plenty of ham and spam. Where are the db files for global bayes located?
I am running Plesk 11.5.30 Update #44, Postfix 2.8.14 and Spamassassin 3.3.1 on a Red Hat Enterprise Linux Server 6.5 server. I am looking to update the rules within Spamassassin. I have had a bit of a look and see that a crontab has been created but its a bash script with a comment saying it has been disabled by psa-spamassassin package (/etc/cron.d/sa-update).
Code:
#!/bin/sh
# This task was disabled by psa-spamassassin package
exit 0
Is there a reason why it has been disabled by Plesk? If I update the rules, will it break something?
I have recently added into Postfix RBLs to reduce the amount of SPAM my customers is getting and this is my next step in a list of things that I would like to change.
I noticed that my spamassassin wasn't running on my server. so I restarted the service from the plesk panel but got the following message:
Error: Unable to make action: Unable to manage service by spammng: spamassassin: unrecognized service
ERROR:spammng:Unable to start SpamAssassin service
('--start', 'spamassassin')
So I SSH'ed into my machine and saw that spamassassin wasn't running.
The I reinstalled spamassassin from the "add and remove product components", but that didn't change anything. Still the same error.
Installing Plesk Panel with Spamassassin on Ubuntu 14.04 LTS gives a significant error:
Restarting SpamAssassin Mail Filter Daemon: No /usr/bin/perl found running; none killed.
server socket setup failed, retry 1: spamd: could not create IO::Socket::INET6 socket on [::1]:783: Cannot assign requested address
server socket setup failed, retry 2: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 9: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use
spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use
invoke-rc.d: initscript spamassassin, action "restart" failed.
dpkg: error processing package sa-compile (--configure):
even though spamassassin (i.e. spamd) is not running. The usual suspects for the before mentioned error, being
a) differences in the name of the PIDFILE variable in /etc/default/spamassassin and /etc/init.d/spamassassin
b) directory and/or file location are not readable/writable
are not causing this specific installation bug. The work-arounds:
1 - not installing spamassassin (not an option)
2 - installing spamassassin and (afterwards)
change /etc/default/spamassassin, add the option "-4" to the line OPTIONS, resulting in the line: OPTIONS="--nouser-config -4 --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=5"
run plesk-installer or autoinstaller again ..Work-around 2 works fine, after reinstallation the /etc/default/spamassassin is as it should be (note that the added "-4" is not present anymore).
The before mentioned work-around suggests some error in the installation process, very likely to be an issue with the chronological order of installation of the various components. In theory, it can be excluded that this bug/issue is caused by psa-spamassassin and/or spamassassin (version 3.3.x) packages, even though some current spamassassin bugs are known: URL....I sincerely hope that Parallels Team can investigate and patch both of the bugs/issues.
I just migrated a bunch of domains from plesk 11.5. Everything appears to be working well however when examining the maillog, I am seeing some strange errors... In this example, the message was delivered and had the spamassassin stuff in the header.
spamd: handle_user unable to find user: 'jason@xxxxxxp.com'
I have one specific domain being to another SMTP server via Postfix transport_maps.
This works great, apart from Spam check not working anymore, Spamassassin is not being called for the domain.
Is there any configuration to have Spamassassin check email before it is routed via transport_maps?
I'm suffer 2 major problem as below :
1.
how to turn off spamassassin completely ?
I've already stop the spamassassin service on Services Management but it's only valid one day. The next day, spam assassin service automatically start
2.
my customer mailbox statistic wrong. Even if their mailbox not full but when they send email. The quota said that their mailbox full. So they can't send/receive email.
Our action :
Manually, use command
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php -f execute-statistics
When I create Mailbox for customer, spamassassin have status (default):
HTML:
Status false
The score that a message must
receive to qualify as spam
What to do with spam mail move
Add the following text to the true
beginning of subject of each
message recognized as spam
Modify spam mail subject text ***SPAM***
Black list
================================
Server-wide black list:
User's black list:
White list
================================
Server-wide white list:
User's white list:
But i want it:
HTML:
Status false
The score that a message must 7
receive to qualify as spam
What to do with spam mail text
Add the following text to the true
beginning of subject of each
message recognized as spam
Modify spam mail subject text ***SPAM***
Black list
================================
Server-wide black list:
User's black list:
White list
================================
Server-wide white list:
User's white list:
Not Move, it only text at "What to do with spam mail text"
How i can do it ?
The FTP on my VPs running centos 6.6 and plesk 12.0.18 Update #44 has stopped allowing FTP conections via filezilla or dreamweaver. My tech knowledge with server management outside of the gui is minimal but i have done the following. Checked that the firwall is allowing ftp traffic through the GUI in plesk.
restarted xinetd and checked status
[root@367549 ~]# service xinetd status
xinetd (pid 11707) is running...
[root@367549 ~]# lsof -i tcp:21
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
xinetd 11707 root 5u IPv6 682472 0t0 TCP *:ftp (LISTEN)
Then tried the following
[root@367549 ~]# ftp localhost
-bash: ftp: command not found
But i can connect via telnet on port 21
when trying to use +dreamweaver or filezilla i get the following. This may be due to one or more of the following reasons: - The network cable is unplugged or the network is down. Please verify that the network cable is connected and that the network is up. - The FTP server is down. Please verify that you can connect to the FTP server using another FTP program. - The FTP host name is incorrect. Please verify that the host name is correct in the Site definition dialog box. - Accessing the server requires proxy settings that aren't properly set. Please verify that the proxy settings in the Site category of the Preferences dialog box are properly set, and that the Use Proxy option in the Site definition dialog box is selected. - You may need to connect to the server using a different port than the one provided. Please specify the correct port in the box provided.
Error: The data connection could not be established: ETIMEDOUT - Connection attempt timed out
Error: Connection timed out after 20 seconds of inactivity
Error: Failed to retrieve directory listin.
What to do and why after no change this just stopped working when ive been using ftp on this server previous.. the company that i brought the vps from have no intrest and tell me its unmanaged.