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?
The VPS has 16 domains running on it, all with different web addresses and their own email accounts etc.
It's a Linux server and is running postfix for the mail. The main website on this domain has the mail service disabled because we have an exchange service on our own server here in the building where we work. Now when anyone on any of our domains on the VPS try to email us at 'maincompany.com' they get the following error message:
This is the mail system at host <vps address>.
Your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
<stevew@maincompany.com>: mail for maincompany.com loops back to myself...
I run a virtual server (Ubuntu 12.04, Plesk 12, Postfix 2.9.6) using plesk to manage multiple domains. The server address is server.domain1.com. I use plesk to also manage domain1.com regarding all services, including DNS and mail.
What I just found is that postfix sometimes issues the following warning:
server postfix/trivial-rewrite[7397]: warning: do not list domain server.domain1.com in BOTH mydestination and virtual_alias_domains
The essential part of my main.cf is:
myhostname = server.domain1.com
mydestination = localhost.$mydomain, localhost.localdomain, localhost
virtual_mailbox_domains = $virtual_mailbox_maps, hash:/var/spool/postfix/plesk/virtual_domains
virtual_alias_maps = $virtual_maps, hash:/var/spool/postfix/plesk/virtual
virtual_mailbox_maps = , hash:/var/spool/postfix/plesk/vmailbox
virtual_transport = plesk_virtual
And /var/spool/postfix/plesk/virtual_domains contains amongst others:
domain1.com domain1.com/
I do not have any issues with receiving or sending e-mails right now, but would like to get rid of the error message however.
Could it be the problem that postfix automatically sets mydomain to $myhostname with skipping the first part (i.e., mydomain is implicitly set to domain1.com)? Should I manually set mydomain to server.domain1.com instead? Any other recommendations? Since mydomain seems to be used in multiple options [URL] ..., I wonder what I might destroy with changing this? As all mail services run without any further troubles at the moment, I don't want to break this...
As I assume that quite some people use a plesk-based server to manage the domain to which the server itself belongs to, I would assume that there should be a general fix/check to updated mydomain accordingly?
My issue started ince a couple of months seemed to increase with update to Plesk 12.0 (though I can't guarantee it).I am using Centos 6.5, all updated. What happens is that postfix usage starts to increase without any apparent reason (during week-ends for example). Then postfix is not responding anymore.
Code:
top - 13:27:13 up 3 days, 18:44, 0 users, load average: 0.73, 0.33, 0.32
Tasks: 238 total, 2 running, 236 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3%us, 0.6%sy, 0.1%ni, 98.7%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 32917292k total, 8982212k used, 23935080k free, 1899416k buffers
Swap: 1046520k total, 0k used, 1046520k free, 4905884k cached
[code]....
I want to backup my server, but i get always error, when i want to save my Personal FTP Repository. I get following error:
Transport error: unable to list directory: Curl error: FTP: weird server reply
What is the reason?
Can't restore.
plesk Internal error: Failed to exec pmm-ras: (array ( 'code' => 127, 'stdout' => 'Transport error: File '_info_1503031904.xml' not found ', 'stderr' => '', )).
in debug mode:
Internal error: Failed to exec pmm-ras: [2015-03-05 16:19:49.215|23284] INFO: pmm-ras started :
/usr/local/psa/admin/bin/pmm-ras --get-dump-info --dump-file-specification=_info_1503031904.xml
--session-path=/var/log/plesk/PMM/logs --debug [2015-03-05 16:19:49.215|23284]
INFO: Repository '/var/lib/psa/dumps': Initializing...
[Code] .....
I have tried this on Plesk 11.5 and Plesk 12.0.10 Preview running on Ubuntu 12.04.4 LTS...
Locate the file
/etc/sw-cp-server/conf.d/plesk.confClick to expand...
Hopefully I'm posting this in the correct area. Our server runs CentOS 4.4 on x86_64 arch.
So basically everything was going rather smoothly...
Problems began to arise at the point where I finished installing/configuring SquirrelMail. Upon logging in, I saw this:
[see attachment]
Ok, so I checked maillog and saw:
Feb 11 13:50:46 zeus imapd: LOGIN, user=alex, ip=[::ffff:127.0.0.1], protocol=IMAP
Feb 11 13:50:47 zeus imapd: Failed to connect to socket /tmp/fam--
Feb 11 13:50:47 zeus imapd: Failed to create cache file: maildirwatch (alex)
Feb 11 13:50:47 zeus imapd: Error: Input/output error
Feb 11 13:50:47 zeus imapd: Check for proper operation and configuration
Feb 11 13:50:47 zeus imapd: of the File Access Monitor daemon (famd).
Feb 11 13:50:47 zeus imapd: DISCONNECTED, user=alex, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=21, sent=57, time=1
So I did some searching and determined it was a problem with Courier-IMAP being compiled with File Alteration Monitor support and famd not running (I built RPM directly from source tarball without any customization whatsoever per the instructions on the Courier website).
I found some possible solutions to be:
1) Install and run fam and be sure portmapper is running as well (problem being is that fam has since been replaced by gamin on CentOS, which is installed properly on my system).
2) Do a source install of Courier-IMAP and --disable-fam
Ok, so route 1 went like this: I uninstalled gamin, found fam-2.6.8, installed it, started it manually, made sure portmapper was running and tried again. This time, I still got the same errors in SquirrelMail, but the errors in maillog didn't show up. However, shortly after the page loaded, the famd process I had started manually promptly ended without my intervention. Ok, onto trying #2.
Route 2 went like this: reinstalled gamin, then I tried building a custom RPM by manually configuring with --disable-fam and then using rpmbuild -bc --short-circuit and rpmbuild -bi --short-circuit. That didn't change anything at all, I still had the same errors both with SquirrelMail and in maillog. Then I said ok, I'll just do a complete source install. ./configure --disable-fam && make && make install. Manually started that server, tried again, same deal, both errors.
So I've got problems. Either with Courier-IMAP, SquirrelMail, or both. The other daemons seem to run fine, I just mentioned them in case of the possibility of some kind of (unknown to me) conflict.
If you need to see any of my configs, let me know...any information greatly appreciated...I'm desperate.
I seem to have an error with backing up to my personal FTP repository. I have only just noticed the issue, but i believe it originated when I upgraded Plesk Panel 11 to Plesk Panel 12. I am currently running version 12.0.18 on Cent OS 6.5.
Note whether i check the "Use passive mode" option makes no difference to my problem.Below is what I get from the panel.log under /usr/local/psa/admin/logs
Code:
[2014-11-20 19:49:44] ERR [util_exec] proc_close() failed
[20-Nov-2014 19:49:44 UTC] PleskUtilException: '/usr/local/psa/admin/bin/pmm-ras' '--check-repository' '--dump-storage=ftp://USERNAME@IPADDRESS/MYFTPDIRECTORY/' '--use-ftp-passive-mode' failed with code 121.
stdout:
Transport error: unable to list directory: Curl error: Access denied to remote resource
stderr:
file: /usr/local/psa/admin/plib/Service/Agent/Transport/Local/Exec.php
line: 57
code: 0
trace: #0 /usr/local/psa/admin/plib/Service/Agent/Transport/Local.php(60): Service_Agent_Transport_Local_Exec->process(0, Object(Service_Agent_Command_Exec), Object(Service_Agent_Transport_LocalTransaction))
[code]....
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 would like each of my clients who have a dedicated IP address and an SSL certificate to be able to use their own domain name (and own certificate) when sending mail on ports 465 or 587. I have managed to change the default certificate used by Postfix to my own server's certificate, but I want users to use their OWN IP address and SSL certificate when sending, so this is not an option.
I have been able to update Dovecot to use a specific certificate for each IP address, but I can't seem to update Postfix. I was trying to follow these instructions but my postfix master.cf was quite different than the poster's file and I didn't succeed: [URL] ....
I know many people will simply say "it can't be done" or "just get the users to use the shared IP address", but I know there must be some workaround to make this work, even if it means manually updating the config file after every Plesk update. I'm even prepared (if possible) to have Plesk abandon management of Postfix and have me manage it manually, if that's even an option.
I can't send any mail from the server. I don't get any log information about errors. Postfix is installed on opensuse 13.1.
View 3 Replies View RelatedI 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.
Each migration in the last years I'm running into this bug that Postfix wants to run on port 587 even though this is turned OFF in the Plesk Panel.
Sometimes it does this after some update.
Because another process is running on port 587 this means that postfix does not start and I have some downtime until I "repair" this.
"Repairing" means going into Plesk panel and turning ON SMTP-Auth.... Wait a moment for it to apply and then turning it OFF again....
This unwanted behaviour can be easily reproduced by having this option turned off in the Plesk panel and then running /usr/local/psa/admin/sbin/mchk --without-spam
This will end up in a non-running postfix if another process is already running on port 587.
This shouldn't be happening. Especially because I reported this behaviour years ago..
on a fresh debian 7 64bit openvz system we actually have a problem with the new plesk 12 feature of limiting outgoing mails.We migrated about 25 systems to plesk, this is the first that makes problems.If limiting outgoing mails is activated (i double-checked all possible checkboxes in plesk) a fresh mailbox gives us the following error while trying to send via smtp:
Aug 15 13:09:32 2d4 postfix/smtpd[8645]: connect from unknown[XX.XX.XX.XX]
Aug 15 13:09:32 2d4 postfix/smtpd[8645]: E9AF61C58851: client=unknown[XX.XX.XX.XX], sasl_method=PLAIN, sasl_username=XX@XXX.XX
Aug 15 13:09:32 2d4 greylisting filter[8651]: Starting greylisting filter...
Aug 15 13:09:32 2d4 /usr/lib/plesk-9.0/psa-pc-remote[8611]: handlers_stderr: SKIP
[code]....
After deactivating the feature all mail is sent without any problems. We use postfix + dovecot.
There are several big domains that frequently defer accepting mail from us causing long delays or rejections. Google, AOL, and Yahoo are examples. I'm considering trying the suggestions found in this online posting regarding rate limiting the sending of messages to those domains. In the below URL, please see the section titled "Different policies for different domains"...URL....
Would these changes be safe to make on a CentOS 6.4 server running Plesk 11.0.9 with Postfix 2.8.4? Would any special modifications for Plesk be necessary?
At this moment, all mail (no matter what domain) goes out straight to its destination. We want to send the mail trough a antispam firewall before it enters the internet.
What setting to change?
Reset postfix configuration in plesk 12? I have some misconfiguration on smtp banner and hostname so I prefer to reset all.
View 6 Replies View RelatedI am unable to switch from qmail to postfix via the control panel. It opens a new window that just hangs and never loads. While waiting for it to load, I see these 2 processes running..
root 25108 0.1 0.0 133972 20604 ? S 21:58 0:00 /var/cache/parallels_installer/parallels_installer_CentOS_6_x86_64 --service-mode=components --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
root 25109 0.0 0.0 104952 3032 ? S 21:58 0:00 /var/cache/parallels_installer/parallels_installer_CentOS_6_x86_64 --service-mode=components --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
But after waiting 20 minutes, the browser never loaded and the two proceses remain. So I killed both processes and removed /tmp/psa-installer.lock and started again. The same thing happened.
Is there a way to fix this? If not, is there an easy way to switch MTAs from the command line?
I've a problem with a server with Postfix. Emails (smtp) are refused by an operator because there is too many mail sent in a few moment.
With Qmail, we make this config :
1) we create file concurrencyremote
# vi /var/qmail/control/concurrencyremote
with the value 3
2) we restart Qmail and it's ok
With Postfix, we make that :
1) we modify the file /etc/postfix/main.cf
default_destination_concurrency_limit = 3
2) In /etc/postfix/transport :
wanadoo.com slow ;
wanadoo.fr slow ;
orange.fr slow ;
orange.com slow ;
laposte.net slow ;
.wanadoo.com slow ;
.wanadoo.fr slow ;
.orange.fr slow ;
.orange.com slow ;
3) After :
#postmap /etc/postfix/transport
4) In /etc/postfix/master.cf :
slow unix - - n - 5 smtp -o syslog_name=postfix-slow -o smtp_destination_concurrency_limit=3 -o slow_destination_rate_delay=1
5) In /etc/postfix/main.cf :
slow_destination_recipient_limit = 20
slow_destination_concurrency_limit = 3
And we modify :
transport_maps = hash:/var/spool/postfix/plesk/transport, hash:/etc/postfix/transport
6) At the end :
# /etc/init.d/postfix reload
But it doesn't work. Operator "Orange" refused emails.
In maillog, we have :
dsn=4.3.0, status=deferred (mail transport unavailable)
I just upgraded my Plesk 11.5 on Plesk version: 12.0.18 Update #9 , and after the upgrade the Postfix stop working. And forwarding, receiving is not working at all and I am getting message bellow.
OS: CentOS 6.5 (Final)
Plesk version: 12.0.18 Update #9
This is the mail system at host nsXXXXX.ovh.net.You can delete your own text from the attached returned message. mail system
<xyz@gmail.com>: Command rejected
Final-Recipient: rfc822; xyz@gmail.com
Action: failed
Status: 5.7.1
Diagnostic-Code: X-Postfix; Command rejected
after reinstalling the mta / postfix / smtp (because I couldn't send mails) my plesk is crashed.
I wanted to log in as admin but it doesn't accept my PW. Now with root and then it wants me to accept the license.
Now I copy all my /var/www/vhosts/ maybe when I do the setup steps in plesk it will overwrite all my website content... I hope not all plesk settings are away.
Why I pay every month money for a license? The trouble and work I have with Plesk..
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'
My server is Plesk 12 with Postfix and Courier IMAP i am also using Thunderbird as mail client...
My question is when i create a folder from my mail client or webmail they just appear as sub folders of my inbox which is not what i want, i want root level folders not to be under inbox... When i searched for this i found [URL] ....
Is this still the case? Is there anything i can do to have root level folders?