• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Weird - e-mail from server after upgrading to 9.23

T

Total

Guest
Since I upgraded to 9.23 , every 6 minutes or so I get a blank e-mail with no sender from my server ? Any Ideas - everything updated great but this e-mail is annoying .. Ideas ??
 
Could be ? It is coming from unknown and it is from my server . How can I check if it is coming from drweb ?
 
Qmail Alias

I think it come from

/var/qmail/alias

You can use command ls -al to list file in that directory.

You will see some file

-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-anonymous
-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-drweb-daemon
-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-mailer-daemon
-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-mailman
-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-postmaster
-rw-r--r-- 1 root qmail 18 Nov 16 23:23 .qmail-root

and you can use cat command to see inside the file.

cat .qmail-anonymous

you will see the email inside it file.
and the email in the file is as same as email in admin profile in plesk.
If you change email in you admin profile the file will change too.
 
Thanks for the info , but how can I stop these blank e-mails from being sent ??
 
Thanks for the info , but how can I stop these blank e-mails from being sent ??

I am willing to bet that if you look at the raw email header you will find a domainKeys error message on top of each of them. I had the same problem and there is only one way that I am aware of to fix the problem

Turn off the "Allow signing outgoing mail" option for DomainKeys in the email settings. But then if you don't go manually remove the domainkeys DNS records from all domains, you will start getting bounced email because plesk will not do that for you automatically anymore in 9.2.3.
 
The full header

Delivered-To: XXXXXXXXXXXXXXXXXXXXXX
Received: by 10.213.28.194 with SMTP id n2cs130901ebc;
Wed, 25 Nov 2009 17:00:14 -0800 (PST)
Received: by 10.115.61.16 with SMTP id o16mr6865897wak.15.1259197212766;
Wed, 25 Nov 2009 17:00:12 -0800 (PST)
Return-Path: <?@??>
Received: from 216-55-183-183.dedicated.abac.net (216-55-183-183.dedicated.abac.net [216.55.183.183])
by mx.google.com with ESMTP id 25si392495pxi.3.2009.11.25.17.00.12;
Wed, 25 Nov 2009 17:00:12 -0800 (PST)
Received-SPF: softfail (google.com: best guess record for domain of transitioning #@[] does not designate 216.55.183.183 as permitted sender) client-ip=216.55.183.183;
Authentication-Results: mx.google.com; spf=softfail (google.com: best guess record for domain of transitioning #@[] does not designate 216.55.183.183 as permitted sender) smtp.mail=#@[]
Date: Wed, 25 Nov 2009 17:00:12 -0800 (PST)
Message-Id: <[email protected]>
Received: (qmail 22856 invoked by alias); 25 Nov 2009 19:00:11 -0600
Delivered-To: [email protected]


Ideas ??
 
Sorry , but what do I need to do with those files ? Thanks

You should backup original /var/qmail/bin/qmail-queue file and replace with attached according your platform architecture - 32bit or 64bit. Do not forget set right permission to this file!

# ll /var/qmail/bin/qmail-queue
-r-x--s--x 1 mhandlers-user popuser 72408 Oct 16 21:58 /var/qmail/bin/qmail-queue
 
You should backup original /var/qmail/bin/qmail-queue file and replace with attached according your platform architecture - 32bit or 64bit. Do not forget set right permission to this file!

Thanks , I will post how it goes ..
 
You should backup original /var/qmail/bin/qmail-queue file and replace with attached according your platform architecture - 32bit or 64bit. Do not forget set right permission to this file!

I got the server people to do this but now I'm getting 10000 + of these in the last 1.5 hrs ..


Delivered-To: XXXXXXXXXXXXXXXXXXXXXXX
Received: by 10.213.28.194 with SMTP id n2cs236301ebc;
Fri, 27 Nov 2009 17:32:03 -0800 (PST)
Received: by 10.115.61.16 with SMTP id o16mr2768502wak.15.1259371838810;
Fri, 27 Nov 2009 17:30:38 -0800 (PST)
Return-Path: <[email protected]>
Received: from 216-55-183-183.dedicated.abac.net (216-55-183-183.dedicated.abac.net [216.55.183.183])
by mx.google.com with ESMTP id 31si3412023pxi.24.2009.11.27.17.30.38;
Fri, 27 Nov 2009 17:30:38 -0800 (PST)
Received-SPF: pass (google.com: best guess record for domain of [email protected] designates 216.55.183.183 as permitted sender) client-ip=216.55.183.183;
Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of [email protected] designates 216.55.183.183 as permitted sender) [email protected]
Date: Fri, 27 Nov 2009 17:30:38 -0800 (PST)
Message-Id: <[email protected]>
Received: (qmail 16079 invoked by alias); 27 Nov 2009 19:30:37 -0600
Delivered-To: [email protected]
 
That workaround is broken

That workaround will break your mail server ..
 
I have 136,000 Messages in my mail que now , from 1969 . How can I delete all these bogus e-mails ?? Thnaks
 
I have the same problem after 9.2.3 upgrade. Here is my message header

DomainKey-Status: bad format
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb3 (2006-10-05) on
myhost.mydomain.com
X-Spam-Level: *****
X-Spam-Status: No, score=5.7 required=6.0 tests=EMPTY_MESSAGE,MISSING_HB_SEP,
MISSING_HEADERS,MISSING_SUBJECT,NO_RELAYS,TO_CC_NONE autolearn=no
version=3.1.7-deb3
Received: (qmail 1580 invoked by alias); 29 Nov 2009 10:00:23 +0100
Delivered-To: [email protected]
 
Sorry guys the patch works .. You just need to make sure that both the ownership and permissions on the replacement qmail-queue are set correctly. It has the setgid set so you have to do it in this order:

Code:
chown mhandlers-user:popuser /var/qmail/bin/qmail-queue
chmod 2511 /var/qmail/bin/qmail-queue
 
Back
Top