• 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

Duplicate emails

kram@

Regular Pleskian
Hello All,

I recently started receiving duplicate emails to many email accounts on my server.
This is happening on multiple domains.
I found that running /usr/local/psa/admin/sbin/mchk -v temporarily resolves the problem.
However as soon as a new email account is added to the server or server is rebooted the problem returns. running /usr/local/psa/admin/sbin/mchk -v fixes the problem again.

I have re sinstalled psa-qmail
I have deleted and recreated one or two of the mail boxes in question.
I have run the command find /var/qmail/mailnames -type d -name '.*' -a -not -name '.spamassassin' -exec touch '{}'/maildirfolder \; -exec chown popuser.popuser '{}'/maildirfolder \;

neither of these resolves the problem.

Any help would be great!
 
You can check your Antivirus software of you email client. Sometime, the antivirus happen the same problem.
 
Hello facers,

After further investigation I found that the problem is indeed server related.

One mail recieved has SPAM Headers

X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
server.kbpsaccess.co.za
X-Spam-Level:
X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,
TVD_SPACE_RATIO autolearn=no version=3.2.3

Subject: testing
Date: Mon, 14 Jan 2008 10:24:47 +0200

Second email - NO SPAM headers

Subject: testing
Date: Mon, 14 Jan 2008 10:24:47 +0200

-------

I ran I found that after running /usr/local/psa/admin/bin/mchk --without-spam
the duplicate emails stopped & obviously No spam checking.

I then ran /usr/local/psa/admin/bin/mchk -v
Still no duplicate emails - but no spamassassin integration.

----

I have logged a support ticket with 4PSA, so far my reply has been
"make sure that you run Spam Guardian 3.1.5. "

----
 
4psa

I found that when I upgraded to 3.1.5 as suggested the problem did go away... Looks like its something with 8.3 and older versions of 4PSA SG?
 
Back
Top