| Summary | not really a whups bug, but related to horde.org SPF record |
| Queue | Horde.org Servers |
| Queue Version | Other |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | chuck (at) horde (dot) org |
| Requester | stevens (at) stevens (dot) it |
| Created | 11/12/08 (6358 days ago) |
| Due | |
| Updated | 11/12/08 (6358 days ago) |
| Assigned | 11/12/08 (6358 days ago) |
| Resolved | 11/12/08 (6358 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Assigned
Queue ⇒ Horde.org Servers
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ not really a whups bug, but related to horde.org SPF record
Queue ⇒ Whups
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
<bugs@horde.org> came from address nazik.horde.org[216.24.166.85] and
it seems the SPF record for "horde.org" doesn't include that address.
horde.org descriptive text "v=spf1 mx a:mail.ammma.de
a:mail.riboflavin.net a:technest.org ip4:205.210.42.0/24
ip4:216.220.40.240/29 ip4:66.207.199.35/32 ~all"
Yes, this is a soft failure, but some software (e.g. whitelister)
rejects the email received if set in strict checking mode.