Restricting delegation user list per project?

Stephen Finucane stephen at that.guru
Mon May 15 19:05:59 AEST 2017


On Thu, 2017-05-11 at 15:41 -0700, Florian Fainelli wrote:
> On 05/11/2017 09:58 AM, Florian Fainelli wrote:
> > > Yup, that feature was flawed so it has been reverted for v2.0.0
> > > and in the v1.1.2 hotfix. If you can upgrade (or ask your
> > > instance admin to upgrade) the instance to v1.1.2 or greater,
> > > this will resolve this issue for you.
> > 
> > Yes, seems to be all good now, thanks both!
> 
> OK, now I am seeing something strange with v1.1.3, I have postfix
> configured to deliver emails to
> > /var/www/patchwork/patchwork/bin/parsemail.sh
> 
> postifx reports that the delivery is OK, but the patches do not show
> up in patchwork.
> 
> If I take the patch as received by the mailing-list and cat *.patch |
> /var/www/patchwork/patchwork/bin/parsemail.sh everything works okay.
> 
> It is possible that commit 6703cb52f9338cf502b6b4167aacb8d3bdf7d69e
> ("parser: parse headers containing invalid characters or codings")
> would
> be responsible for that?
> 
> I can't quite explain the different in behavior between postfix
> delivery versus shell invocation.
> 
> The log between v1.1.0 and v1.1.3 against patchwork/bin/parsemail.py
> does not show anything peculiar that would seem relevant here.
> 
> Any clues what could be going on?

I'm afraid I've little to no insight into this as I don't use the
postfix model myself. You'll have to do a little work here yourself, I
guess, probably starting with reverting the patch above (though I also
fail to see what could be happening here).

Have you checked the postfix logs? Looks like there's a good deal of
information available there http://www.postfix.org/DEBUG_README.html

Stephen


More information about the Patchwork mailing list