But yes, I think both the to and from email addresses must be reachable from outside your network. Though that probably is not sufficient.
Another thing I thought of is Sender Policy Framework (SPF). For example, if you have the dig command look at the TXT record returned by these commands:
Your domain may need an SPF TXT record in DNS.
But if your IP address is in a range owned by an ISP like Verizon or Comcast, I still don't think Google will ever except SMTP traffic from you unless you authenticate the connection with a username and password. That's what the SMART_HOST option and access database do.
Hi gurus!
I need help to make sendmail to accept unknown user mail. That is if the user does not exist sendmail keep on processing the mail and store it in a some mailbox ...
Thanks for any idea! (5 Replies)
Hi,
yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email,
This happened with sendmail on solaris 10 and also with sendmail on a linux box.
Found it is something to do with DNS blacklists,
following lists did not work for me,... (2 Replies)
Hi Team,
I have a script written to sendmail along with attachment in html format.
The code is
export MAILFROM="abc@abc.com"
export MAILTO="abc@abc.com"
export CONTENT="./GRP_SPI_ERR.html"
export SUBJECT="TEST EMAIL: TESTING HTML"
{
print - "From: $MAILFROM"
print - "To: ${MAILTO}"... (3 Replies)
Hi, Guru
i had configure in my two server to send out the email.
One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all.
below is the syslog when i try to send out the mail.
GOOD Server
Dec 28 11:29:39... (5 Replies)
Hi all,
we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent..
Thanks in advance.. (1 Reply)
My aix boxes have the port 25 listening and I want to bock that. But before that I want to check the recent logs of the sendmail activity and any open sockets using the port. Please advise. (1 Reply)
Hi Every One,
one of our server configuration on sendmail config
we are using SMAR_HOST
###
define(`SMART_HOST', 'mail.xxx.com')
and /etc/sysconfig/sednmail DAEMON is setted to NO
so let me know why sendmail is not working for this server
any this else u need please do let me know (0 Replies)
One of the applications sends mail to the users on daily basis. It sends mail within (internal users) the firewall (e.g., username@companyname.com) and not sending mail outside (external users) the firewall (e.g., username@yyyy.com). When we contacted the admin people they informed us to register... (5 Replies)
Hi,
I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Dear All ,
I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine.
But suddenly there was an issue , the SMTP takes the IP of the bond1 interface.
So the IP could not get validated in the relay server.
So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
LEARN ABOUT CENTOS
mail::spamassassin::plugin::spf
Mail::SpamAssassin::Plugin::SPF(3) User Contributed Perl Documentation Mail::SpamAssassin::Plugin::SPF(3)NAME
Mail::SpamAssassin::Plugin::SPF - perform SPF verification tests
SYNOPSIS
loadplugin Mail::SpamAssassin::Plugin::SPF
DESCRIPTION
This plugin checks a message against Sender Policy Framework (SPF) records published by the domain owners in DNS to fight email address
forgery and make it easier to identify spams.
USER SETTINGS
whitelist_from_spf user@example.com
Works similarly to whitelist_from, except that in addition to matching a sender address, a check against the domain's SPF record must
pass. The first parameter is an address to whitelist, and the second is a string to match the relay's rDNS.
Just like whitelist_from, multiple addresses per line, separated by spaces, are OK. Multiple "whitelist_from_spf" lines are also OK.
The headers checked for whitelist_from_spf addresses are the same headers used for SPF checks (Envelope-From, Return-Path, X-Envelope-
From, etc).
Since this whitelist requires an SPF check to be made, network tests must be enabled. It is also required that your trust path be
correctly configured. See the section on "trusted_networks" for more info on trust paths.
e.g.
whitelist_from_spf joe@example.com fred@example.com
whitelist_from_spf *@example.com
def_whitelist_from_spf user@example.com
Same as "whitelist_from_spf", but used for the default whitelist entries in the SpamAssassin distribution. The whitelist score is
lower, because these are often targets for spammer spoofing.
ADMINISTRATOR OPTIONS
spf_timeout n (default: 5)
How many seconds to wait for an SPF query to complete, before scanning continues without the SPF result.
do_not_use_mail_spf (0|1) (default: 0)
By default the plugin will try to use the Mail::SPF module for SPF checks if it can be loaded. If Mail::SPF cannot be used the plugin
will fall back to using the legacy Mail::SPF::Query module if it can be loaded.
Use this option to stop the plugin from using Mail::SPF and cause it to try to use Mail::SPF::Query instead.
do_not_use_mail_spf_query (0|1) (default: 0)
As above, but instead stop the plugin from trying to use Mail::SPF::Query and cause it to only try to use Mail::SPF.
ignore_received_spf_header (0|1) (default: 0)
By default, to avoid unnecessary DNS lookups, the plugin will try to use the SPF results found in any "Received-SPF" headers it finds
in the message that could only have been added by an internal relay.
Set this option to 1 to ignore any "Received-SPF" headers present and to have the plugin perform the SPF check itself.
Note that unless the plugin finds an "identity=helo", or some unsupported identity, it will assume that the result is a mfrom SPF check
result. The only identities supported are "mfrom", "mailfrom" and "helo".
use_newest_received_spf_header (0|1) (default: 0)
By default, when using "Received-SPF" headers, the plugin will attempt to use the oldest (bottom most) "Received-SPF" headers, that
were added by internal relays, that it can parse results from since they are the most likely to be accurate. This is done so that if
you have an incoming mail setup where one of your primary MXes doesn't know about a secondary MX (or your MXes don't know about some
sort of forwarding relay that SA considers trusted+internal) but SA is aware of the actual domain boundary (internal_networks setting)
SA will use the results that are most accurate.
Use this option to start with the newest (top most) "Received-SPF" headers, working downwards until results are successfully parsed.
perl v5.16.3 2011-06-06 Mail::SpamAssassin::Plugin::SPF(3)