Since most of our lists are used as moderated distribution lists and are
synchronized via scripts, it wasn't very difficult.
You have your standard mailman list aliases - which we partition into their
own alias file /etc/mail/aliases.mailman
fubar:"|/opt/mailman/mail/wrapper post fubar"
fubar-
Aaron,
You should be able to extract it from the log files
in ~mailman/logs/subscribe using grep
Scott
l'
I've manually added the types that are needed in my environment, but it
would be nice to see the code updated so I don't have to reapply the change
with each incremental update.
I'm currently at version 2.0.8
Thanks,
Scott
=
That's about as descriptive as I can get regarding
my problem.
The scenario is this -
I've replaced pipermail with the updated hypermail
package and I've done this by subscribing a special user to each list and
setting
ARCHIVE_TO_MBOX=1
PUBLIC_EXTERNAL_ARCHIVER=0
PRIVATE_EXTERNAL_ARCHIVER=0
I just discovered somewhat odd behavior in
mailman-2.0.7. When sending to the list, it only used my "From" address and
failed to honor the "Reply-To" header. While I don't have a problem with it
using "From" to determine whether a posting should be held for a moderated list,
I was wondering
Does anyone have any ideas about using RADIUS to override internal mailman
password authentication for addresses inside the domain? We'd really like
our users to be able to have single sign-on.
Thanks,
Scott
--
Mailman-Users maillist - [EMA
