On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

How to rewrite headers in outgoing mail messages

Follow

Comments

6 comments

  • Avatar
    Miomir Besarabic

    Hi,

    Is it possible to prevent outgoing mails marked as Spam with header_check? A lot of customers forward mails to extern mail addresses and make us a problem.

    Regards,

    Miomir

     

    0
    Comment actions Permalink
  • Avatar
    Dinara Aspembitova

    Hello @Miomir Besarabic,
    As I can see the case has been already discussed in the following article https://support.plesk.com/hc/en-us/articles/115000786914 
    Here is your reply:
    -----------
    The best solution was Spamassassin pre-queue filtering, which cover everything and allow to reject Spam or unwanted mails. Pre-queue filtering is simple to implement with Postfix and header_checks (on Linux). I did on our test server with just few changes in 2 files.
    -----------

    Glad to hear the solution is found.

    If you have any additional questions, let us know.

    0
    Comment actions Permalink
  • Avatar
    Andrii Balytskyi

    pcre does not work for me. I use regexp.

    0
    Comment actions Permalink
  • Avatar
    Clemens Mol

    Adding the "/^Received:s+.*/ IGNORE" makes Plesk add a second Date header. This behaviour started at Obsidian, had this rule work for Plesk Onyx a few weeks ago. Any suggestions on how to fix this?

    0
    Comment actions Permalink
  • Avatar
    Andrii Balytskyi

    Do not use IGNORE. Use REPLACE and this issue  will be fixed.

    0
    Comment actions Permalink
  • Hi Clemens Mol,

    I've just tested it on our test environment and it hasn't added a second date header as you can see below:

    [root@our cur]# cat 1586266053.M953238P25613.our.example.com\,S\=1408\,W\=1446\:2\,S
    Authentication-Results: our.example.com;
    dmarc=pass (p=NONE sp=NONE) smtp.from=example.com header.from=example.com;
    dkim=pass header.d=example.com
    Return-Path: <webspuser@example.com>
    X-Original-To: padmin@example.com
    Delivered-To: padmin@example.com
    Received: by our.example.com (Postfix, from userid 10000)
    id 7104A2A318; Tue, 7 Apr 2020 15:27:33 +0200 (CEST)
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=example.com;
    s=default; t=1586266053;
    bh=*******************=; h=To:Subject:From;
    b=*******************=
    To: padmin@example.com
    Subject: New WordPress Site
    Date: Tue, 7 Apr 2020 13:27:33 +0000
    From: WordPress <wordpress@example.com>
    Message-ID: <cMID@example.com>
    X-Mailer: PHPMailer 5.2.27 (https://github.com/PHPMailer/PHPMailer)
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8

    Are you sure your Postfix configuration is by default and has no customizations?

    In any case, in order to investigate, it would be better if you open a new support request.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request