I have followed the instructions here to send Plesk notifications through External SMTP (overuse, new domain creation, etc): URL....Here is the error I see in the panel.log: ERR [panel] Unable to send mail.
Is there another log that I'm missing with a more detailed error? Sending through an external SMTP works fine on sites hosted on the same server (Wordpress, Joomla).
Fehler: Unable to create notification: Unable to create Note object: Note: unable to select: no such row in the table and Fehler: Benachrichtigung kann nicht aktualisiert werden: Unable to create Note object: Note: unable to select: no such row in the table
In tools&settings -> Email Notifications
I run plesk 12.00.18#7 and i have upgrade from 11.5.30 ....
Whenever trying to send an email using roundcube it just seems to fail... No error code is given - see attached image:
I've tried following the article here: [URL] ....
But it didn't seem to work and incidentally the main.inc.php file didn't even exist only a main.inc.php.rpmnew was there. I tried copying it to main.inc.php but it made no difference. Normal SMTP usage via thunderbird works, and everything works when trying to use horde.... it's just a problem with roundcube after the upgrade from 11.5 to 12.
I'm having difficulty sending an email to another email address (with a different domain) which is on the same VPS.The trouble is, on the other domain's VPS control panel, within the DNS settings, the MX records have been pointed externally (to an exchange server). Their email is turned off. But bizarrely, their mailbox is full.
It seems as though Plesk is ignoring the MX records, and sending MY email internally to the OTHER domain's mailbox on the same VPS.How do I get Plesk to send my mail to the correct EXTERNAL MX records?
I am unable to send or receive email from the server in Mail Queue Manager it shows this when clicking deliver now
Code: Delivery attempt for Message ID 1ITmWS-0001u4-QJ Message 1ITmWS-0001u4-QJ is no longer frozen delivering 1ITmWS-0001u4-QJ LOG: MAIN lowest numbered MX record points to local host: domain.com LOG: MAIN == email@example.com R=lookuphost defer (-1): lowest numbered MX record points to local host LOG: MAIN Frozen
The problem is, can not send mail via SMTP using popular scripts Opencart, SMF, Osclass. The problem was lapping Plesk 11.5 via 587 port. That was timeout connection or authorization error with the correct settings. Mail may be sent, sometimes not. No longer working than working. At the same time when working with e-mail clients(example, The Bat) work fine. In Plesk 12 same problem. Port 465 - e-mail clients(example, The Bat) work fine. But can not send mail via SMTP using popular scripts Opencart, SMF, Osclass. When using Cpanel with Exim - all work perfect. But the Plesk e-mail with Postfix - constant problems.
we regularly get this message in boxmail of adress used to send email from server.This is the mail system at host DOMAIN.fr. You can delete your own text from the attached returned message.The mail system
<1@SERVERNAME.HOSTER.com> (expanded from <1>): User unknown in virtual alias table
If i look in maillog i see that :
May 18 16:48:52 SERVERNAME postfix/error: F22521B4E45: to=<1@SERVERNAME.HOSTER.com>, orig_to=<1>, relay=none, delay=0.07, delays=0.04/0.01/0/0.02, dsn=5.0.0, status=bounced (User unknown in virtual alias table)
The problem is in error message (at top) the message attached is the one sent to EMAIL@DOMAIN.com. So we can think the message is not sent to EMAIL@DOMAIN.com. SERVERNAME, HOSTER and EMAIL@DOMAIN are here to mask real data.
Upgrading to 12.0.8 and found this that looks like a bug. Email messages cannot be send through Roundcube Webmail. Outbound Email Limits are active.
Code: REDACTED py_limit_out: ERROR Rejecting message: system user uid='10039' is not allowed to send mail REDACTED plesk sendmail: handlers_stderr: DATA REPLY:554:5.7.0 Your message could not be sent. The user roundcube_sysuser is not allowed to send email.#012REJECT
Apart from Domains, Emails and Subscriptions there is no way to allow roundcube_sysuser through Mail server settings.
I have Plesk and SmarterMail running on a server.SmarterMail is setup as 'require SMTP authentication before relaying' email (I think this is standard practice).I cannot get Plesk to send any emails, such as forgotten password reminders and notifications.Plesk tries to send but gets a "550 Authentication is required for relay" error... which is expected, because I can't find anywhere in Plesk to enter the authentication details for the email account being used to send (relay) the emails.
I don't want to setup a 'whitelist' or 'bypass relay authentication' for 127.0.0.1 as I have had a spam issue with this previously.where to enter the username / password details so Plesk Panel can authenticate and send it's emails?
I keep having certain domains being hijacked and mass emails being sent from them somehow. I've disabled mail within domain control panel for each domain and issue keeps occurring. I've limited # of emails as well to 2-5 per hour but now so many are trying to be sent from my server it is clogging up mail queue and I have to log into server via ssh and run postsuper -d ALL every day or two. It is very frustrating. The only way I can stop it is to disable domain in plesk panel but that is not an option.
What can I do to find the cause of this issue and stop it?
I registered a domain name and setup a Linux server on GoDaddy, choosing Plesk panel with Power Pack. Inside the panel I created an email address, which I can access from the webmail interface without problems. I decided to setup my clients as well, using the IMAP configuration, as I'm using multiple devices.
I followed the instructions for Outlook express and I was able to setup the account on my virtual machine, with Windows 7 and Windows Live Mail.Though, speaking of the host machine, a MacBook Pro, I normally use Apple Mail that comes with MacOS. Instructions for setting up Mail are updated back to Snow Leopard at least and they do not work properly. I tried various configurations, but I was only able to receive mail on the account, while sending won't work at all.
I'd like Parallels to update the guide or, at least, to open a KB page with the solution(s) to this issue: I googled it and found out that it is a common issue.
How can I completely disable ALL notifications from plesk? We NEVER want plesk to notify customers of overages.
Not only do we want to disable all notifications but I want someone at parallels to know about the bug.. It notifies people that they are over or approaching limits when they aren't anywhere near it.. Here is a sample of one of the notifications emails sent. Names and emails changed of course...
Code: From: My Name [mailto:firstname.lastname@example.org] Sent: Wednesday, October 09, 2013 3:38 AM To: My Customer Name Subject: <host.mydomain.com> Notification: Resource usage by subscription has exceeded the allotments.
The 'domain.com' subscription, owned by user 'Customer Name', is approaching or already exceeded the resource usage limits:
On one CentOS 6.5 Plesk 12.0.18 install (with all MUs applied) each time an admin logs in a notification is displayed ("Plesk was successfully updated. View detailed information on the updates.") and once a week the panel generates an email notification (Plesk panel updated successfully).
Other Plesk 12.0.18 servers that are set to automatically update aren't generating this email notification or displaying the "green" notification upon login to the Plesk Panel. Is there a flag, tmp file, or a DB trigger that isn't being set properly to cause this?
Run a small but fast-growing social network and we're getting to the point where our email notifications (e.g., SoAndSo Added You as a Friend) isn't scaling and we need to find an alternative solution. We're going to be sending out 1,000+ notifications a day and one option would be to run Postfix (or something similar) on our servers. Of course the challenge with this is message delivery. Our concern is that even if abide by strict protocols and give our people unsubscribe options we'll still get listed as Spam. Some of the hosted services seem to have solutions that help with this given that they have good relationships with major ISPs, email hosts, etc.