Email detected as phishing email in Outlook Express/outlook?

[datnus]

Hi everyone,
I'm using Zimbra 7.0.1 on CentOS
[root@mail ~]# su - zimbra
[zimbra@mail ~]$ zmcontrol -v
Release 7.0.1_GA_3105.RHEL5_64_20110304210645 CentOS5_64 FOSS edition.

Recently, my emails have been detected as phishing, even if I send email from my account in outlook to my own email.

I attach the screenshot.
Any help is appreciated.

[datnus]

Is it because I use self-cert?
But the problem seems to happen recently.
Or I need to patch 7.1.1?

Thanks

[phoenix]

You should update your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

It's impossible to give an answer to the question 'my email is marked as spam' without any information about the email or the problem. Does this only happen in Outlook? If it does, I'd ask yourself why Outlook is marking messages (or is it Windows?) as spam. Does it happen when you view the email in the Web UI? You'd need to post some headers from a suspect email. Are you the only person seeing this problem?

[datnus]

Originally Posted by phoenix

You should update your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

It's impossible to give an answer to the question 'my email is marked as spam' without any information about the email or the problem. Does this only happen in Outlook? If it does, I'd ask yourself why Outlook is marking messages (or is it Windows?) as spam. Does it happen when you view the email in the Web UI? You'd need to post some headers from a suspect email. Are you the only person seeing this problem?

Updated the profile.
I have an application (Redmine) to send email to my email account. It's also marked as phishing (not spam)
I read somewhere on Google. Outlook may mark the email as phishing if using self-cert?

-----------------------
This is the header.

Return-Path: kevin@optimum.vn
Received: from mail.optimum.vn (LHLO mail.optimum.vn) (210.211.109.15) by
mail.optimum.vn with LMTP; Wed, 6 Jul 2011 06:48:30 +0700 (ICT)
Received: from localhost (localhost.localdomain [127.0.0.1])
by mail.optimum.vn (Postfix) with ESMTP id DBDD4EB8077;
Wed, 6 Jul 2011 06:48:29 +0700 (ICT)
X-Virus-Scanned: amavisd-new at optimum.vn
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level:
X-Spam-Status: No, score=-2.898 tagged_above=-10 required=6.6
tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=0.001,
NORMAL_HTTP_TO_IP=0.001] autolearn=ham
Received: from mail.optimum.vn ([127.0.0.1])
by localhost (mail.optimum.vn [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 6OP6BSOW6ceh; Wed, 6 Jul 2011 06:48:16 +0700 (ICT)
Received: from optimum.vn (unknown [210.211.110.59])
by mail.optimum.vn (Postfix) with ESMTPA id 7FBD6EB8076;
Wed, 6 Jul 2011 06:48:12 +0700 (ICT)
Date: Wed, 6 Jul 2011 06:50:42 +0700
From: kevin@optimum.vn
Message-Id: <redmine.journal-183.20110706065042@optimum.vn>
References: <redmine.issue-81.20110704133555@optimum.vn>
Subject: =?utf-8?Q?=5BERP=5FMD_=2D_Bug_=23=38=31=5D_=28Resolved=2 9_=5BChung=5D_BlockUI_khi=E1=BA=BFn_kh=C3=B4ng_up_ h=C3=ACnh_d=C3=B9ng_DBImage_=C4=91=C6=B0=E1=BB=A3c ?=
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary=mimepart_4e13a356a37d4_1056156858ec787425 ac
X-Redmine-Issue-Author: admin
Precedence: bulk
X-Redmine-Issue-Assignee: huy
X-Redmine-Issue-Id: 81
X-Mailer: Redmine
X-Redmine-Project: erpmd
Auto-Submitted: auto-generated
X-Redmine-Site: Optimum issue tracker
X-Redmine-Host: issue.optimum-infra.asia/redmine
To: undisclosed-recipients:;
X-Antivirus: AVG for E-mail 10.0.1388 [1516/3745]
X-AVG-ID: ID68EF54DF-20C136F1

--------------------
Thanks too much.

[datnus]

Any help :|
I have two installation for 2 domains. And both of them have a similar issue RECENTLY.

[datnus]

Any help

[meesha]

Outlook detects phishing - not zimbra, am I right?

You should know what does it mean phishing.
Read this: Phishing - Wikipedia, the free encyclopedia

You should find some "phishing attributes" in your email body. It couldn't be because of problem in headers.