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
<email@example.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: 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:
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.
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:
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
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
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.
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).
#!/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.
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.
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: connect from unknown[XX.XX.XX.XX] Aug 15 13:09:32 2d4 postfix/smtpd: E9AF61C58851: client=unknown[XX.XX.XX.XX], sasl_method=PLAIN, sasl_username=XX@XXX.XX Aug 15 13:09:32 2d4 greylisting filter: Starting greylisting filter... Aug 15 13:09:32 2d4 /usr/lib/plesk-9.0/psa-pc-remote: handlers_stderr: SKIP
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?
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: 'firstname.lastname@example.org'
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?