All outgoing mail goes to spam folder (Gmail, Outlook, etc)

[MiquelA]

Hi all,

I've been looking for a solution of this problem for more than one week and I'm tired of trying things that don't solve anything.

The problem is that all the mail that exits my VPS server (OVH) is going to the spam folders of Gmail, Outlook, etc accounts.

I've tryied to connect my Gmail account to check via POP3 my inbox on my VPS, and all I get is an SSL error.

Can somebody help me?

 

[UFHH01]

First, I would suggest to investigate your logs and configuration files ( Parallels Plesk Panel for Linux services logs and configuration files ( KB: 111283 ) ) if you experience issues/problems, because guessing might not solve issues and provided suggestions might not work and there are really a lot of possibilities, why something might not work as expected.

Afterwards, you might check with the help of "http://www.port25.com/support/authentication-center/email-verification/" your eMail - server configurations, as well as your SPF - entries and DKIM - signatures.

Even that Plesk makes it very easy to administrate servers, you might as well read some documentations about your product: Parallels Plesk - Documentations

Another great help is the Parallels Knowledge-Base. Most issues/problems and a lot of work-arounds are there to help you.

.... and if all this didn't help... there is as well the Search Forums, where you can search with the words "spam mail Google" and you probably will find threads and posts with the same issues/problems.


Feel free to ask further questions, but pleeeeeeaaaaase ( ^^ ), provide some log - entries with failures/issues/problems, so that helpfull people might suggest work-arounds or guide you to a direction, so that your issues can be fixed.

 

[MiquelA]

Okay, I wasn't able to check my postfix log because I can't access it or it's empty, when I nano the: /usr/local/psa/var/log/maillog I got an empty file.

Also I checked my mail with Port25 and I got the following:

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         neutral
Sender-ID check:    pass
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname:  mail.miquelfa.com
Source IP:      92.222.181.247
mail-from:      [email protected]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: [email protected]
DNS record(s):
    miquelfa.com. SPF (no records)
    miquelfa.com. 86400 IN TXT "v=spf1 +a +mx -all"
    miquelfa.com. 86400 IN A 92.222.181.247

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: [email protected]
DNS record(s):

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified:

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: [email protected]
DNS record(s):
    miquelfa.com. SPF (no records)
    miquelfa.com. 86400 IN TXT "v=spf1 +a +mx -all"
    miquelfa.com. 86400 IN A 92.222.181.247

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)

Result:         ham  (-2.9 points, 5.0 required)

pts rule name              description
---- ---------------------- --------------------------------------------------
-1.0 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]

==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================

SPF and Sender-ID Results
=========================

"none"
      No policy records were published at the sender's DNS domain.

"neutral"
      The sender's ADMD has asserted that it cannot or does not
      want to assert whether or not the sending IP address is authorized
      to send mail using the sender's DNS domain.

"pass"
      The client is authorized by the sender's ADMD to inject or
      relay mail on behalf of the sender's DNS domain.

"policy"
     The client is authorized to inject or relay mail on behalf
      of the sender's DNS domain according to the authentication
      method's algorithm, but local policy dictates that the result is
      unacceptable.

"fail"
      This client is explicitly not authorized to inject or
      relay mail using the sender's DNS domain.

"softfail"
      The sender's ADMD believes the client was not authorized
      to inject or relay mail using the sender's DNS domain, but is
      unwilling to make a strong assertion to that effect.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability to
      retrieve a policy record from DNS.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being absent or
      a syntax error in a retrieved DNS TXT record.  A later attempt is
      unlikely to produce a final result.


DKIM and DomainKeys Results
===========================

"none"
      The message was not signed.

"pass"
      The message was signed, the signature or signatures were
      acceptable to the verifier, and the signature(s) passed
      verification tests.

"fail"
      The message was signed and the signature or signatures were
      acceptable to the verifier, but they failed the verification
      test(s).

"policy"
      The message was signed but the signature or signatures were
      not acceptable to the verifier.

"neutral"
      The message was signed but the signature or signatures
      contained syntax errors or were not otherwise able to be
      processed.  This result SHOULD also be used for other
      failures not covered elsewhere in this list.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability
      to retrieve a public key.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being
      absent. A later attempt is unlikely to produce a final result.

 

[MiquelA]

Nobody can help me with this?

 

[Triantafyllos]

hi MiquelA, did you find any solution ?

 

[MiquelA]

hi MiquelA, did you find any solution ?

Hi, yes, talking to a friend we realized that my DNS default settings where wrong. The TXT record of mailing options had a default schema (that I don't remember) that was wrong, now I'm using this one: "v=spf1 mx" and my mail is working great since this change.

¡Hope this helps you!

 

[UFHH01]

A recommended SPF - setting is:

v=spf1 +a +mx +a:server.example.com +ip4:999.999.999.999 ?all
​

• Please make sure, that an "A" entry exists for your server on your initial nameserver ( this is mostly either the nameserver from your server-hosting-provider, or the one from your domain-hosting-provider! ). It should be the same as your output for the command "hostname -f". ( +a:server.example.com )

There is no need to create a subdomain over the Plesk Control Panel for that domain, but it is recommended to have such an "A" - entry on your initial nameserver.

Plesk is mostly NOT the initial nameserver, if you rented an IP, so please be aware, that the specific rDNS - setting for an IP can only be done on the nameserver of the provider, where you rented the IP from. If you changed the possible initial hostname ( i.e.: server123.yourserver_provider_domain.com ) to a hostname related to your registered FQDN - domain ( i.e.: server1.example.com ), please ask your hosting-provider to reverse the initial entry to your specification, because most hosting-provider don't let the customer doing this on their nameserver, or charge an extra monthly amount for it for such a feature.​

• Please have as well a look at your /etc/hosts - file and ensure, that it looks like the example:

127.0.0.1    localhost.localdomain    localhost
::1          localhost6.localdomain6  localhost6

999.999.999.999    server1.example.com    server1

999.999.999.999 has to be replaced with your own, unique IP.​

• Adding the IP in your SPF - entry is not essential, but can prevent issues ( +ip4:999.999.999.999 )

• Using the string "?all", instead of the common used "~" or even "-" is the best solution to prevent HARD FAILS, because the string "?" will result in a SOFT FAIL, if any of your settings may not be verified. SOFT FAILS are execpted by most mail - servers, but HARD FAILS will always result in denys.

 

[ophiel]

i'm sorry for reviving and old topic, i guess i didn't want to make another thread for it.
i'm having the same issues all the outgoing mails ends up in spam folder, i've tried every suggestion i could find but to no avail (be it dkim,spf, sending mail via smtp) if someone could guide a beginner on this topic and thank you very much

 

[AYamshanov]

I think will be better create a new topic with information about your infrastructure and some diagnostic information.

 

[ophiel]

I think will be better create a new topic with information about your infrastructure and some diagnostic information.

alright thank you for replying