thon.org
> Subject: Re: [Mailman-Users] New list's SMTP failures
>
> On 11/01/2017 09:19 AM, Nick Wyman wrote:
> >
> > I now think this is due to a spam email which was sent to
> mail...@mydomain.com (it's stuck in my mail queue) which is somehow
> erroneously b
Sapiro [mailto:m...@msapiro.net]
> Sent: Wednesday, November 01, 2017 1:26 PM
> To: Nick Wyman ; Mailman Users us...@python.org>
> Subject: Re: [Mailman-Users] New list's SMTP failures
>
> On 11/01/2017 11:00 AM, Nick Wyman wrote:
> >
> > This is not cpanel. This i
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] New list's SMTP failures
>
> On 11/01/2017 07:41 AM, Nick Wyman wrote:
> >
> > On a server which hosts several mailman lists, a new list is exhibiting odd
> behavior for owner email addresses. There a
Hello,
On a server which hosts several mailman lists, a new list is exhibiting odd
behavior for owner email addresses. There are two owners, and both are
receiving post emails, but are also bouncing what I assume are administrative
emails.
The smtp-failure log looks like:
Nov 01 09:37:09 20
>
> What group is GID 38?
>
> I would expect the wrapper to see the effective GID is that of "list"
> and the real GID is that of "www-data" and then to be trying to set the
> real GID to be the effective GID.
>
Yes, sorry, that was captured when I tried setting the apache gid to 38 (list
grou
> > Why this would start occurring following an OS update, I
> > don't know. Possibly it is some apparmor config or something similar.
>
> Or SELinux became enabled?
>
I've been able to eliminate apparmor (disabled) and selinux (not installed).
The setregid call simply returns -1. What is od
Mark,
Thank you for looking.
> The error is "Operation not permitted". My best guess is this is
> occurring at this point in the wrapper
>
> #ifdef HAVE_SETREGID
> status = setregid(getegid(), -1);
> if (status)
> fatal(logident, SETREGID_FAILURE, "%s", strerror(e
Hello,
I have an Ubuntu 14.04 server running apache2.4 and mailman. This server has
been running a few lists with no problems for over a year. After updating some
Ubuntu packages for security maintenance (unfortunately I don't know all that
changed, but apache2 and mailman were unaltered), th
