[Mailman-Users] Re: group mismatch

2022-05-16 Thread Mark Sapiro
On 5/16/22 19:27, Carl Zwanzig wrote: On 5/16/2022 4:31 PM, Mark Sapiro wrote: That's a Debian 'feature'. Which then makes me wonder if there are other Debian "features" getting in the way. No. It's a simple group mismatch. The OP has to arrange for the process that pipes the mail to

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Stephen J. Turnbull
Lucio Chiappetti writes: > On Sun, 15 May 2022, Jon Baron wrote: > > > I am trying to use spamassassin by running everything through > > /etc/procmail, > > Sorru, I do not understand what procmail and spamassassin, intended to > process INCOMING mail, have to do with mailman which is

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Carl Zwanzig
On 5/16/2022 4:31 PM, Mark Sapiro wrote: That's a Debian 'feature'. Which then makes me wonder if there are other Debian "features" getting in the way. z! -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Julian H. Stacey
> Also: procmail is antique abandonware that no one should use in 2022, > but it can be very hard to replace. I have a massive time investment in working procmail rules. Use is not abandoned here. "If it aint broke dont fix it." ;-) Cheers, -- Julian Stacey http://berklix.com/jhs/

[Mailman-Users] Re: group mismatch

2022-05-16 Thread dmitri maziuk
On 2022-05-16 3:31 PM, Bill Cole wrote: ... SpamAssassin can be used as a milter during the SMTP transaction or as a filter in the delivery pipeline via a delivery agent like procmail. Using procmail is generally suboptimal, but it may be the only mechanism available for an end user to deploy

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Mark Sapiro
On 5/16/22 16:18, Carl Zwanzig wrote: One thing is odd about the message above, it says "one of the groups" whereas some versions (eg 2.1.25) have "Mailman expected the %s wrapper to be executed as group" (singular). Could be that the OP's version is rather old. That's a Debian 'feature'.

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Carl Zwanzig
Going back to the original email- On 5/15/2022 4:35 PM, Jon Baron wrote: "Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group:

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Bill Cole
On 2022-05-16 at 12:32:54 UTC-0400 (Mon, 16 May 2022 18:32:54 +0200 (CEST)) Lucio Chiappetti is rumored to have said: On Sun, 15 May 2022, Jon Baron wrote: I am trying to use spamassassin by running everything through /etc/procmail, Sorru, I do not understand what procmail and

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Lucio Chiappetti
On Sun, 15 May 2022, Jon Baron wrote: I am trying to use spamassassin by running everything through /etc/procmail, Sorru, I do not understand what procmail and spamassassin, intended to process INCOMING mail, have to do with mailman which is SENDING OUT mail. I still have a few almost-dead

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Carl Zwanzig
On 5/16/2022 3:42 AM, Jon Baron wrote: procmail is not "running". It is not listed in any version of "ps". It is evoked by sendmail or by /etc/aliases.db. sendmail and aliases.db are both owned by root and smmsp. It is "run" or "envoked" on-demand by sendmail to execute the line in the

[Mailman-Users] Re: group mismatch

2022-05-16 Thread Jon Baron
Thanks to both. But I'm afraid that this advice does not help, and I am giving up. I suspect that what I am trying to do is impossible. And I also think I was going about it wrong. I was trying to use /etc/aliases to get the mail to go to procmail, with lines like this: Method 1 jdm-society: