Dear Sir,
Whenever an email is sent to my list I get this :
[listname]-bou...@mydomain.com ON BEHALF [email] in the mail header
Is there a way to get rid of this and put just [email].
Plus how can anyone send emails to the list without the process of approving
and confirming and stuf
Hi,
I am trying to set up a mailman server and having some real difficulties.
Details:
Using CentOS 5.2
MTA = Postfix
I have postfix working, i can log into my user and send and receive
messages. I then installed mailman and started configuring based on
this page:
http://forums.fedoraforum.org
I searched the archives, but couldn't find this question answered there.
Is there a way, as the list admin for a number of Mailman-run email
lists, to find if someone is subscribed to multiple lists?
Thanks,
Evan
--
-
Evan Perkins
Operations Director
KGNU Community Radio
88.5 FM Boulder, 1
On 3/3/2009 7:30 PM, Mark Sapiro wrote:
If this is a 'large' list, you could easily make a Mailman list and
pipe the output of bin/list_owners into bin/sync_members to keep the
list current.
Might this be an idea for a ""virtual (dynamic) list that is a list of
all the list owners? Say somet
On Tue, Mar 03, 2009 at 05:30:10PM -0800, Mark Sapiro wrote:
> Alan Rubin wrote:
> >
> >Just curious if the community has a Standard Operating Procedure for
> >list administrators to notify list owners when there are changes to the
> >Mailman installation. Maybe like a list of list owners?
>
>
Alan Rubin wrote:
>
>Just curious if the community has a Standard Operating Procedure for
>list administrators to notify list owners when there are changes to the
>Mailman installation. Maybe like a list of list owners?
Other people may have other ideas. I'm not aware of any Best Current
Practi
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>In looking over my recursive listing closely, I see that there are 501
>total digest.mboxes out there (!). All of them are 30K or under.
>
>
>>>That still doesn't explain why they are all still there and nothing
>was
>>>delivered when I ran the cron job
Hello,
Just curious if the community has a Standard Operating Procedure for
list administrators to notify list owners when there are changes to the
Mailman installation. Maybe like a list of list owners?
Regards,
Alan Rubin
Technician Unix
DCS Midrange Services
Phone: +61 (08) 8999 5111
Fax:
>Mark Sapiro wrote:
>You need the cron job because nothing else in Mailman sends digests
>periodically. The only other mechanism sends a digest when the list's
>digest.mbox exceeds a certain size, which may not happen for weeks on
>a low traffic list.
Ok I understand 100% now. The only reason I
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>The digest messages are accumulated for a list in a mbox format file
>>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>>digest.mbox and the size of digest.mbox is now greater than the list's
>>digest_size_threshold, a digest is se
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>Running cron/senddigests will send a digest for any list which has a
>>digest.mbox file and for which digest_send_periodic=yes regardless of
>>how big the digest is.
>
>This is where we part ways.
>
>Without the senddigests cron job, isn't the above stat
>Mark Sapiro wrote:
>The digest messages are accumulated for a list in a mbox format file
>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>digest.mbox and the size of digest.mbox is now greater than the list's
>digest_size_threshold, a digest is sent at that time for that
>Mark Sapiro wrote:
>The digest messages are accumulated for a list in a mbox format file
>lists/LISTNAME/digest.mbox. When a new message arrives and is added to
>digest.mbox and the size of digest.mbox is now greater than the list's
>digest_size_threshold, a digest is sent at that time for that
Savoy, Jim wrote:
>
>All of our lists allow users to select the
>digest
>
>option ("digestable=yes"), and the digests are sent out when the 30k
>threshold is
>
>reached ("digest_size_threshold=30"). The next option asks if a digest
>should be
>
>sent out DAILY when the threshold isn't reached
>("di
Hi all,
I started a new thread for this as it no longer applies to cron, but
rather digests.
I just ran the senddigests cron option (again, for the first time ever)
but it didn't seem to do anything. I can't really understand what it
does anyway
(from the description given). All of ou
>> Jim Savoy wrote:
>>I will probably leave the gateway news stuff out forever. And also the
>>password reminder thing, as we don't want to bombard our students with
>>more info...
> Mark Sapiro wrote:
>Fair enough, although the sending of reminders is a list option. You
can set
>DEFAULT_SEND_R
Savoy, Jim wrote:
>
>>Mark Sapiro wrote:
>
>>For the others, you need to at least read the comments in crontab.in
>and understand what the job does before deciding not to run it.
>
>I will probably leave the gateway news stuff out forever. And also the
>password
>reminder thing, as we don't want to
>>Jim Savoy wrote:
>> I am not all that familiar with cron. Is that "crontab -u mailman
>>crontab.in" something you need to run every time you reboot the
system?
>>Or does it add something to /etc/cron.d or /etc/cron.daily or
/etc/crontab?
>>(I don't see anything new in those).
>Mark Sapiro wro
Oliver Glueck wrote:
>
>But bin/check_perms says, that everything is ok.
>It is an apache problem?
>
>
>/usr/local/mailman# ls -al archives/private/
>insgesamt 56
>drwxrws--- 14 root mailman 4096 2009-03-03 10:30 .
The archives/private/ directory must be either 'drwxrws--x' or owned by
the we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 3, 2009, at 4:43 AM, IEM - network operating center (IOhannes m
zmoelnig) wrote:
Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
The core question is whether /someone/ should be able to (easily)
set the List-ID, and I think we
Hi,
"Symbolic link not allowed or link target not accessible:
/usr/local/mailman/archives/public/about-ox.."
But I added:
--> Options +FollowSymLinks <---
AddDefaultCharset Off
What else?
Ari Moisio schrieb:
Hi
It looks like Apache issue. Look for Apache's access and error l
Hi
It looks like Apache issue. Look for Apache's access and error logs.
--
mr. M01510 & guide Loadstone-GPS
On Tue, 3 Mar 2009, Oliver Glueck wrote:
Hi,
if I click on the archive of a list, I get this error:
Forbidden
You don't have permission to access /pipermail/about-ox/ on this se
/usr/local/mailman/archives/public# ls -al
insgesamt 8
drwxrwsr-x 2 root mailman 4096 2009-03-03 10:30 .
drwxrwsr-x 4 root mailman 4096 2009-02-27 17:54 ..
lrwxrwxrwx 1 root mailman 44 2009-03-01 14:26 about-ox ->
/usr/local/mailman/archives/private/about-ox
Oliver Glueck schrieb:
Hi,
if I click on the archive of a list, I get this error:
Forbidden
You don't have permission to access /pipermail/about-ox/ on this server.
But bin/check_perms says, that everything is ok.
It is an apache problem?
/usr/local/mailman# ls -al archives/private/
insgesamt 56
drwxrws--- 14 root
Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
The core question is whether /someone/ should be able to (easily) set
the List-ID, and I think we agree the answer to that is "yes". You
state that command-line configuration would be fine for MM2, and I agree
with that too. :) I sti
25 matches
Mail list logo
