postfix check warns about symlink being group writable

Looking into git, this problem seem to have been introduced with the 3.0.0 release:

$ git remote -v
origin https://git.launchpad.net/postfix (fetch)
origin https://git.launchpad.net/postfix (push)

$ git show 5afd7bb2 -- conf/postfix-script | sed -n '59,81 p'
+ todo="$config_directory/."
+ test -n "$check_shared_files" && {
+ todo="$daemon_directory/. $meta_directory/. $todo"
+ test "$shlib_directory" = "no" ||
+ todo="$shlib_directory/. $todo"
+ }
+ todo=`echo "$todo" | tr ' ' '\12' | sort -u`

  find $todo ! -user root \
- -exec $WARN not owned by root: {} \;
+ -exec $WARN not owned by root: {} \;

- todo="$config_directory/."
- test -n "$check_shared_files" && todo="$daemon_directory/. $todo"
+ find $todo \( -perm -020 -o -perm -002 \) \
+ -exec $WARN group or other writable: {} \;

- find $todo \
- \( -perm -020 -o -perm -002 \) -type f \
- -exec $WARN group or other writable: {} \;
+ # Check Postfix mail_owner-owned directory tree owner/permissions.

  find $data_directory/. ! -user $mail_owner \

In the above, the "-type f" argument of the last find was dropped causing the issue.

This was fixed in 3.1.4-2 which was synced into ubuntu for zesty and later.

Xenial does indeed show this behavior, but I don't think it's worth an SRU to fix it. The exit code is still 0, and it's just a warning.

Maybe if there was another bug worth of an SRU, this fix could piggy back on it.

FWIW, the fix is in debian/patches/70_postfix-check.diff:
--- a/conf/postfix-script
+++ b/conf/postfix-script
@@ -302,9 +302,14 @@
  find $todo ! -user root \
      -exec $WARN not owned by root: {} \;

- find $todo \( -perm -020 -o -perm -002 \) \
+ # Handle symlinks separately
+ find -L $todo \( -perm -020 -o -perm -002 \) \
      -exec $WARN group or other writable: {} \;

+ find $todo -type l | while read f; do \
+ readlink "$f" | grep -q / && $WARN symlink leaves directory: "$f"; \
+ done; \
+
  # Check Postfix mail_owner-owned directory tree owner/permissions.

  find $data_directory/. ! -user $mail_owner \

Status changed to 'Confirmed' because the bug affects multiple users.

I am setting the xenial bug to wontfix because xenial is no longer under its standard support period.