McAfee SMEFCE-AI-DA Administration Guide - Page 84

Create an Enforced SPF Domain, Add », « Remove

Get McAfee SMEFCE-AI-DA - Email Security Service Inbound PDF manuals and user guides View all McAfee SMEFCE-AI-DA manuals
Add to My Manuals
Save this manual to your list of manuals

Page 84 highlights

Email Authentication Email Protection Administrator Guide • Nothing prevents spammers and hackers from implementing SPF, so it is not a reliable spam indicator - Many organizations allow third parties to send mail on behalf of their domain (authorized spoofing). These third parties must be authorized by the domain owner as part of their SPF records in order for recipients to successfully validate the third party messages. • Hosted email providers often give the same SPF records to all their customers, making it impossible to distinguish one customer from the another, thus reducing usefulness of the technology. • Even when SPF is implemented and enforced, it is still possible for spammers to create very convincing spoofed emails; therefore, continued user training and caution is advised. Create an Enforced SPF Domain Go to the Email Authentication | Enforced SPF tab and complete the following information to implement an SPF domain. To enter values for the SPF domain list, enter the full address of the Sender domain and/or sub-domain, or use part of the domain using wildcards. Any Sender domain or subdomain must be explicitly specified for enforced SPF. Specifying a Sender domain doesn't automatically include any sub-domains of that domain. Examples of Wildcard use include any of the following: • *.example.com • example.* • mysubdomain.*.* • subdomain.*.example.com 1 Click the Add » button. The value is added to the list box. Note: The maximum number of values allowed in the Add Domain list is 1500. This limit is defined at the system level. Any duplicate or invalid values are discarded automatically. 2 To remove a value from the list, select it in the list box and click the « Remove button. Note: To select more than one value from the list, press Ctrl on your keyboard, click each entry you want to remove, and then click the « Remove button. 76 Proprietary: Not for use or disclosure outside McAfee without written permission. November 2012

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
Email Authentication
Email Protection Administrator Guide
76
Proprietary:
Not for use or disclosure outside McAfee without written permission.
November 2012
•
Nothing prevents spammers and hackers from implementing SPF, so it is not a
reliable spam indicator - Many organizations allow third parties to send mail on behalf
of their domain (authorized spoofing). These third parties must be authorized by the
domain owner as part of their SPF records in order for recipients to successfully
validate the third party messages.
•
Hosted email providers often give the same SPF records to all their customers, making
it impossible to distinguish one customer from the another, thus reducing usefulness
of the technology.
•
Even when SPF is implemented and enforced, it is still possible for spammers to
create very convincing spoofed emails; therefore, continued user training and caution
is advised.
Create an Enforced SPF Domain
Go to the Email Authentication
| Enforced SPF tab and complete the following
information to implement an SPF domain.
To enter values for the SPF domain list, enter the full address of the Sender domain and/or
sub-domain, or use part of the domain using wildcards. Any Sender domain or subdomain
must be explicitly specified for enforced SPF. Specifying a Sender domain doesn't
automatically include any sub-domains of that domain. Examples of Wildcard use include
any of the following:
•
*.example.com
•
example.*
•
mysubdomain.*.*
•
subdomain.*.example.com
1
Click the
Add »
button. The value is added to the list box.
Note: The maximum number of values allowed in the Add Domain list is 1500. This limit is defined
at the system level. Any duplicate or invalid values are discarded automatically.
2
To remove a value from the list, select it in the list box and click the
« Remove
button.
Note: To select more than one value from the list, press Ctrl on your keyboard, click each entry
you want to remove, and then click the « Remove button.