• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

DomainKey-Status: bad format (blank e-mails)

FrantišekH

New Pleskian
Just after I upgraded from Plesk v9.2.? to 9.5.2, server started to send to my postmaster (probably directed by /var/qmail/alias/*) blank e-mails. Every about 20 minutes arrives 1-4 e-mails. Why?

Example header (===domain=== is a replacement):
DomainKey-Status: bad format
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on ===domain===
X-Spam-Level: *****
X-Spam-Status: No, score=5.7 required=7.0 tests=EMPTY_MESSAGE,MISSING_HB_SEP,
MISSING_HEADERS,MISSING_SUBJECT,NO_RELAYS,TO_CC_NONE autolearn=no
version=3.1.9
Received: (qmail 9372 invoked by alias); 17 Sep 2010 04:51:22 +0200
Delivered-To: postmaster@===domain===

I read bunch of topics here, but nothing resolve my problem. I exactly tried mchk, and then replacing qmail by postfix and back too, but it did not help. What now? It is disturbing. Why server sends me that? What part of system sends that?


Thank you in advance.
 
I think that it is a "from=#@[]" problem, as I can see in log. You have solution for Centos v, but I use Centos 4.

How can I fix that?
 
Last edited:
Back
Top