https://bugzilla.novell.com/show_bug.cgi?id=414666
User fnmueller@opensuse.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=414666#c14
--- Comment #14 from Felix-Nicolai Müller 2008-08-10 07:27:57 MDT ---
"That's probably a little much to expect in less than a week. "
All I want is something like a status update (see below).
"Second, the proposed solutions are untried and untested - I don't think it's a
good idea to rush into a deployment on a high volume mail server."
How do you know that? I personally was in contact with the suse.de postmaster
and his answer indicated that nothing will be done if I leave it up to just
him. I don't know how opensuse folks can talk internally to suse.de folks, I
don't know which way they want to go or how much priority is given to this
issue. And I need some safety to deploy my opensuse.org address, which I have
already used in congresses (not a good idea as it now turned out!).
This _is_ a highly critical issue if you give someone at a congress an
openuse.org emailaddress to show the flag and then this only causes problems.
"Third, AFAICS, this problem does not affect everyone with an @opensuse.org
alias - in fact, it is only a problem when your forwarding-to address is on a
mail-server with strict SPF enforcement."
Just plain wrong. The forwarding-from address / server is "the problem" (well,
not it SPF was properly supported by suse.de). Therefore, if you don't have
your opensuse.org address forwarded to a server you have complete control of -
you have a problem.
"There used to be a scheme called "trusted forwarders" for problems exactly
like
this, in fact the website is still up http://www.trusted-forwarder.org. I
don't know if it works anymore nor if anyone is using it, but you never know.
(the latest zone file is from february 2008)"
This only worked if all the mailservers using SPF would use it and trust this
list....
Baseline is:
We need a working opensuse.org address as soon as _possible_. And it seems
suse.de postmaster is the only one able to solve this for every opensuse member
with one change in his configuration.
In effect, every opensuse member can be hit by this. In effect, a problemfree
account might not work tommorrow if the provider changes his mind to use SPF
(which more and more are doing).
I know every change needs to be tested. I know it is sunday and I don't expect
an answer today. But slowing down and taking pressure away is no solution, nor
is it a solution to not use the opensuse.org address or for each member to run
his own mailserver. If presenting opensuse to the outside can be done in a good
way by having a sometimes working emailaddress.....
Fixing this asap and for everyone in a way that no action has to be taken by
each individual member is in the interest of opensuse, novell and suse and each
member.
Open communication and a status update from time to time would certainly keep
me calmer.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.