Re: [Mailman-Users] Updating MM 2.1.2 - 2.1.5 stucks

2004-06-28 Thread Frank Thommen
  update exits at this point, but the next time it is run, the error does not
  appear any more (- I have to run 'update' three times to get rid of all these
  errors).  These errors always appear, when 'update' is run after MM 2.1.2 has
  been used.
 
 OK. You have done with update to 2.1.5. Don't go back to 2.1.2.


I cannot use 2.1.5:  It does not deliver any mails after giving me the
following errors (around 20 times) at start time:

---
# mailmanctl start
Starting Mailman's master qrunner.
# Traceback (most recent call last):
  File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 270, in ?
main()
  File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 230, in main
qrunner.run()
  File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 70,
in run
filecnt = self._oneloop()
  File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 99,
in
_oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
  File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Switchboard.py, line
147, in
dequeue
data = cPickle.load(fp)
EOFError
[...]
#
---

2.1.2 at least still delivers mails.

I'm helpless


  frank

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] listowners list?

2004-06-28 Thread Brad Knowles
At 7:15 PM -0700 2004-06-27, Steve Portigal wrote:
 I have been using majordomo for many many years and am a couple of days
 into my first mailman list, as a customer of an ISP, and I'm looking for
 an appropriate resource to configuration help from my level (i.e., not
 the system access that the folks here are oriented towards).
	The only Mailman-related mailing lists I know of are 
mailman-users and mailman-developers.  I'm not aware of any 
Mailman-related mailing list that is exclusively oriented towards 
just list owners.

If you know of any or find out about some, please let us know.
--
Brad Knowles, [EMAIL PROTECTED]
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
-Benjamin Franklin, Historical Review of Pennsylvania.
  SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] listowners list?

2004-06-28 Thread Richard Barrett
Brad
On 28 Jun 2004, at 10:42, Brad Knowles wrote:
At 7:15 PM -0700 2004-06-27, Steve Portigal wrote:
 I have been using majordomo for many many years and am a couple of 
days
 into my first mailman list, as a customer of an ISP, and I'm looking 
for
 an appropriate resource to configuration help from my level (i.e., 
not
 the system access that the folks here are oriented towards).
	The only Mailman-related mailing lists I know of are mailman-users 
and mailman-developers.  I'm not aware of any Mailman-related mailing 
list that is exclusively oriented towards just list owners.

If you know of any or find out about some, please let us know.
Steve, the author of the original question, is correct about there 
having been a list for mailman list owners which was operational until 
quite recently: http://listowner.org and [EMAIL PROTECTED]

But it has dropped off the radar of late; the most recent post to it I 
received is dated April 2004

The listowner.org DNS entries are still there but I have no idea what 
has happened to the site or mailing lists associated.

Richard
--
Brad Knowles, [EMAIL PROTECTED]
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
-Benjamin Franklin, Historical Review of Pennsylvania.
  SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: 
http://www.mail-archive.com/mailman-users%40python.org/


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] listowners list?

2004-06-28 Thread Brad Knowles
At 12:00 PM +0100 2004-06-28, Richard Barrett wrote:
 Steve, the author of the original question, is correct about there
 having been a list for mailman list owners which was operational until
 quite recently: http://listowner.org and [EMAIL PROTECTED]
	Indeed, after seeing that message, I re-checked the list of 
mailman mailing lists at http://www.list.org/lists.html and noticed 
that it was there.  I don't know why, but I must have missed that 
every single previous time I saw that page.

 But it has dropped off the radar of late; the most recent post to it
 I received is dated April 2004
	There seems to have been some problems with it before then -- see 
Barry's message dated Mon Jan 12 18:28:24 EST 2004 at 
http://mail.python.org/pipermail/mailman-users/2004-January/033888.html.

 The listowner.org DNS entries are still there but I have no idea what
 has happened to the site or mailing lists associated.
It looks like it's off-the-air:
% lft www.listowner.org.
Tracing _
TTL  LFT trace to airband-69-26-234-42.airband.net (69.26.234.42):80/tcp
**   [neglected] no reply packets received from TTL 1
 2   1-233.242.81.adsl.skynet.be (81.242.233.1) 23.5ms
 3   at-0-2-0--0-224.iadslbnc1.isp.belgacom.be (80.201.237.73) 39.7ms
 4   ge1-0.intlmar1.isp.belgacom.be (194.78.0.147) 31.8ms
 5   ge-8-1.hsa2.brussels1.level3.net (212.3.234.177) 23.3ms
 6   so-5-0-0.mp2.brussels1.level3.net (4.68.113.205) 21.5ms
 7   so-3-0-0.mp1.london2.level3.net (212.187.128.46) 21.8ms
 8   as-0-0.bbr2.washington1.level3.net (4.68.128.102) 105.9ms
 9   so-7-0-0.edge1.washington1.level3.net (209.244.11.14) 107.6ms
10   ge-2-2-0--101.er01.asbn.eli.net (207.173.144.29) 109.2ms
11   so-2-0-0--0.cr02.mcln.eli.net (207.173.115.109) 109.6ms
12   p10-0.cr01.dlls.eli.net (207.173.115.65) 149.8ms
13   srp2-0.cr02.dlls.eli.net (208.186.20.66) 145.8ms
14   p7-0.cr02.phnx.eli.net (207.173.114.113) 165.9ms
15   srp0-0-0.gw02.phnx.eli.net (208.186.20.114) 167.0ms
16   gw-cust-airband2-dom.phnx.eli.net (216.190.193.162) 188.6ms
17   airband-69-26-225-126.airband.net (69.26.225.126) 176.1ms
18   airband-69-26-225-142.airband.net (69.26.225.142) 184.5ms
**   [neglected] no reply packets received from TTL 19
20   airband-66-226-237-150.airband.net (66.226.237.150) 184.4ms
**   [80/tcp failed]  Try alternate options or use -V to see packets.
There is an advertised mail server:
% dig listowner.org. mx
;  DiG 9.2.2  listowner.org. mx
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 8718
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;listowner.org. IN  MX
;; ANSWER SECTION:
listowner.org.  86400   IN  MX  0 sparky.cisto.org.
;; AUTHORITY SECTION:
listowner.org.  86400   IN  NS  c.ns.cisto.org.
listowner.org.  86400   IN  NS  ns1.cisto.com.
listowner.org.  86400   IN  NS  ns2.cisto.com.
listowner.org.  86400   IN  NS  b.ns.cisto.org.
;; Query time: 227 msec
;; WHEN: Mon Jun 28 13:47:57 2004
;; MSG SIZE  rcvd: 140
However, all I get is a timeout when I try to connect to this machine:
% telnet sparky.cisto.org. 25
Trying 69.26.234.42...
telnet: connect to address 69.26.234.42: Operation timed out
telnet: Unable to connect to remote host
I can trace to it fine, though:
% lft sparky.cisto.org.
Tracing _
TTL  LFT trace to airband-69-26-234-42.airband.net (69.26.234.42):80/tcp
**   [neglected] no reply packets received from TTL 1
 2   1-233.242.81.adsl.skynet.be (81.242.233.1) 23.5ms
 3   at-0-2-0--0-224.iadslbnc1.isp.belgacom.be (80.201.237.73) 53.4ms
 4   ge1-0.intlmar1.isp.belgacom.be (194.78.0.147) 23.4ms
 5   ge-8-1.hsa2.brussels1.level3.net (212.3.234.177) 21.5ms
 6   so-5-0-0.mp2.brussels1.level3.net (4.68.113.205) 30.2ms
 7   so-3-0-0.mp1.london2.level3.net (212.187.128.46) 23.3ms
 8   as-0-0.bbr2.washington1.level3.net (4.68.128.102) 106.0ms
 9   so-7-0-0.edge1.washington1.level3.net (209.244.11.14) 108.5ms
10   ge-2-2-0--101.er01.asbn.eli.net (207.173.144.29) 110.2ms
11   so-2-0-0--0.cr02.mcln.eli.net (207.173.115.109) 108.1ms
12   p10-0.cr01.dlls.eli.net (207.173.115.65) 147.3ms
13   srp2-0.cr02.dlls.eli.net (208.186.20.66) 145.9ms
14   p7-0.cr02.phnx.eli.net (207.173.114.113) 167.9ms
15   srp0-0-0.gw02.phnx.eli.net (208.186.20.114) 186.0ms
16   gw-cust-airband2-dom.phnx.eli.net (216.190.193.162) 186.6ms
17   airband-69-26-225-126.airband.net (69.26.225.126) 184.4ms
18   airband-69-26-225-142.airband.net (69.26.225.142) 190.5ms
**   [neglected] no reply packets received from TTL 19
20   airband-66-226-237-150.airband.net (66.226.237.150) 186.5ms
**   [80/tcp failed]  Try alternate options or use -V to see packets.
	Maybe we need to give Norbert a call?  Unfortunately, while his 
address appears to be in 

[Mailman-Users] mailman not working on virtual host ???

2004-06-28 Thread Yogesh Subhash Talekar
hi

I am trying to configure mailman on my postfix server (postfix-1.1.11-114)
 using virtual domain.

So I added a virtual domain list.mydomain.com on my postfix which is
alreasy configured for mydomain.com

Then I added /var/mailman/data/aliases file to alias_maps in main.cf
Also added /var/mailman/data/virtual-mailman to virtual_maps in main.cf

I created new list. Now it seems that when I drop a mail to my newly
created mailman list. The postfix is able use to virtual table and
re-write the address to mydomain.com but after this it is not able to
recongnise the aliases written in /var/mailman/data/aliases and says user
unknown

postconf's output is given below.

Can anyone help/advice

--yogesh


==postconf -n output 
alias_maps = hash:/etc/aliases, hash:/var/mailman/data/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix-out
content_filter =
daemon_directory = /usr/lib/postfix
debug_peer_level = 2
default_destination_concurrency_limit = 10
default_destination_recipient_limit = 50
default_extra_recipient_limit = 1000
default_minimum_delivery_slots = 3
default_process_limit = 50
default_recipient_limit = 1
delay_warning_time = 4h
disable_dns_lookups = no
inet_interfaces = 57.193.32.70
initial_destination_concurrency = 5
mail_name =  Mail Server
mail_owner = postfix
mail_spool_directory = /var/mail
mailbox_command = /usr/bin/procmail -a $EXTENSION
mailbox_transport =
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = mydomain.com
mydomain = mydomain.com
myhostname = mailt-out.mydomain.com
mynetworks = hash:/etc/postfix-out/mynetworks,hash:/etc/postfix-out/mynetw
orks.dr
mynetworks_style = host
myorigin = $mydomain
newaliases_path = /usr/sbin/sendmail
owner_request_special = no
qmgr_fudge_factor = 100
qmgr_message_active_limit = 1
qmgr_message_recipient_limit = 1
qmgr_message_recipient_minimum = 10
qmgr_site_hog_factor = 100
queue_directory = /var/spool/postfix-out
readme_directory = /usr/share/doc/packages/postfix/README_FILES
recipient_canonical_maps = hash:/etc/postfix-out/recipient_canonical,
ldap:fax
procldap,   ldap:receipldap,ldap:receipldap2,
recipient_delimiter = +
relayhost =
sample_directory = /usr/share/doc/packages/postfix/samples
sender_canonical_maps = hash:/etc/postfix-out/sender_canonical,
ldap:senderldap,ldap:senderldap2
sendmail_path = /usr/sbin/sendmail
setgid_group = maildrop
smtp_bind_address = 57.66.52.70
smtp_connect_timeout = 180s
smtp_line_length_limit = 1024
smtpd_banner = $myhostname ESMTP $mail_name
smtpd_client_restrictions =
smtpd_helo_required = yes
smtpd_helo_restrictions =
smtpd_recipient_limit = 1000
smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination
strict_rfc821_envelopes = no
syslog_facility = local1
syslog_name = postfix-out
transport_maps = hash:/etc/postfix-out/transport,
hash:/etc/postfix-out/baddomains_transport
virtual_maps = hash:/etc/postfix-out/virtual,
hash:/var/mailman/data/virtual-mailman


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] bug?

2004-06-28 Thread Ian A B Eiloart
Hi,
Users have reported getting moderator messages like this:
Subject: -1 CGPE-internal moderator request(s) waiting
The [EMAIL PROTECTED] mailing list has -1 request(s) waiting
for your consideration at:
http://mail.sussex.ac.uk/mailman/admindb/cgpe-internal

Please attend to this at your earliest convenience.  This notice of
pending requests, if any, will be sent out daily.
That's not 1 request, its -1 request. There aren't any requests when they 
get there. I think this is a bug introduced in the last update (or the one 
before, I skipped a version). I've only seen it since I last upgraded.

--
Ian Eiloart
Servers Team
Sussex University ITS
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] Migration to a new server - issues

2004-06-28 Thread Josh Harding
Hello,

I recently migrated mailman from our catch-all server to a dedicated
listserv server. The process I used was as follows:
1.) Create lists on new server based on list_lists on old server
1.) Stop mail on old server (Postfix stop) and new server
2.) Insert temporary redirect away from web interface on old server
3.) Rsync /var/lib/mailman/lists and /var/lib/mailman/archives from old
server to new server
4.) Change DNS and setup forwards from the old server for people slow to
update their DNS
5.) Bring everything back up

This seemed to go well, and list activity continued as normal on the new
server, until 9 am the next day, when mailman's bounce processing disabled
about 200 list members from various list,, and deleted 100 or so more. It
did not continue this pattern the following day. I have intact membership
lists I can drop in, but don't know why it happened, and so am hesitant to
move blindly forward. The membership list was up to date, as we were using
fairly stringent bounce processing on the old server.

Any ideas on why that would occur? Was my migration process flawed?
Assistance would be greatly appreciated.

Joshua Harding
Community Software Lab
csl.ltc.org


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] bug?

2004-06-28 Thread Arkadiusz Miskiewicz
On Monday 28 of June 2004 18:06, Ian A B Eiloart wrote:

  Subject: -1 CGPE-internal moderator request(s) waiting
[...]
 That's not 1 request, its -1 request. There aren't any requests when they
 get there. I think this is a bug introduced in the last update (or the one
 before, I skipped a version). I've only seen it since I last upgraded.
I can say ,,me too'' here. After updating to 2.1.5 I started getting such 
informations from mailman for new mailing lists without any traffic, yet.

-- 
Arkadiusz Mikiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Migration to a new server - issues

2004-06-28 Thread Josh Harding

 That's not the process I would use, but I don't see where it should
 have been a problem. Unless somehow bad characters got inserted into
 those addresses and caused them to bounce.

 What did the bounces say? What do you see in your MTA log about these
 addresses?


That's the interesting part - the MTA log doesn't show any bounces from
those addresses. It successfully delivered each warning message, and then
disabled the user anyway. The mailman log file doesn't show the
individual messages, only when each user was disabled or deleted.

As a side note - what would a better process be for the future?

-Joshua



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] listowners list?

2004-06-28 Thread Brad Knowles
At 1:15 AM +0200 2004-06-29, Norbert Bollow wrote:
  I'll try to find a little time soon to set it up again on one of
 the machines which I use for my commercial stuff (they're all up and
 running).  I have a recent backup of the list's data, hence it
 shouldn't be a real problem.
Thanks for the update!
--
Brad Knowles, [EMAIL PROTECTED]
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.
-Benjamin Franklin, Historical Review of Pennsylvania.
  SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] Mailman book

2004-06-28 Thread Michael Sullivan
I'm looking for a good book on mailman that will explain setting it up
and day-to-day operations involved with mailman.  I've searched
Amazon.com and O'Reilly.com and not had any luck finding one.  Can
anyone give me any recommendations for a good book to help me work with
mailman?


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] Load-balancing Mailman in LVS cluster

2004-06-28 Thread Guy Waugh
Hi there,
I'm a new user of Mailman, and a new subscriber to this list.
I want to set up Mailman in a load-balanced fashion on two servers 
running within an LVS (linux virtual server) cluster. I want the two 
servers to act as the same Mailman instance. The two servers will mount 
an NFS shared directory from a third server, and the NFS mount will, I 
guess, contain the shared Mailman stuff. I've found a few things on the 
web about load-balancing Mailman, but not much.

The following directories exist in $prefix/mailman:
archives *
bin
cgi-bin
cron
data *
icons
lists *
locks *
logs
mail
Mailman *
messages
pythonlib
qfiles
scripts
spam
templates
tests
Can anybody suggest which of these directories should be NFS shared 
between the two servers? To me, it looks like good candidates would be 
those that I have marked with an * ...

Further, is anyone running Mailman in a load-balanced fashion like this? 
Any hints/tricks/tips?

Thanks in advance,
Guy.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/