TGPlatt, WebMaster wrote:
I'm pleased to report my mailman archive update process is working again. As
it turned out, what was keeping the feature from working was ownership
and/or permissions on files in /usr/mailman/archives/private/[LISTNAME] and
TGPlatt, WebMaster wrote:
I've probably just misunderstood something here. When you helped me with my
setup in July, you had me create a mailman directory in the user's web space
and we used that directory somehow. I've forgotten the exact reason we did
that now but I vaguely recall it had
TGPlatt, WebMaster wrote:
Now that my archiver is working again, I have several files in qfiles/shunt
that I'd like to recover and convince mailman to insert into my (now
working) October archive. If it's possible to do so, I also have a few
shunted files from the end of September that I'd like
As usual, you're right, Mark. That fixed it. As a result, I was able to
recover at least some of the archived messages from September and many of
the October messages that occurred during the resurrection and testing
period too.
My trouble here was I could find no docs about shunt to guide me
Thanks, Mark. That's all I needed to know!
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Friday, October 31, 2008 12:59 AM
To: [EMAIL PROTECTED]; mailman-users@python.org
Subject: RE: [Mailman-Users] What happened to my archive? Why isn't the
archive process
Hello,
is there a possibility to add, in the email template sent to the list
owner when someone is deleted, the REASON (BYBOUNCE etc) ?
--
Fil
--
Mailman-Users mailing list
Mailman-Users@python.org
TGPlatt, WebMaster wrote:
My trouble here was I could find no docs about shunt to guide me and never
realized unshunt existed until I saw your note. I went for help to the only
place I knew of where mailman's command line utilities were listed:
www.gnu.org/software/mailman/site.html Shunt isn't
Fil wrote:
is there a possibility to add, in the email template sent to the list
owner when someone is deleted, the REASON (BYBOUNCE etc) ?
This is a good suggestion. I'll add it in 2.2 to include the 'whence'
argument to ApprovedDeleteMember() which is a phrase like 'email
confirmation', 'web
Hello,
I've enabled mailing lists with Mailman 2.1.2 and Postfix in a Mac OS
X Server 10.3.9
I've the following errors when a subscribed user sent a post to the list:
logs/smtp
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008
So I didn't have the entry for POSTFIX_STYLE_VIRTUAL_DOMAINS in my
mm_cfg.py file.
So I added the following:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['www.second-domain.com']
Ran /bin/genaliases, no errors
Mail still bounces with the following:
Your message did not reach some or all of the
NetBiker wrote:
I've enabled mailing lists with Mailman 2.1.2 and Postfix in a Mac OS
X Server 10.3.9
Search the FAQ Wiki for mac os x.
I've the following errors when a subscribed user sent a post to the list:
logs/smtp
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
faisal anif wrote:
is there a kind of temporary files that mailman doesn't cleanup? what can I do?
No. The only files are the queue files which hold the message as it is
processed and the archives. The queue files are removed when message
processing is complete.
As Brad says, you need to
John Gray wrote:
But the mailman cron jobs didn't run for about a week.
Is there a way for get senddigets to send out the digests for the
missing days?
Or did senddigest send everything since the last digest?
There should be no missing digests. Assuming no digest was triggered on
'size' when
Brad Knowles wrote:
NetBiker wrote:
I've the following errors when a subscribed user sent a post to the list:
logs/smtp
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
associated with nodename')
Oct 30 16:52:39 2008 (378) All recipients refused: (7, 'No address
Scott Race wrote:
So I didn't have the entry for POSTFIX_STYLE_VIRTUAL_DOMAINS in my
mm_cfg.py file.
So I added the following:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['www.second-domain.com']
This domain has to match the host_name attribute of the list (the
'email host', not the 'url host'). It
Thanks, fixed the domain name in the mm_cfg.py to read ['second-domain.com'].
Running the /bin/genaliases doesn't return an error, but doesn't generate the
/data/virtual-mailman file. The mailman error logs don't show anything (no
errors since Oct 22).
Sounds like the virtual-mailman file
Scott Race wrote:
Thanks, fixed the domain name in the mm_cfg.py to read ['second-domain.com'].
Running the /bin/genaliases doesn't return an error, but doesn't
generate the /data/virtual-mailman file. The mailman error logs don't
show anything (no errors since Oct 22).
Sounds like the
Thanks for the reply - so this will be a multiple mailman domain.
Currently list working on first-domain.org, trying to get it working on
second-domain.org.
So yes, Host name this list prefers for email is correct as
second-domain.org.
My mm_cfg.py looks like this:
from socket import *
Scott Race wrote:
Thanks for the reply - so this will be a multiple mailman domain.
Currently list working on first-domain.org, trying to get it working on
second-domain.org.
So yes, Host name this list prefers for email is correct as
second-domain.org.
My mm_cfg.py looks like this:
Sorry bout that...yes, RHLE server.
/etc/postfix/main.cf has the following (in reference to the questions
below):
virtual_alias_maps = hash:/etc/postfix/virtual_alias_maps
virtual_alias_domains = hash:/etc/postfix/mydomains
alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases
With your
Now just hit one more slight snag, can no longer create new lists on the
second-domain.org.
Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a bug!
Error.
/var/log/mailman error shows:
admin(14722): RuntimeError: command failed: /usr/sbin/postmap
/etc/mailman/virtual-mailman
Scott Race wrote:
Sorry bout that...yes, RHLE server.
It isn't a question of the OS, but rather whether Mailman was
configured and installed from our source distribution or from a RedHat
RPM which differs significantly in terms of where things are found.
With your direction, realizing I
Scott Race wrote:
Now just hit one more slight snag, can no longer create new lists on the
second-domain.org.
Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a bug!
Error.
/var/log/mailman error shows:
admin(14722): RuntimeError: command failed: /usr/sbin/postmap
Checked the permissions:
Mailman directory:
drwxrwsr-x 2 root mailman4096 Oct 31 16:41 mailman
Alias files:
-rw-rw-rw- 1 root mailman 12582 Oct 31 16:41 aliases
-rw-rw-rw- 1 root mailman 24576 Oct 31 16:41 aliases.db
-rw-rw 1 apache mailman 3689 Oct 31 16:41
I'm running MM 2.1.11 on Debian Etch4.0r3 with Postfix 2.3.8. I hesitate to
explain how I made this work... In fact perhaps I shouldn't. It could jinx
me. But in our case, I've got the individual LOCAL virtual email addresses
for each domain defined in the /etc/postfix/virtual file and I've
TGPlatt, WebMaster wrote:
VIRTUAL_HOSTS = {'firstdomain.net':'firstdomain.net',
'seconddomain.com':'seconddomain.com',
'thirddomain.com':'thirddomain.com'}
Just FYI the abbove is EXACTLY eqiivalent to
VIRTUAL_HOSTS = {}
add_virtualhost('firstdomain.net',
26 matches
Mail list logo
