DenverD wrote:
On 05/07/2013 07:50 PM, Per Jessen wrote:
DenverD wrote:
On 05/07/2013 04:44 PM, Carlos E. R. wrote:
It turns out that it is suse mail service that is broken. They have implemented an SPF definition that does not include mx2.suse.de (and maybe others). Thus when my ISP sees those emails they get correctly rejected:
i wonder into where the SUSE/Novell/Attachmate/openSUSE/(other?) system did those rejects flow...and why were they not acted on?
They go back to "bugzilla_noreply@novell.com".
The reason they are not acted on is that
1) there most probably way too many and 2) what would you want to do?
maybe fix the spf in their DNS setup (if that is the problem)--i say because my host recently changed their stuff around and when they did i got bounce/rejects complaining....instead of shruging and ignoring them i worked the cause/problem until it was fixed..
Well, SPF is at least in the mix. The problem is that a mail is sent from bugzilla, from an IP-address listed in the SPF record for "novell.com". That's all very good right up until the mail goes to a "computer.org" or "opensuse.org" alias (for instance) and is _forwarded_ to the actual recipient address. Forwarding breaks SPF and a forwarding mail-server would need to use SRS to fix it.
no more rejects.
Plenty of other rejects - poorly configured mail-servers, greylisting, mailbox quotas, non-existent addresses, flawed anti-spam filters etc etc.
isn't that what (even) SUSE/openSUSE/whoever should do when they get "way too many" rejects?
Yes in principle, no in practice. For such mass-mail operations, it is really up to the recipient to make sure his address works. I know this sounds harsh, but it's simply a matter of resources and of who is best placed to investigate. -- Per Jessen, Zürich (14.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org