My scan pass...I just writing what I have mention them so if someone else has got the same problem can see it
------------------------------------------------------------------------------------------------------------------
I am writing this regarding the false positive.
I will explain the reasons why I believe that is false/positive
1) The error CVE-2011-0411 is applied to postfix. My server is not installed with Postfix but with courier and dovecot
The below link is for reference
http://forums.cpanel.net/f43/mail-s...sing-courier-mail-server-fail-pci-426422.html
Also those 2 links are reference that Cpanel is not use Postfix
Dear CPanel. You need to support Postfix. I’ll even ask nicely. - Welcome to Nowhere
http://forums.cpanel.net/f5/where-does-postfix-get-installed-default-114809.html
2) Also we enabled "connect with SSL or issue the STARTTLS command before they are allowed to authenticate with the server" setting in exim configuration.
3) We tried also to disable IMAPD and POP3D but after this Webmail no works
4) Please read the whole forum link that I gave you before
http://forums.cpanel.net/f5/where-does-postfix-get-installed-default-114809.html
They mentioned the same problems with panopticsecurity before some months and after this you accept the error as false/positive
For those reasos as you can understand its not false positive
Some other reasons why need to be done as false positive
1)The specific server (213.175.193.247) use only files regarding the payment method (Emerchantpay). I don't have any other site on that server.Also the main website (domain.com) is not hosted to that server.
What does that mean?
It means that I don't send any e-mail with credit cards or passwords when the transaction will complete to the customer or to somewhere else. Also that means at all I don't use e-mail.
How can you confirm this?
You can asked our payment provider (emerchantpay). We enable e-mail notifications by their control panel and they are doing the ''job'' of sending e-mails by their server..
Reference from exim that they mention it as '' Extra paranoia around STARTTLS-with-data-in-buffer.'' but not vurnenable
https://lists.exim.org/lurker/message/20110324.091715.d5e73afd.es.html
------------------------------------------------------------------------------
''+ /* There's an attack where more data is read in past the STARTTLS command
+ before TLS is negotiated, then assumed to be part of the secure session
+ when used afterwards; we use segregated input buffers, SO ARE NOT
+ VURNENABLE, but we want to note when it happens and, for sheer paranoia,
+ ensure that the buffer is "wiped".
+ Pipelining sync checks will normally have protected us too, unless disabled
+ by configuration. */""
----------------------------------------------------------------------------------