• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Autoresponder forwards messages to root

keff

Basic Pleskian
Hello,

my Plesk is 10.4.4 #MU47 on Debian 6.0 64-bit Postfix

I have problem with autoresponder on one account. When user set autoresponder messagess are forarded to:
[email protected]omain
[email protected]omain
[email protected]omain
Only with this account problem exist. What can I chceck to repair this problem?

X-Original-To: [email protected]
Delivered-To: [email protected] # admin email
Received: by nsxxx.ovh.net (Postfix)
id A0AE8AF418B; Fri, 9 Nov 2012 08:36:00 +0100 (CET)
Delivered-To: [email protected]omain
Received: by nsxxx.ovh.net (Postfix)
id 9C6B1AF3E58; Fri, 9 Nov 2012 08:36:00 +0100 (CET)
Delivered-To: [email protected]omain
Received: by nsxxx.ovh.net (Postfix)
id 9B581B271C0; Fri, 9 Nov 2012 08:36:00 +0100 (CET)
Delivered-To: [email protected]omain
Received: by nsxxx.ovh.net (Postfix, from userid 0)
id 9871EAF3E58; Fri, 9 Nov 2012 08:36:00 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on nsxxx.ovh.net
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=7.0 tests=RCVD_IN_DNSWL_NONE,
UNPARSEABLE_RELAY autolearn=ham version=3.3.1
X-Original-To: account@userdomain # this account have autoresponder set
Delivered-To: account@userdomain
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network
Received: from mailoutvans01.telekom-dienste.de (mailoutvans01.telekom-dienste.de [62.153.159.240])
by nsxxx.ovh.net (Postfix) with ESMTP id 29BAEAA0E68;
Fri, 9 Nov 2012 08:35:56 +0100 (CET)
Received: from fwd17.aul.t-online.de (fwd17.aul.t-online.de )
by mailoutvans01.telekom-dienste.de with smtp
id 1TWisf-00014D-20; Fri, 09 Nov 2012 08:19:57 +0100
Received: from CEG-EX1.techfab.local (r9X2ooZXrtXz8vQblyXyeWo4OdZj+o1lmYYJ28xLEpZ2sRupW+NvqMBpCDSNI9V9jGGAG0yxv4@[217.7.196.122]) by fwd17.webpage.t-com.de
with esmtp id 1TWisc-0h2yh60; Fri, 9 Nov 2012 08:19:54 +0100
Received: from CEG-EX1.techfab.local ([::1]) by CEG-EX1.techfab.local ([::1])
 
I'm experiencing the same issue on a Plesk 11 server on Centos5.8... did you ever find a solution?
 
Parallels: This is still unresolved, we have that too....we can read client's mail's because of this, our boss is VERY unhappy right now....
 
---------------------------------------------------------------
PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE

OS CentOS 5.8 (Final)
Panel version 11.0.9 Update #32
KVM Virtualization

PROBLEM DESCRIPTION
when activating autoresponder for one of the email addresses on the server (always the same),messages sent to this address generate a bounce to the Plesk administrator.
Other addresses on the same domain or server can activate their auto-responder without experiencing this issue.

STEPS TO REPRODUCE
activating autoresponder for this very email address on the server.
So far it's happening on only one of our shared Plesk servers, only for this specific email user.
Contact us for access to the server.

ACTUAL RESULT
somehow the incoming email on this active auto-responder generates a bounce that's sent to [email protected]omain/ [email protected]omain which is delivered to the Plesk Server administrator address.

Delivered-To: [email protected]omain
Received: by psaXXX.host.com (Postfix)
id 0BD5F100048; Mon, 19 Nov 2012 12:24:40 -0500 (EST)
Delivered-To: [email protected]omain
Received: by psaXXX.host.com (Postfix)
id 04D661000BC; Mon, 19 Nov 2012 12:24:40 -0500 (EST)
Delivered-To: [email protected]omain
Received: by psaXXX.host.com (Postfix, from userid 0)
id F1C581000B8; Mon, 19 Nov 2012 12:24:39 -0500 (EST)
X-Original-To: [email protected]
Delivered-To: [email protected]
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network


EXPECTED RESULT
messages sent to this email address should NOT be bounced to the Plesk admin email address.

ANY ADDITIONAL INFORMATION
--------------------------------------------------------------

we can provide sample full message headers of the message received by the Plesk administrator.
The sample provided above is old, but this has been happening each time this user activates his auto-responder.
 
The same problem here since last update:

CentOS 6.4 (Final)
Plesk 11.0.9 Update #44

Any solutions?
 
No response from Parallels? The issue still occur and we are very unhappy to reading customers mail.
 
Same issue here with Plesk 9.5.4 MU29 (CentOS release 5.9 (Final)). Please Parallels look into this ASAP. Thanks.
 
Cool. Hopefully Parallels will have an easy fix! My email headers on these postmaster emails are similar. Oddly, only two of my hosted domains are "sending" this spam to my Plesk admin email address. The email header looks like this:

Return-path: <>
Envelope-to: [email protected]
Delivery-date: Thu, 08 Aug 2013 10:55:21 -0500
Received: from my-plesk-domain.net ([000.000.000.000]:47187)
by diamante.websitewelcome.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
(Exim 4.80)
id 1V7SYa-0006hd-My
for [email protected]; Thu, 08 Aug 2013 10:55:21 -0500
Received: by my-plesk-domain.net (Postfix)
id D3DF9E40E2; Thu, 8 Aug 2013 11:55:19 -0400 (EDT)
Delivered-To: [email protected]omain
Received: by my-plesk-domain.net (Postfix)
id D3483E4114; Thu, 8 Aug 2013 11:55:19 -0400 (EDT)
Delivered-To: [email protected]omain
X-No-Auth: unauthenticated sender
X-No-Relay: not in my network
Received: from 2.185.213.142 (unknown [2.185.213.142])
by my-plesk-domain.net (Postfix) with SMTP id CACD6E40E2
for <[email protected]>; Thu, 8 Aug 2013 11:55:18 -0400 (EDT)
Received: from unknown (HELO localhost) ([email protected]@70.167.133.196)
by 2.185.213.142 with ESMTPA; Thu, 8 Aug 2013 20:26:36 +0330
From: [email protected]
To: [email protected]
Subject: Report
X-Spam-Status: No, score=2.4
X-Spam-Score: 24
X-Spam-Bar: ++
X-Spam-Flag: NO
X-Antivirus: avast! (VPS 130808-0, 8/8/2013), Inbound message
X-Antivirus-Status: Clean
 
This just started happening with our Plesk 10.4.4 box on Saturday the 17th of August. The panel did update then, but it's not clear which update # it was. We're now on #54 and the issue is still present.

I've disabled and re-enabled mail services on the domain. I've disabled the mail account and re-enabled it. I've disabled and re-enabled the autoresponder and run mchk --without-spam. I've also killed all postfix processes and restarted the service. The issue remains after all of this.
 
I found a workaround for this. In the Auto-reply settings, there's an option to forward the original message to an address after the auto reply is sent. By specifying an address here, it seems to no longer send emails to the mailer-daemon / root on the server. Oddly setting up auto-replies for other addresses without the forward address specified did *not* result in this problem occurring, so I can't say what the circumstances are that create the issue.

If you don't have an address to put in there, you can create one to 'black-hole' the messages. Simply create a new mailname, don't give it a mailbox or redirect of any kind. Then enter that address in for the auto-reply 'forward' setting.
 
The following query will show you all affected mail addresses:

Code:
SELECT psa.mail.mail_name, psa.domains.name FROM psa.mail,psa.domains WHERE psa.mail.dom_id=psa.domains.id AND psa.mail.id in (SELECT psa.mail_resp.mn_id FROM psa.mail_resp WHERE psa.mail_resp.id in (SELECT psa.resp_forward.rn_id FROM psa.resp_forward WHERE psa.resp_forward.address=''));


You can then continue to follow the steps in:

http://kb.parallels.com/en/117978
 
Back
Top