Sponsor:

Server and Web Integrator
Link:
Kloxo-MR logo
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:
Click Here
Please login or register. 2024-04-29, 18:07:26

Author Topic: DMARC signining in Qmailtoaster  (Read 2883 times)

0 Members and 1 Guest are viewing this topic.

Offline Spacedust

  • Super Grand Master
  • ****
  • Posts: 4,050
  • Karma: +1/-0
    • View Profile

Offline MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,807
  • Karma: +119/-11
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: DMARC signining in Qmailtoaster
« Reply #1 on: 2015-04-29, 09:51:05 »
Look like we don't need this plugin because qmail-toaster that we used already modified qmail-remote to handle domainkeys and dkim.
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

Offline Spacedust

  • Super Grand Master
  • ****
  • Posts: 4,050
  • Karma: +1/-0
    • View Profile
Re: DMARC signining in Qmailtoaster
« Reply #2 on: 2015-04-29, 12:23:42 »
Look like we don't need this plugin because qmail-toaster that we used already modified qmail-remote to handle domainkeys and dkim.

So just add DMARC to Qmail. DMARC in DNS does not report anything.

Offline MRatWork

  • Administrator
  • The Elite
  • *****
  • Posts: 15,807
  • Karma: +119/-11
  • Gender: Male
    • View Profile
    • MRatWork Forum
Re: DMARC signining in Qmailtoaster
« Reply #3 on: 2015-04-29, 13:24:40 »
This is example from google.com about something wrong with hostspectra.com:
Code: [Select]
<?xml version="1.0" encoding="UTF-8" ?>
<feedback>
  <report_metadata>
    <org_name>google.com</org_name>
    <email>noreply-dmarc-support@google.com</email>
    <extra_contact_info>http://support.google.com/a/bin/answer.py?answer=2466580</extra_contact_info>
    <report_id>10619206793863869024</report_id>
    <date_range>
      <begin>1430179200</begin>
      <end>1430265599</end>
    </date_range>
  </report_metadata>
  <policy_published>
    <domain>hostspectra.com</domain>
    <adkim>r</adkim>
    <aspf>r</aspf>
    <p>quarantine</p>
    <sp>quarantine</sp>
    <pct>50</pct>
  </policy_published>
  <record>
    <row>
      <source_ip>62.210.181.21</source_ip>
      <count>2</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>fail</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>hostspectra.com</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>oln3.hostspectra.com</domain>
        <result>pass</result>
      </dkim>
      <spf>
        <domain>hostspectra.com</domain>
        <result>softfail</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>62.210.181.21</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>fail</spf>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>hostspectra.com</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>hostspectra.com</domain>
        <result>pass</result>
      </dkim>
      <spf>
        <domain>hostspectra.com</domain>
        <result>softfail</result>
      </spf>
    </auth_results>
  </record>
  <record>
    <row>
      <source_ip>62.210.181.21</source_ip>
      <count>1</count>
      <policy_evaluated>
        <disposition>none</disposition>
        <dkim>pass</dkim>
        <spf>fail</spf>
        <reason>
          <type>sampled_out</type>
          <comment></comment>
        </reason>
      </policy_evaluated>
    </row>
    <identifiers>
      <header_from>hostspectra.com</header_from>
    </identifiers>
    <auth_results>
      <dkim>
        <domain>hostspectra.com</domain>
        <result>pass</result>
      </dkim>
      <spf>
        <domain>hostspectra.com</domain>
        <result>softfail</result>
      </spf>
    </auth_results>
  </record>
</feedback>

Note:
- Hostspectra.com using IP 195.154.58.245 but hostname IP is 62.210.181.21
- Report as SPF fail because sending via 62.210.181.21 instead 195.154.58.245
- Solution for this situation:
1. Add /var/qmail/control/outgoingip with content 195.154.58.245 --> so, sending always via 195.154.58.245, or
2. Add 'Additional IP For SPF (one Per Line)' in 'Email Auth' for all IPs, or
3. Add 'A record' for IP 62.210.181.21 for all domains (better via dns template and then rebuilt)
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

 


MRatWork Affiliates:    BIGRAF(R) Inc.    House of LMAR    EFARgrafix
Click Here

Page created in 0.066 seconds with 19 queries.

web stats analysis