Hello,
i changed the default Email address for my Admin and Reseller user.
But if the System write's a Message.
The Sender is shown as noreply@hostname.tld and the Sendername is I-IMSCP.
Do you know how can I change that?
Default email address doesn't change
-
- patched
- bashify
- Closed
- Thread is marked as Resolved.
-
-
That is expected. However your own email should be set in Reply-To header which is not the case for system notifications at this moment. Will be fixed in version 1.3.1.
Right now, message source for system notifications look like:
Code- Return-Path: <noreply@bbox.nuxwin.com>Delivered-To: l.declercq@nuxwin.comReceived: from srv01.bbox.nuxwin.com (unknown [176.154.36.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: l.declercq@nuxwin.com) by panel.i-mscp.net (Postfix) with ESMTPSA id 304253E566 for <l.declercq@nuxwin.com>; Wed, 10 Aug 2016 08:41:43 +0200 (CEST)Received: by srv01.bbox.nuxwin.com (Postfix, from userid 1001) id 4396F25058; Wed, 10 Aug 2016 08:42:28 +0200 (CEST)To: administrator <l.declercq@nuxwin.com>Subject: i-MSCP NoticeFrom: i-MSCP (bbox.nuxwin.com) <noreply@bbox.nuxwin.com>MIME-Version: 1.0Content-Type: text/plain; charset=utf-8Content-Transfer-Encoding: 8bitX-Mailer: i-MSCP Mailer (frontEnd)Message-Id: <20160810064228.4396F25058@srv01.bbox.nuxwin.com>Date: Wed, 10 Aug 2016 08:42:28 +0200 (CEST)Dear administrator,This is an automatic email sent by i-MSCP:Server name: srv01.bbox.nuxwin.comServer IP: 176.154.36.71Version: Git 1.3.xBuild: UnavailableMessage severity: Notice==========================================================================admin logged outUser IP: 192.168.1.1==========================================================================Please do not reply to this email.___________________________i-MSCP Mailer
Here, the Reply-To header is missing.
In version 1.3.1, the message source will looks like:
Display MoreCode- Delivered-To: l.declercq@nuxwin.com
- Received: from srv01.bbox.nuxwin.com (unknown [176.154.36.71])
- (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
- (No client certificate requested)
- (Authenticated sender: l.declercq@nuxwin.com)
- by panel.i-mscp.net (Postfix) with ESMTPSA id AD0EA3E566
- for <l.declercq@nuxwin.com>; Wed, 10 Aug 2016 09:03:25 +0200 (CEST)
- Received: by srv01.bbox.nuxwin.com (Postfix, from userid 1001)
- id BD60725059; Wed, 10 Aug 2016 09:04:10 +0200 (CEST)
- To: administrator <l.declercq@nuxwin.com>
- Subject: i-MSCP Notice
- From: i-MSCP (bbox.nuxwin.com) <noreply@bbox.nuxwin.com>
- Reply-To: l.declercq@nuxwin.com
- MIME-Version: 1.0
- Content-Type: text/plain; charset=utf-8
- Content-Transfer-Encoding: 8bit
- X-Mailer: i-MSCP Mailer (frontEnd)
- Message-Id: <20160810070410.BD60725059@srv01.bbox.nuxwin.com>
- Date: Wed, 10 Aug 2016 09:04:10 +0200 (CEST)
- Dear administrator,
- This is an automatic email sent by i-MSCP:
- Server name: srv01.bbox.nuxwin.com
- Server IP: 176.154.36.71
- Version: Git 1.3.x
- Build: Unavailable
- Message severity: Notice
- ==========================================================================
- admin logged out
- User IP: 192.168.1.1
- ==========================================================================
- Please do not reply to this email.
- ___________________________
- i-MSCP Mailer
However nobody should answer to those messages normally... -
-
-
A fix has been added in the 1.3.x branch. See
- https://github.com/i-MSCP/imsc…7bf7e2ec2abe255265c0a2462
- https://github.com/i-MSCP/imsc…b3fdca648b46e708d07213eca
Thank you for your report.
-
-
I did the Update.. but nothing changed.. the Sendermail is noreply@hostname.tld
-
We do not use the default admin email address in the From header (sender). We set it via the Reply-To header. Look at the message source.
If we process this way, that is not for nothing. The default admin email address can be whatever you want (eg, can be an email not managed by i-MSCP such as a gmail address). This explain why we don't use it in the From header because any server with SPF checks enabled (such as gmail) would reject the mails. Instead, we set it via the Reply-To header, meaning that if a client answer to the mail, it will reply to the mail set in the Reply-To header.
-