Bug#882324: amavisd-new doesn't honor "originating" configuration flag, contrary to documentation

2019-04-01 Thread Laurent Bigonville
severity 882324 serious thanks On Tue, 21 Nov 2017 13:40:24 + Karim Malhas wrote: > Dear Maintainer, > > amavisd-new contains detailed documentation about using the "originating" flag[0], > but this is not actually supported. > > A solution[1] has been posted to the amavisd mailing list,

Bug#882324: amavisd-new doesn't honor "originating" configuration flag, contrary to documentation

2019-02-28 Thread Bernhard Schmidt
Control: tags -1 + patch confirmed fixed-upstream Control: forward -1 https://gitlab.com/amavis/amavis/issues/6 On Wed, Feb 14, 2018 at 03:06:10PM +, Karol Augustin wrote: Hi, > Recently I hit this bug and following that I have written summary on > amavis-users mailing list: > >

Bug#882324: amavisd-new doesn't honor "originating" configuration flag, contrary to documentation

2018-02-14 Thread Karol Augustin
Hi, Recently I hit this bug and following that I have written summary on amavis-users mailing list: https://lists.amavis.org/pipermail/amavis-users/2018-February/005292.html Giovanni, the author of original patch, provided updated patch for that issue. I have confirmed my suspicion that

Bug#882324: amavisd-new doesn't honor "originating" configuration flag, contrary to documentation

2017-11-21 Thread Karim Malhas
Package: amavisd-new Version: 1:2.11.0-1 Severity: important Tags: upstream Dear Maintainer, amavisd-new contains detailed documentation about using the "originating" flag[0], but this is not actually supported. A solution[1] has been posted to the amavisd mailing list, but has been without