In view of Stephen Turnbull's comments, I changed my mind and will
respond to the list. I was the "original poster" (OP?) about the
strange "group mismatch" error in my log. It complained about the user
"baron" (my own account on the server) not matching the required list
of groups. Several people
Christian Buser via Mailman-Users writes:
> You know that in a mailing list everyone should help if he can and
> not only consume?
Technically correct, but please don't be so antagonistic.
> So then, please unsubscribe here.
What you do with your own filters is your business, but for the
Ah so…
You found another way to fix the main problem - but you do not tell us?
You know that in a mailing list everyone should help if he can and not only
consume?
So then, please unsubscribe here.
Thank you
Christian
--
Christian Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)
I would like to thank everyone for all the ideas about my
group-mismatch problem.
As it happens, nothing helped. Moreover, almost all of the
speculations about what I was doing or not doing, using or not using,
know or do not know, were incorrect.
I found another way to fix the main problem,
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
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
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
> 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/
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
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'.
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:
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
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
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
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:
On 5/15/22 16:35, Jon Baron wrote:
I'm sure this is a very dumb question, because I have seen several
posts about it, all of which imply that there is some simple solution.
I am trying to use spamassassin by running everything through
/etc/procmail, and I get the following in /var/log/procmail:
On 10/25/2020 11:48 AM, Mark Sapiro wrote:
> On 10/25/20 7:37 AM, Dennis Putnam wrote:
>
>> This is still a bit confusing. I need to state that 'fetchmail' is
>> involved here. I don't know how it interfaces but I have the
>> 'postmaster' parameter in 'fetchmailrc' set to 'mailman'. This was not
On 10/25/20 7:37 AM, Dennis Putnam wrote:
> This is still a bit confusing. I need to state that 'fetchmail' is
> involved here. I don't know how it interfaces but I have the
> 'postmaster' parameter in 'fetchmailrc' set to 'mailman'. This was not
> an issue with the previous version of mailman so
On 10/24/2020 6:57 PM, Mark Sapiro wrote:
> On 10/24/20 3:10 PM, Dennis Putnam wrote:
>> I am getting this error:
>>
>> (expanded from ):
>> Command died with status 2: "/usr/lib/mailman/mail/mailman post
>> cufsalumni". Command output: Group mismatch error. Mailman expected the
>>
On 10/24/20 3:10 PM, Dennis Putnam wrote:
> I am getting this error:
>
> (expanded from ):
> Command died with status 2: "/usr/lib/mailman/mail/mailman post
> cufsalumni". Command output: Group mismatch error. Mailman expected the
> mail wrapper script to be executed as group
20 matches
Mail list logo
