Re: [Mailman-Users] Virtual hosts

Brad Knowles writes: [[ Aside: > I was on the DRUMS working group for a while, Thank you! ]] > The MTA needs to rewrite headers that the MTA needs to rewrite. The > question is which headers should the MTA be rewriting? RFC 2821 section 3.8.4 (IIRC) mandates that gateways rewrite non-FQDN

[Mailman-Users] PROBLEM

Hello ALL I have a new requirement for my company As per the requirement I need to add multiple domains.for example list.web2ph.net and list.ispai.in in the same mail server Requirement When i will create a mailing list for ispai.in it should show me to subscribe to the list send mail to [

Re: [Mailman-Users] mailman-bounces with wrong domain

Hello again, >>The only ones that I use are: >> >>OWNERS_CAN_ENABLE_PERSONALIZATION = Yes >>DEFAULT_URL_HOST = 'DOMAIN.TLD' >>SMTPHOST = 'localhost' >>VERP_CONFIRMATIONS = Yes > > > What is in Defaults.py for DEFAULT_EMAIL_HOST? > > Add the following lines to mm_cfg.py following the assignment to

[Mailman-Users] header intact

Elly -- 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/ Unsubsc

Re: [Mailman-Users] Virtual hosts

At 10:59 AM +0900 4/12/07, Stephen J. Turnbull quoted Mark Sapiro: > > I have added FAQ 6.22 > > . > > Look it over and comment/fix as appropriate. > > Basic format, especially the length, looks good to me. Agreed. >

Re: [Mailman-Users] Virtual hosts

At 12:26 AM +0900 4/12/07, Stephen J. Turnbull wrote: > I think it's odd that RFC 2821 section 3.6 fails to mention that it > contradicts RFC 1123 section 5.2.2. Nor does RFC 2821 claim to > supersede or update RFC 1123 or STD 3. The fact that in both 3.6 and > throughout section 5 it implau

Re: [Mailman-Users] Virtual hosts

Mark Sapiro writes: > I have added FAQ 6.22 > . > Look it over and comment/fix as appropriate. Basic format, especially the length, looks good to me. Two suggestions: my feeling is that the first line should mention the *pl

Re: [Mailman-Users] Virtual hosts

Brad Knowles wrote: > >So, we're still going to need a FAQ on this subject, regardless of >whether the then-current RFCs require that CNAME aliases be resolved >to their actual canonical names or not. I have added FAQ 6.22 .

Re: [Mailman-Users] Blocked from moderating the list

[EMAIL PROTECTED] wrote: >I just put in 'listname'... it was originally the [EMAIL PROTECTED] in that >slot. > > -- Original message -- >From: Paul Tomblin <[EMAIL PROTECTED]> >> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): >> > Forbidden >> > You don't have perm

Re: [Mailman-Users] Subscription Help

Dave Kall wrote: > >The address I have is like: > >http://my.domain.org/mailman/admin/scoop/members/add? >subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notification >s_to_list_owner=0&subscribees=&subscribees_upload=&invitation=&setmember >opts_btn=Submit Your Changes You have ex

Re: [Mailman-Users] mailman-bounces with wrong domain

Zbigniew Szalbot wrote: > >>>But when I write to [EMAIL PROTECTED], I get an email from >>>[EMAIL PROTECTED] >>> >> What are your settings for DEFAULT_URL_HOST, and add_virtualhost() for >> that host. > >The only ones that I use are: > >OWNERS_CAN_ENABLE_PERSONALIZATION = Yes >DEFAULT_URL_HOST = 'D

Re: [Mailman-Users] Blocked from moderating the list

I just put in 'listname'... it was originally the [EMAIL PROTECTED] in that slot. -- Blessings, Toni -- Original message -- From: Paul Tomblin <[EMAIL PROTECTED]> > Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > > Forbidden > > You don't have permission to acc

Re: [Mailman-Users] Blocked from moderating the list

Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > Forbidden > You don't have permission to access /mailman/admindb/listname.com on this > server. Did you really put "listname.com" in the URL, or did your browser spaz out and put it the ".com" in? -- Paul Tomblin <[EMAIL PROTECTED]> http://blog.x

[Mailman-Users] Blocked from moderating the list

I was doing my daily chores of dealing with pending messages just fine. Suddenly, this is the message I get when I try to approve or dump emails to the list. (I've changed only what shows as the listname here.) I'm hoping there is an easy fix to this. Thanks for helping a newbie like me. :) Fo

[Mailman-Users] Subscription Help

I'm trying to write a script to add users through the url address: Seems that this should work. The address I have is like: http://my.domain.org/mailman/admin/scoop/members/add? subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notification s_to_list_owner=0&subscribees=&subscribee

Re: [Mailman-Users] mailman-bounces with wrong domain

Dear Mark, >>But when I write to [EMAIL PROTECTED], I get an email from >>[EMAIL PROTECTED] >> > What are your settings for DEFAULT_URL_HOST, and add_virtualhost() for > that host. The only ones that I use are: OWNERS_CAN_ENABLE_PERSONALIZATION = Yes DEFAULT_URL_HOST = 'DOMAIN.TLD' SMTPHOST = 'l

Re: [Mailman-Users] mailman-bounces with wrong domain

Zbigniew Szalbot wrote: > >I have a problem with just one list - the main list called mailman. It was >created with 192.168.11.51 IP as default for this list but since then I >ran fix_url to point it to my current domain and when I visit the general >options page for mailman, I can see the appropri

Re: [Mailman-Users] No hitches

Paul Tomblin <[EMAIL PROTECTED]> wrote: >Debian just marked Debian 4.0 (etch) as stable, so I upgrade my Debian >3.1 (sarge) colo box to Debian 4.0. Along the way, it upgraded Mailman >from 2.1.5 to 2.1.9. Just wanted to let anybody else contemplating such >an upgrade that it went without a h

Re: [Mailman-Users] Virtual hosts

Brad Knowles writes: > | In the dot-atom form, this is interpreted as an Internet > | domain name (either a host name or a mail exchanger name) as > | described in [STD3, STD13, STD14]. > > In particular, note that it says "host name" or "mail exchanger > name", and specif

[Mailman-Users] mailman-bounces with wrong domain

Hello, I have a problem with just one list - the main list called mailman. It was created with 192.168.11.51 IP as default for this list but since then I ran fix_url to point it to my current domain and when I visit the general options page for mailman, I can see the appropriate domain there. But