Re: [Mailman-Users] Help getting SuSE 9.3+Mailman 2.1.5+Apache2 working

[Poster]

Michael Regoli said:
> Hello! I'm trying to get mailman and Apache2 working nicely from the
> stock SuSE distro. (YOU, Yast Online Update is current on the machine,
> so if there's new stuff for either mailman or Apache2, I've got it.
> mailman is version [2.1.5] and Apache2 is version [2.0.53].)

I had a similar problem -- I think. I have Suse 9.3, stock Mailman and
stock Apache2, all updated with YOU. In my case, it was first the
inability for Mailman to run as the right GID, then it was the
inability to read the wrapper config files (which incidentally, don't
exist). Scouring the internet led me to clues that the error really
meant that the GID was still wrong. Nothing I did worked. I changed
the UID GID files that Mailman uses. I tweaked the mailman.conf files
in /etc/apache2. I inspected mail.err logs in /var/log. I changed
perms, owner, group, and access bits on everything that seemed
related. Still nothing.

Finally, out of sheer desperation, I reinstalled the stock Suse
Mailman RPM running as the mailman user. Then I checked (and fixed)
permissions issues using the scripts in /usr/lib/mailman/bin. With the
mailman cgi files moved to /cgi-bin/mailman and aliased in apache's
default-server.conf file (and given their own separate 
section with CGI script running turned on), everything worked!

I'm convinced that a reinstall is necessary to fix some permissions
SOMEWHERE. I spent way too much time trying to debug it, but with
mailman's lame, unhelpful error messages, there's just not much I
could do.

I don't use virtual servers yet, but I expect I will soon. And BTW,
the error message you're currently seeing is an Apache error message.

HTH,
Poster

++
+www.intaligo.com/mt +
+  Professional Editing/Web Design   +
+www.intaligo.com/mt +
++
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Improving SMTP performance?

[Paul Key]

Mailman 2.1.3
Solaris 9
Exim 4.43

I have a list with 2300 subscribers and have set SMTP_MAX_RECEIPTS = 0 
to submit all the entire recipient list in one transaction to Exim.

Looking in the Mailman SMTP log file I see the following line:

smtp for 2300 recips, completed in 1921.891 seconds.

This seems a long time to me ?  Is it?  Does anyone know how I can speed 
this up?

Thanks

Paul



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Improving SMTP performance?

[Brad Knowles]

At 1:48 PM +0100 2005-06-28, Paul Key wrote:

>  smtp for 2300 recips, completed in 1921.891 seconds.
>
>  This seems a long time to me ?  Is it?  Does anyone know how I can speed
>  this up?

Did you search the Mailman FAQ Wizard for "performance"?

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman 2.1.6b4 issues

[Darren G Pifer]

Hello,

  I am new to the list so if I miss something or is improper
protocol, please let me know.

  Recently, we upgraded our mailman software from 2.0.13 to 2.1.6b4
and moved from a Solaris to Linux platform (RedHat AS 3 Update) on a
different machine. The Apache Web server we are running is 2.0.52. We
are successfully sending mail through the list server and the web server
is generally working, except for a couple of issues. The first issue is
that the software is sending unsubscription notices to user's e-mail
addresses, even though the "Send unsubscription acknowledgement to the
user" is set to No, under "Membership Management", "Mass Removal".
Secondly, when I try to change one of the configuration settings on a
list as the mailman administrator for any of the radio buttons under
"Mass Subscription" or "Mass Removal" and click on submit, the settings
revert back to the default setting.

 We were planning on installing the stable release of 2.1.6 but it
did not appear that this version addressed any of the problems that we
are having.

 Has anybody seen these problems? What can I check for? Is there any
other information you need from me to get an answer for these issues?

 Regards,

Darren Pifer
Old Dominion University
UNIX systems admin

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman 2.1.6b4 issues

[Brad Knowles]

At 11:24 AM -0400 2005-06-28, Darren G Pifer wrote:

>  Secondly, when I try to change one of the configuration settings on a
>  list as the mailman administrator for any of the radio buttons under
>  "Mass Subscription" or "Mass Removal" and click on submit, the settings
>  revert back to the default setting.

Hmm.  Did you look in the Mailman FAQ Wizard?  In particular, the 
entry at 
 
sounds like it might be useful.

>   We were planning on installing the stable release of 2.1.6 but it
>  did not appear that this version addressed any of the problems that we
>  are having.

There were other important fixes in the 2.1.6-release version. 
You should install it to get those, if nothing else.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman 2.1.6b4 issues

[Mark Sapiro]

Darren G Pifer wrote:
>
>The first issue is
>that the software is sending unsubscription notices to user's e-mail
>addresses, even though the "Send unsubscription acknowledgement to the
>user" is set to No, under "Membership Management", "Mass Removal".


This setting only affects that particular mass removal. In general,
this is controlled by 'send_goodbye_msg' on the general options page.

If the issue is that notices are sent for a particular mass removal
even though send acknowledgement is set to No for that removal, this
may be a case of 'post' data being lost as Brad suggested in another
reply, but that usually results in nothing working at all.


>Secondly, when I try to change one of the configuration settings on a
>list as the mailman administrator for any of the radio buttons under
>"Mass Subscription" or "Mass Removal" and click on submit, the settings
>revert back to the default setting.

Any settings you make to the radio buttons on the mass subscribe/remove
pages affect that particular action only. Defaults for these buttons
are as follows:

Mass Subscribe
   Subscribe/Invite = Subscribe (can't change default w/o hacking code)
   Send Welcome = send_welcome_msg setting from general options
   Notify list owner = admin_notify_mchanges from general options

Mass Remove
   Send Ack to user = No (can't change default w/o hacking code)
   Notify list owner = admin_notify_mchanges from general options

Arguably, the default for

Mass Remove
   Send Ack to user

should be send_goodbye_msg from general options, but it has been 'No'
at least since 2.1.4.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Multiple subscription requests and reminders

[Bruno Ferreira]

Mark Sapiro wrote:

>The question is why is Mailman processing the request 4 times. Is it a
>bug in mailman or does mailman actually receive 4 requests?
>
>Does the request arrive via the web interface (subscribe form on the
>listinfo page) or via e-mail. If from the web, what do the web servers
>logs say about how many 'post' transactions were processed? If via
>mail, what do the incoming MTA logs say about how many messages were
>piped to the wrapper?
>  
>

After a bit more investigation at the MTA side, I managed to find 
out that Mailman processes the subscribe requests alone twice. 
Subscribing through the web interface makes Mailman process the request 
once.  However, sending a mail without proper commands to 
[EMAIL PROTECTED] throws ONE error e-mail back, as it should 
be. So there's this situation:

- Subscription through web interface: OK
- Subscription through e-mail: 2 subscriptions processed
- Other mail to [EMAIL PROTECTED]: OK

Where do you suggest I start looking now?

-- Bruno Ferreira
---
[This E-mail scanned for viruses by Declude Virus]

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Mailman 2.1.6b4 issues

[Darren G Pifer]

Thanks to all for the answers. After some testing I realized this
was the case for the specific list I was using. It worked as was
expected.

We will upgrade to 2.1.6 at our first opportunity to take advantage
of some fixes.

Darren
Old Dominion University

On Tue, 2005-06-28 at 12:49, Mark Sapiro wrote:
> Darren G Pifer wrote:
> >
> >The first issue is
> >that the software is sending unsubscription notices to user's e-mail
> >addresses, even though the "Send unsubscription acknowledgement to the
> >user" is set to No, under "Membership Management", "Mass Removal".
> 
> 
> This setting only affects that particular mass removal. In general,
> this is controlled by 'send_goodbye_msg' on the general options page.
> 
> If the issue is that notices are sent for a particular mass removal
> even though send acknowledgement is set to No for that removal, this
> may be a case of 'post' data being lost as Brad suggested in another
> reply, but that usually results in nothing working at all.
> 
> 
> >Secondly, when I try to change one of the configuration settings on a
> >list as the mailman administrator for any of the radio buttons under
> >"Mass Subscription" or "Mass Removal" and click on submit, the settings
> >revert back to the default setting.
> 
> Any settings you make to the radio buttons on the mass subscribe/remove
> pages affect that particular action only. Defaults for these buttons
> are as follows:
> 
> Mass Subscribe
>Subscribe/Invite = Subscribe (can't change default w/o hacking code)
>Send Welcome = send_welcome_msg setting from general options
>Notify list owner = admin_notify_mchanges from general options
> 
> Mass Remove
>Send Ack to user = No (can't change default w/o hacking code)
>Notify list owner = admin_notify_mchanges from general options
> 
> Arguably, the default for
> 
> Mass Remove
>Send Ack to user
> 
> should be send_goodbye_msg from general options, but it has been 'No'
> at least since 2.1.4.
> 
> --
> Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 
> 
> 
> 

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] wrong server at all the links

[ronny]

Hi,

A customer upgraded from debian WOODY to SARGE and finishes in mailman
problems. There is a list "mitarbeiter". We can connect the options by using
"http://local_server_one/cgi-bin/mailman/admin/mitarbeiter"; but every link
we see shows to "http://local_server_two/...";, we dont want to know why this
change happens, we only want to solve the problem.

I can't find "local_server_two" at mailman directories in /etc, /usr and
/var please help.




Mit freundlichen Grüßen / With kind regards

  Ronny Seffner

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Subscribe not functioning

[Mark Sapiro]

[EMAIL PROTECTED] wrote:

>--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
>> Can an external user post successfully?
>
>-- Yes, anyone already subscribed to the list can
>post.  I've had to add all outside addresses manually
>through the administration pages.
> 
>> If an internal user can successfully subscribe by
>> e-mail, but an
>> external user can't, I think it must be an Exim
>> configuration issue.
>
>-- When testing it out, I don't receive an
>"undeliverable"-type reply, so the message is being
>delivered.  There's just no confirmation response at
>all...  I'm looking into upgrading Exim to 4 with SSL.
> Perhaps that may make a difference, as it appears 3.x
>is not very well supported...?


So posting works which indicates Exim properly delivers posts to the
wrapper. I don't know Exim, but it seems this should mean Exim will
also handle '-subscribe', etc. e-mail at least if configured in accord
with http://www.exim.org/howto/mailman.html, but note that the two
documents there cover Mailman 2.0/Exim 3 and Mailman 2.1/Exim 4. For
Mailman 2.1/Exim 3, you may need to interpolate between the two.

Upgrading to Exim 4 is probably a good idea.

In any case, check Exim logs to see that the request is properly piped
to the Mailman wrapper.

 
>> Can internal users subscribe via the web and
>> external users not? I
>> can't offhand understand what might cause this.
>
>-- Web subscribing does not work at all.  No
>confirmation email is delivered, nor is an
>administrative accept request issued when I tried that
>route.

Does the rest of the web interface work? Did you edit the listinfo.html
template? If so, you should be aware that the 
tag in the template comes 'too early' making it really easy to break
the subscribe form when editing.

Also, look at the source html of the actual listinfo page to make sure
the ACTION= URL in the FORM tag looks correct. If not, there may be
issues with Defaults.py/mm_cfg.py things such as DEFAULT_URL_HOST,
DEFAULT_EMAIL_HOST and add_virtualhost() and/or the list attributes
host_name and web_page_url. See
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp
for more info.

You might also look at
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.033.htp
and try this minimal subscribe form to see if it works.


For both issues, check Mailman's logs for anything relevant.
Particularly the 'subscribe', 'error', 'smtp' and if any the
'smtp-failure' logs.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] wrong server at all the links

[Mark Sapiro]

[EMAIL PROTECTED] wrote:
>
>A customer upgraded from debian WOODY to SARGE and finishes in mailman
>problems. There is a list "mitarbeiter". We can connect the options by using
>"http://local_server_one/cgi-bin/mailman/admin/mitarbeiter"; but every link
>we see shows to "http://local_server_two/...";, we dont want to know why this
>change happens, we only want to solve the problem.

You need to run bin/fix_url.py - run it directly for instructions.

Also see
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Multiple subscription requests and reminders

[Mark Sapiro]

Bruno Ferreira wrote:
>
>After a bit more investigation at the MTA side, I managed to find 
>out that Mailman processes the subscribe requests alone twice. 
>Subscribing through the web interface makes Mailman process the request 
>once.  However, sending a mail without proper commands to 
>[EMAIL PROTECTED] throws ONE error e-mail back, as it should 
>be. So there's this situation:
>
>- Subscription through web interface: OK
>- Subscription through e-mail: 2 subscriptions processed
>- Other mail to [EMAIL PROTECTED]: OK
>
>Where do you suggest I start looking now?

Look at the actual subscription request e-mail (Bcc: yourself to get a
copy). Look for anything strange like two From: headers or e-mail
address appearing twice in From: header.

Check MTA log to make sure request is only piped once to the wrapper,
although it seems that you've probably already done this or at least
empirically verified it (- Other mail to [EMAIL PROTECTED]:
OK)

Are you mailing [EMAIL PROTECTED] with 'subscribe' both in the
subject and in the body of the e-mail?

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Welcome to the "Mailman-Users" mailing list

[Peter Seebach]

In message <[EMAIL PROTECTED]>, Mark Sapiro writes:
>Peter Seebach wrote:
>
>>In message <[EMAIL PROTECTED]>, mailman-us
>>[EMAIL PROTECTED] writes:
>>>Welcome to the Mailman-Users@python.org mailing list! Don't forget to
>>>check out the Mailman FAQ at:
>
>
>And if you had, you might have come across
>http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp
>which would have helped with your problem.
>
>You need to run fix_url against your old lists as explained in the
>'Existing versus new lists' section of the above FAQ article.

Thanks!  I actually did search the FAQ, but I apparently used the wrong search
keywords.  That looks helpful.  I was looking for explanations of the behavior; 
I
had no idea that the URLs were encoded in the list, or mattered, so I had no
idea I needed to read the stuff about changing the URL.  I assumed that since 
the
Mailman list was showing up, the URL was set correctly...

-s
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Welcome to the "Mailman-Users" mailing list

[Mark Sapiro]

Peter Seebach wrote:
>
>Thanks!  I actually did search the FAQ, but I apparently used the wrong search
>keywords.  That looks helpful.  I was looking for explanations of the 
>behavior; I
>had no idea that the URLs were encoded in the list, or mattered, so I had no
>idea I needed to read the stuff about changing the URL.  I assumed that since 
>the
>Mailman list was showing up, the URL was set correctly...

If you could let us know what searches you tried that didn't return the
article or how we could better describe what the article addresses, we
can try to update the FAQ to do better next time.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Welcome to the "Mailman-Users" mailing list

[Peter Seebach]

In message <[EMAIL PROTECTED]>, Mark Sapiro writes:
>If you could let us know what searches you tried that didn't return the
>article or how we could better describe what the article addresses, we
>can try to update the FAQ to do better next time.

Good point!

The issue here is that the FAQ describes what to do, and even mentions "old
lists", but doesn't mention the symptoms.  As a person whose mailman
installation is failing, the only thing I have access to is symptoms.  It
would be good to have cross-references to this in the troubleshooting stuff;
for instance, in the same place where you talk about database conversion
(which I found) or the importance of creating an umbrella list (which I
found).

I had no information that would have led me to suspect that "URLs" were part
of my problem.  I didn't know that a list had a URL encoded in it or anything
like that.  What I knew was that I had lists which looked correct, but which
didn't show up on the admin.cgi page.  And, also, where test messages to those
lists produced no response at all, not even a mention in the log file.

Those are the kinds of symptoms I was looking at, and I knew enough to look
around at the symptoms, but that FAQ entry, while describing what one needs
to do, doesn't mention any symptoms... So there's no likelihood of a match.

I would think the right sort of thing would be a checklist of "things that
can make a list not work", and have "wrong URL encoded in list (common when
migrating lists)" on it.  :)

-s
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] virtual domain lists

[Christian Anton]

Am Dienstag 28 Juni 2005 02:56 schrieb Mark Sapiro:
> Christian Anton wrote:
> >i am running mailman 2.1.5 with the mailman-virtual patch for some virtual
> >domains.
> >Because of the usage of suexec on my Webserver i have every vhost running
> > its CGI's with another UID on the system. For being able to access the
> > mailman-binaries i have to create a new vhost that ist only for this, for
> > example "lists.domain.tld", configuring in this vhost that cgi's are
> > executed with the UID 'mailman'.
> >
> >Now i want to create a mailinglist [EMAIL PROTECTED], but the URL host for
> > seeing the webpages of the list must be [EMAIL PROTECTED]
>
> Do you mean lists.mglug.de?
yes, i meant!
>
> >I have read the documentation and i think that add_virtualhost(,
> >) has to be what i want, so that when i create a list with the
> >command:
> >
> >bin/newlist [EMAIL PROTECTED]
>
> If you carefully read 'bin/newlist --help' you will see the command you
> want is
>
> bin/newlist [EMAIL PROTECTED]
>
> i.e., [EMAIL PROTECTED], not [EMAIL PROTECTED]
>
> I know this is confusing and it has been addressed in 2.1.6 by adding
> new options so you could do
>
> bin/newlist list --urlhost=lists.mglug.de
>
> but this won't work in 2.1.5.
>
Reading manuals is a fine thing... 

It runs, thank you very much!



Christian
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] How to specify alternate port in ./configure --mailhost= ?

[Forrest Aldrich]

We're running a special MTA on a different port, and I would like to
point the mailman instance to that.   Is it possible to specify this in
the ./configure options or does it need to be input into mm_cfg.py
somewhere?


Thanks.

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] How to specify alternate port in ./configure--mailhost= ?

[Mark Sapiro]

Forrest Aldrich wrote:

>We're running a special MTA on a different port, and I would like to
>point the mailman instance to that.   Is it possible to specify this in
>the ./configure options or does it need to be input into mm_cfg.py
>somewhere?

It isn't a ./configure option. It is an mm_cfg.py option. See SMTPHOST
and SMTPPORT in Defaults.py for info.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] How to specify alternate port in ./configure--mailhost= ?

[Forrest Aldrich]

I was referring to the ./configure option:

--with-mailhost  specify the hostname part for outgoing email

Though I put your suggested fixes in there and that seems to work, too.

What is this configure option - or is it just a switch that can be
overidden in mm_cfg.py.


Thanks.


Mark Sapiro wrote:

>Forrest Aldrich wrote:
>
>  
>
>>We're running a special MTA on a different port, and I would like to
>>point the mailman instance to that.   Is it possible to specify this in
>>the ./configure options or does it need to be input into mm_cfg.py
>>somewhere?
>>
>>
>
>It isn't a ./configure option. It is an mm_cfg.py option. See SMTPHOST
>and SMTPPORT in Defaults.py for info.
>
>--
>Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
>San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>  
>
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] How to specify alternate port in./configure--mailhost= ?

[Mark Sapiro]

Forrest Aldrich wrote:

>I was referring to the ./configure option:
>
>--with-mailhost  specify the hostname part for outgoing email


This option sets the value in Defaults.py for DEFAULT_EMAIL_HOST which
in turn sets the domain part of e-mail addresses that appear in
outgoing mail and on web pages. E.g. the envelope sender is set to
-bounces@.

It has nothing to do with the host for the outgoing SMTP server.

>
>Though I put your suggested fixes in there and that seems to work, too.
>
>What is this configure option - or is it just a switch that can be
>overidden in mm_cfg.py.

See above.

--
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp