Sorry, I mixed up different problems in my last mail. We have tested it after SLES 11 SP3 was released. After that we give up, because it costs us to much time to analyse that. So we script it with postconf now.
As I can remember we have tested this after the 30.09.2013 where the last update for ./x86_64/postfix-2.9.4-0.15.1.x86_64.rpm was submitted. But as I have wrote in my first report, this problem first occurs after the following packages were changed @31. Jan (for SLES11SP2):
31. Jan yast2-mail-plugins-2.17.6-0.11.2.noarch.rpm 31. Jan yast2-mail-2.17.6-0.11.2.noarch.rpm 31. Jan yast2-mail-plugins-2.17.6-0.9.15_0.11.2.noarch.delta.rpm 31. Jan yast2-mail-2.17.6-0.9.15_0.11.2.noarch.delta.rpm
Am 20.11.2013 15:43, schrieb Federica Teodori:
On 20 November 2013 15:32, Thomas Fehr email@example.com wrote:
Do you have the bugzilla number of your bug avilable? If yes, I could at least check if it is assigned to the right person.
For sles11sp3 this is already sorted, see #833004
Mario, Hajo: For what i can see the packages are also already released for sp3: Could you make sure you are testing with the latest postfix version?