-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(Yahoo!) "Unresolvable RFC.5321 from domain" section updated
- Loading branch information
1 parent
72abb9d
commit b4807ce
Showing
1 changed file
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -71,16 +71,16 @@ RFC compliance failures | |
□ Incorrect mime types | ||
□ …and more | ||
|
||
Unresolvable RFC.5321 from domain | ||
Unresolvable RFC.5321 or RFC.5322 from domain | ||
|
||
• These errors indicate that the domain used to the right of the @ in the | ||
MAIL FROM does not appear to be a real domain. | ||
MAIL FROM or HEADER FROM does not appear to be valid. | ||
This comment has been minimized.
Sorry, something went wrong.
azumakuniyuki
Author
Owner
|
||
• We determine if the domain name exists by using an SOA query; therefore, if | ||
multiple subdomains are used in MAIL FROM commands, then besides setting up | ||
a DNS A or MX record (perhaps using a wildcard), then SOA records must be | ||
set up as well. | ||
• This error can be returned as either a timeout/servfail (451) or a permfail | ||
(554) | ||
multiple subdomains are used in MAIL FROM or HEADER FROM commands, then | ||
besides setting up a DNS A or MX record (perhaps using a wildcard), then | ||
SOA records must be set up as well. | ||
• These errors can be returned as either a timeout/servfail (451) or a | ||
permfail (554) | ||
|
||
This comment has been minimized.
Sorry, something went wrong.
azumakuniyuki
Author
Owner
|
||
Excessive user complaints | ||
|
||
|
This comment has been minimized.
Sorry, something went wrong.
azumakuniyukiMay 29, 2024
Author Owner