| Name : perl-Mail-DMARC
| |
| Version : 1.202.403.140
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : lp155.1.1
| Date : 2024-08-25 19:45:38
|
| Group : Unspecified
| Source RPM : perl-Mail-DMARC-1.202.403.140-lp155.1.1.src.rpm
|
| Size : 1.25 MB
| |
| Packager : https://www_suse_com/
| |
| Summary : Perl implementation of DMARC
|
Description :
This module is a suite of tools for implementing DMARC. It adheres to the
2013 DMARC draft, intending to implement every MUST and every SHOULD.
This module can be used by...
* MTAs and filtering tools like SpamAssassin to validate that incoming
messages are aligned with the purported sender\'s policy.
* email senders, to receive DMARC reports from other mail servers and display
them via CLI and web interfaces.
* MTA operators to send DMARC reports to DMARC author domains.
When a message arrives via SMTP, the MTA or filtering application can pass
in a small amount of metadata about the connection (envelope details, SPF
and DKIM results) to Mail::DMARC. When the *validate* method is called,
Mail::DMARC will determine if:
a. the header_from domain exists
b. the header_from domain publishes a DMARC policy
c. if a policy is published...
d. does the message conform to the published policy?
e. did the policy request reporting? If so, save details.
The validation results are returned as a Mail::DMARC::Result object. If the
author domain requested a report, it was saved to the Report Store. The
Store class includes a SQL implementation that is tested with SQLite, MySQL
and PostgreSQL.
There is more information available in the $result object. See
Mail::DMARC::Result for complete details.
Reports are viewed with the dmarc_view_reports program or with a web
browser and the dmarc_httpd program.
Aggregate reports are sent to their requestors with the dmarc_send_reports
program.
For aggregate reports that you have been sent, the dmarc_receive program
will parse the email messages (from IMAP, Mbox, or files) and save the
report results into the Report Store.
The report store can use the same database to store reports you have
received as well as reports you will send. There are several ways to
identify the difference, including:
* received reports will have a null value for report_policy_published.rua
* outgoing reports will have null values for report.uuid and
report_record.count
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/15.5/noarch |
