[Mailman-Users] mailman not working

[Jeff Hedglen]

My mailman program just quit working - the mail is sent back undeliverable 
after over a year of working just fine

 

Anyone else have this issue.

 

I did nothing different and none of my lists work

 

Jeff 

--
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] Command line modification of user options?

[Jim Norton]

Hello all,

I run a large list and have a need to turn of the no-mail by-bounce  
setting from a large number of subscribers.


Is there an easy way to do this from the command-line? Or perhaps  
somebody has a script?


--
Jim Norton

"The starting point of all achievement is desire. Keep this
constantly in mind. Weak desires bring weak results, just as
a small amount of fire makes a small amount of heat." - Napoleon Hill
---
--
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] clarification on virtual domains

[bijayant kumar]

Thanks Barry. I use Web Interface to create the lists.
I have not tried yet the command-line option. In my
scenario i think that i have to use command-line
option to create the list.

--- Barry Finkel <[EMAIL PROTECTED]> wrote:

> bijayant kumar <[EMAIL PROTECTED]> wrote:
> 
> >Hi list,
> >
> >I have postfix configure for virtual domain.
> Whenever
> >i add a new list for a new domain, it takes the
> >[EMAIL PROTECTED] as a email address for
> >newly created list and all the aliases being
> generated
> >on the basis of previousdomain.com. When i change
> the
> >default host this list prefers setting from the
> >interface, then mails are started to bounce saying
> >user unknown in virtual mailbox table. I will
> explain
> >my problem with the example...
> >I have three virtual domain dom1.com,
> >dom2.com,dom3.com
> >in mm_cfg.py i have
> >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
> >add_virtualhost('lists.bijayant.com', 'dom1.com')
> >
> >It works fine. lists created takes the address
> >[EMAIL PROTECTED]
> >
> >But when i add a new list say list2 like
> >
> >POSTFIX_STYLE_VIRTUAL_DOMAINS =
> >['dom1.com','dom2.com']
> >add_virtualhost('lists.bijayant.com', 'dom1.com')
> >add_virtualhost('lists.bijayant.com', 'dom2.com')
> >
> >The newly created list2 takes the address
> >[EMAIL PROTECTED]
> >
> >when i update hostname setting from the list2
> >Administrative interface, mail start bouncing.
> >
> >I hope i am able to convey my problem.
> >
> >My question is how to achieve this, i have read
> some
> >articles and tried to follow those but without any
> >success. Please guide me to achieve this.
> 
> How do you create the new list?  If via the command
> line
> 
>  /usr/sbin/newlist  LISTNAME
> 
> then you need a first parameter
> 
>  /usr/sbin/newlist -e DOMAIN LISTNAME
> 
> for example,
> 
>  /usr/sbin/newlist -e dom2.com  mynewlist
> 
> Use
> 
>  /usr/sbin/newlist -h
> 
> to get the help information for the newlist command.
>
--
> Barry S. Finkel
> Computing and Information Systems Division
> Argonne National Laboratory  Phone:+1
> (630) 252-7277
> 9700 South Cass Avenue   Facsimile:+1
> (630) 252-4601
> Building 222, Room D209  Internet:
> [EMAIL PROTECTED]
> Argonne, IL   60439-4828 IBMMAIL: 
> I1004994
> 
>
--
> 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/bijayant4u%40yahoo.com
> 
> Security Policy:
>
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> 


Bijayant Kumar

Send instant messages to your online friends http://uk.messenger.yahoo.com 
--
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] clarification on virtual domains

[bijayant kumar]

Thanks Mark for your reply. It is a great help to
understand some basic things about mailman.

--- Mark Sapiro <[EMAIL PROTECTED]> wrote:

> bijayant kumar wrote:
> >
> >I have postfix configure for virtual domain.
> Whenever
> >i add a new list for a new domain, it takes the
> >[EMAIL PROTECTED] as a email address for
> >newly created list and all the aliases being
> generated
> >on the basis of previousdomain.com. When i change
> the
> >default host this list prefers setting from the
> >interface, then mails are started to bounce saying
> >user unknown in virtual mailbox table. I will
> explain
> >my problem with the example...
> >I have three virtual domain dom1.com,
> >dom2.com,dom3.com
> >in mm_cfg.py i have
> >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
> >add_virtualhost('lists.bijayant.com', 'dom1.com')
> >
> >It works fine. lists created takes the address
> >[EMAIL PROTECTED]
> >
> >But when i add a new list say list2 like
> >
> >POSTFIX_STYLE_VIRTUAL_DOMAINS =
> >['dom1.com','dom2.com']
> >add_virtualhost('lists.bijayant.com', 'dom1.com')
> >add_virtualhost('lists.bijayant.com', 'dom2.com')
> >
> >The newly created list2 takes the address
> >[EMAIL PROTECTED]
> 
> 
> Are you sure it isn't the other way around? When you
> have
> 
> add_virtualhost('lists.bijayant.com', 'dom1.com')
> add_virtualhost('lists.bijayant.com', 'dom2.com')
> 
> The second entry effectively replaces the first
> because what they do is
> add entries to a Python dictionary (a hash table).
> The first argument
> is the key and the second is the value. So the first
> above makes an
> entry with key 'lists.bijayant.com' and value
> 'dom1.com' and the
> second replaces the value for key
> 'lists.bijayant.com' with 'dom2.com'

I am not sure about this functionality of python, but
what you are saying seems to right. After this
explanation, it is little bit clear to me now why the
second domain is taking the previous value. But i dont
have any other option because i have to use only one
url i.e 'lists.bijayant.com'. So all the lists created
have to take the same url 'lists.bijayant.com'.

> 
> >when i update hostname setting from the list2
> >Administrative interface, mail start bouncing.
> 
> 
> If you run Mailman's bin/genaliases after editing
> the list's host_name,
> that should fix the virtual maps.

I have not tried this yet, because list creator is
creating the list via the web-interface and he do not
have access the box where the mailman is running. I
will try this and let you know.

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


Bijayant Kumar

Send instant messages to your online friends http://uk.messenger.yahoo.com 
--
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] Phantom moderation pending requests & heldmsg files

[Mark Sapiro]

Chris Waltham wrote:

>Can you think of an easy way to discard all the messages in  
>request.pck _except those_ which still have tokens remaining in  
>pending.pck?


If you're willing to accept that the only messages that have unexpired
tokens left in pending.pck are those newer than PENDING_REQUEST_LIFE
which defaults to 3 days, you can use the method suggested in the FAQ

 $ cd ~mailman
 $ find data -name heldmsg--\* -print | xargs bin/discard

but make it

 $ cd ~mailman
 $ find data -name heldmsg-\* -mtime +3 -print | xargs bin/discard

-- 
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] Phantom moderation pending requests & heldmsg files

[Chris Waltham]

On May 7, 2008, at 4:07 PM, Mark Sapiro wrote:

I looked at my heldmsg files (all 40,000 of them :-)) and there  
are a
number patterns. Most heldmsg files are from a handful of lists  
(let's

call them baseball and football). If I do a dumpdb of the hockey
list's pending.pck file, this is the output:

[EMAIL PROTECTED] ~/bin]$ ./dumpdb ../lists/hockey/pending.pck
[- start pickle file -]
<- start object 1 ->
{   '6183e43cf99b4a6850537d2a4837b26886bade2a': ('H', 5145),
   'd22c46a0b5c704ec8be5c63a791e53adc23dc7fc': ('H', 5146),
   'df7eae0e0a275c43b9c4bfb8d5f037df578e6cc2': ('H', 5147),



Note that the entries in lists/hockey/pending.pck are only the
confirmation tokens and they expire after (default) 3 days, so there
may normally be lots of held messages that are not in pending.pck.


Okay.


The tokens in pending.pck are for the submitter of the held message to
be able to cancel the post or for the admin/moderator to be able to
cancel or approve the post by email. They have nothing to do with
what's in the admindb interface which is controlled by what's in the
request.pck file.


Okay. :-) That clears up things very well, thank you.

[EMAIL PROTECTED] ~/lists/hockey]$ dumpdb request.pck | grep heldmsg | wc -l
3835



Now, the first line ends with the value "5145". Here is what I can
find on the filesystem:

[EMAIL PROTECTED] ~/data]$ ls -al heldmsg-hockey* | grep 5145
-rw-rw-r--  1 mailman mailman   3395 May  4 12:54 heldmsg-
hockey-5145.pck

I rinsed & repeated that process with the other two entries in the
pending.pck file, i.e. 5146 and 5147. For both of those two, I can
find heldmsg-hockey-.pck (where  equals the ID above).
However, I still have an awful lot of heldmsg-hockey files that
are .txt files, not .pck files:



The fact that they are .txt files is not a problem per se. As long as
there are entries in request.pck for them, they should appear in the
admindb interface and can be approved if you wish, or rejected or
discarded.


Now if I run bin/discard, that will discard all the messages in  
request.pck, right? As per this FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.074.htp


Can you think of an easy way to discard all the messages in  
request.pck _except those_ which still have tokens remaining in  
pending.pck?



Chris
--
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] Phantom moderation pending requests & heldmsg files

[Mark Sapiro]

Chris Waltham wrote:

>Hi Mark,
>
>Just to re-visit this...
>
>On Apr 8, 2008, at 1:24 PM, Mark Sapiro wrote:
>
>> Chris Waltham wrote:
>>>
>>> With the exception of 3-4 lists (out of 800+), I let the "make  
>>> update"
>>> command run so I presume that actually upgraded the lists. I think I
>>> might just delete the holdmsg files en masse, I can't see why
>>> (organizationally) I should need to keep them.
>>
>>
>> When you delete these files, it is better to use bin/discard as
>> discussed in
>> 
>> rather than just rm. This is because bin/discard actually removes the
>> held message from the requests.pck file (see below). However, if the
>> heldmsg-* file is an orphan, it won't be removed by bin/discard, so
>> you need to run bin/discard first and then rm any files left.
>>
>> The problem with just removing the heldmsg-* file is if there are a
>> large number of held messages for a single list, the admindb CGI can
>> time out trying to create the held messages page, and just removing
>> the heldmsg-* files without also removing the request.pck entries
>> won't cure this time out.
>
>I looked at my heldmsg files (all 40,000 of them :-)) and there are a  
>number patterns. Most heldmsg files are from a handful of lists (let's  
>call them baseball and football). If I do a dumpdb of the hockey  
>list's pending.pck file, this is the output:
>
>[EMAIL PROTECTED] ~/bin]$ ./dumpdb ../lists/hockey/pending.pck
>[- start pickle file -]
><- start object 1 ->
>{   '6183e43cf99b4a6850537d2a4837b26886bade2a': ('H', 5145),
> 'd22c46a0b5c704ec8be5c63a791e53adc23dc7fc': ('H', 5146),
> 'df7eae0e0a275c43b9c4bfb8d5f037df578e6cc2': ('H', 5147),


Note that the entries in lists/hockey/pending.pck are only the
confirmation tokens and they expire after (default) 3 days, so there
may normally be lots of held messages that are not in pending.pck.

The tokens in pending.pck are for the submitter of the held message to
be able to cancel the post or for the admin/moderator to be able to
cancel or approve the post by email. They have nothing to do with
what's in the admindb interface which is controlled by what's in the
request.pck file.


>Now, the first line ends with the value "5145". Here is what I can  
>find on the filesystem:
>
>[EMAIL PROTECTED] ~/data]$ ls -al heldmsg-hockey* | grep 5145
>-rw-rw-r--  1 mailman mailman   3395 May  4 12:54 heldmsg- 
>hockey-5145.pck
>
>I rinsed & repeated that process with the other two entries in the  
>pending.pck file, i.e. 5146 and 5147. For both of those two, I can  
>find heldmsg-hockey-.pck (where  equals the ID above).  
>However, I still have an awful lot of heldmsg-hockey files that  
>are .txt files, not .pck files:


The fact that they are .txt files is not a problem per se. As long as
there are entries in request.pck for them, they should appear in the
admindb interface and can be approved if you wish, or rejected or
discarded.

If they are not in request.pck and do not appear in the admindb
interface, all you can do is remove the files or 'repost' the messages
using bin/inject


>[EMAIL PROTECTED] ~/data]$ ls -al heldmsg-hockey*.txt | wc -l
>3610
>
>[EMAIL PROTECTED] ~/data]$ ls -alt heldmsg-hockey*.txt | head
>-rw-rw-r--  1 mailman mailman   2210 Mar 13 08:42 heldmsg- 
>hockey-4920.txt
>-rw-rw-r--  1 mailman mailman   3250 Mar 13 08:14 heldmsg- 
>hockey-4919.txt
>-rw-rw-r--  1 mailman mailman   3646 Mar 13 01:18 heldmsg- 
>hockey-4918.txt
>-rw-rw-r--  1 mailman mailman   2505 Mar 12 03:50 heldmsg- 
>hockey-4917.txt
>-rw-rw-r--  1 mailman mailman   2377 Mar 12 03:50 heldmsg- 
>hockey-4916.txt
>-rw-rw-r--  1 mailman mailman   2815 Mar 11 14:38 heldmsg- 
>hockey-4915.txt
>-rw-rw-r--  1 mailman mailman   2354 Mar 10 12:02 heldmsg- 
>hockey-4914.txt
>-rw-rw-r--  1 mailman mailman   2591 Mar 10 11:28 heldmsg- 
>hockey-4913.txt
>-rw-rw-r--  1 mailman mailman   2227 Mar 10 11:19 heldmsg- 
>hockey-4912.txt
>-rw-rw-r--  1 mailman mailman   2551 Mar 10 11:19 heldmsg- 
>hockey-4911.txt
>
>I think March 10 is around the time that I went from Mailman 2.0.12 to  
>2.1.9. Now my question is this: does Mailman 2.1.9 reference .txt  
>files for heldmessages, or are we only using .pck files now?


Theis is controlled by HOLD_MESSAGES_AS_PICKLES which defaults to Yes
but can be set to No in mm_cfg.py.

-- 
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.

Re: [Mailman-Users] Phantom moderation pending requests & heldmsg files

[Chris Waltham]

Hi Mark,

Just to re-visit this...

On Apr 8, 2008, at 1:24 PM, Mark Sapiro wrote:


Chris Waltham wrote:


With the exception of 3-4 lists (out of 800+), I let the "make  
update"

command run so I presume that actually upgraded the lists. I think I
might just delete the holdmsg files en masse, I can't see why
(organizationally) I should need to keep them.



When you delete these files, it is better to use bin/discard as
discussed in

rather than just rm. This is because bin/discard actually removes the
held message from the requests.pck file (see below). However, if the
heldmsg-* file is an orphan, it won't be removed by bin/discard, so
you need to run bin/discard first and then rm any files left.

The problem with just removing the heldmsg-* file is if there are a
large number of held messages for a single list, the admindb CGI can
time out trying to create the held messages page, and just removing
the heldmsg-* files without also removing the request.pck entries
won't cure this time out.


I looked at my heldmsg files (all 40,000 of them :-)) and there are a  
number patterns. Most heldmsg files are from a handful of lists (let's  
call them baseball and football). If I do a dumpdb of the hockey  
list's pending.pck file, this is the output:


[EMAIL PROTECTED] ~/bin]$ ./dumpdb ../lists/hockey/pending.pck
[- start pickle file -]
<- start object 1 ->
{   '6183e43cf99b4a6850537d2a4837b26886bade2a': ('H', 5145),
'd22c46a0b5c704ec8be5c63a791e53adc23dc7fc': ('H', 5146),
'df7eae0e0a275c43b9c4bfb8d5f037df578e6cc2': ('H', 5147),

Now, the first line ends with the value "5145". Here is what I can  
find on the filesystem:


[EMAIL PROTECTED] ~/data]$ ls -al heldmsg-hockey* | grep 5145
-rw-rw-r--  1 mailman mailman   3395 May  4 12:54 heldmsg- 
hockey-5145.pck


I rinsed & repeated that process with the other two entries in the  
pending.pck file, i.e. 5146 and 5147. For both of those two, I can  
find heldmsg-hockey-.pck (where  equals the ID above).  
However, I still have an awful lot of heldmsg-hockey files that  
are .txt files, not .pck files:


[EMAIL PROTECTED] ~/data]$ ls -al heldmsg-hockey*.txt | wc -l
3610

[EMAIL PROTECTED] ~/data]$ ls -alt heldmsg-hockey*.txt | head
-rw-rw-r--  1 mailman mailman   2210 Mar 13 08:42 heldmsg- 
hockey-4920.txt
-rw-rw-r--  1 mailman mailman   3250 Mar 13 08:14 heldmsg- 
hockey-4919.txt
-rw-rw-r--  1 mailman mailman   3646 Mar 13 01:18 heldmsg- 
hockey-4918.txt
-rw-rw-r--  1 mailman mailman   2505 Mar 12 03:50 heldmsg- 
hockey-4917.txt
-rw-rw-r--  1 mailman mailman   2377 Mar 12 03:50 heldmsg- 
hockey-4916.txt
-rw-rw-r--  1 mailman mailman   2815 Mar 11 14:38 heldmsg- 
hockey-4915.txt
-rw-rw-r--  1 mailman mailman   2354 Mar 10 12:02 heldmsg- 
hockey-4914.txt
-rw-rw-r--  1 mailman mailman   2591 Mar 10 11:28 heldmsg- 
hockey-4913.txt
-rw-rw-r--  1 mailman mailman   2227 Mar 10 11:19 heldmsg- 
hockey-4912.txt
-rw-rw-r--  1 mailman mailman   2551 Mar 10 11:19 heldmsg- 
hockey-4911.txt


I think March 10 is around the time that I went from Mailman 2.0.12 to  
2.1.9. Now my question is this: does Mailman 2.1.9 reference .txt  
files for heldmessages, or are we only using .pck files now?


Thanks!


Chris

--
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] clarification on virtual domains

[Paul]

On Wed, May 7, 2008 5:07 am, bijayant kumar wrote:
> Hi list,
>
> I have postfix configure for virtual domain. Whenever
> i add a new list for a new domain, it takes the
> [EMAIL PROTECTED] as a email address for
> newly created list and all the aliases being generated
> on the basis of previousdomain.com. When i change the
> default host this list prefers setting from the
> interface, then mails are started to bounce saying
> user unknown in virtual mailbox table. I will explain
> my problem with the example...
> I have three virtual domain dom1.com,
> dom2.com,dom3.com
> in mm_cfg.py i have
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
> add_virtualhost('lists.bijayant.com', 'dom1.com')
>
> It works fine. lists created takes the address
> [EMAIL PROTECTED]
>
> But when i add a new list say list2 like
>
> POSTFIX_STYLE_VIRTUAL_DOMAINS =
> ['dom1.com','dom2.com']
> add_virtualhost('lists.bijayant.com', 'dom1.com')
> add_virtualhost('lists.bijayant.com', 'dom2.com')

Try setting your new domain in postfix in this setting:

mydestination = newdomain.com

Then it will use the mailman aliases or you will need to manual set all
aliasing in the postfix aliasing.





--
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] clarification on virtual domains

[Mark Sapiro]

bijayant kumar wrote:
>
>I have postfix configure for virtual domain. Whenever
>i add a new list for a new domain, it takes the
>[EMAIL PROTECTED] as a email address for
>newly created list and all the aliases being generated
>on the basis of previousdomain.com. When i change the
>default host this list prefers setting from the
>interface, then mails are started to bounce saying
>user unknown in virtual mailbox table. I will explain
>my problem with the example...
>I have three virtual domain dom1.com,
>dom2.com,dom3.com
>in mm_cfg.py i have
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
>add_virtualhost('lists.bijayant.com', 'dom1.com')
>
>It works fine. lists created takes the address
>[EMAIL PROTECTED]
>
>But when i add a new list say list2 like
>
>POSTFIX_STYLE_VIRTUAL_DOMAINS =
>['dom1.com','dom2.com']
>add_virtualhost('lists.bijayant.com', 'dom1.com')
>add_virtualhost('lists.bijayant.com', 'dom2.com')
>
>The newly created list2 takes the address
>[EMAIL PROTECTED]


Are you sure it isn't the other way around? When you have

add_virtualhost('lists.bijayant.com', 'dom1.com')
add_virtualhost('lists.bijayant.com', 'dom2.com')

The second entry effectively replaces the first because what they do is
add entries to a Python dictionary (a hash table). The first argument
is the key and the second is the value. So the first above makes an
entry with key 'lists.bijayant.com' and value 'dom1.com' and the
second replaces the value for key 'lists.bijayant.com' with 'dom2.com'

>when i update hostname setting from the list2
>Administrative interface, mail start bouncing.


If you run Mailman's bin/genaliases after editing the list's host_name,
that should fix the virtual maps.

-- 
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] clarification on virtual domains

[Barry Finkel]

bijayant kumar <[EMAIL PROTECTED]> wrote:

>Hi list,
>
>I have postfix configure for virtual domain. Whenever
>i add a new list for a new domain, it takes the
>[EMAIL PROTECTED] as a email address for
>newly created list and all the aliases being generated
>on the basis of previousdomain.com. When i change the
>default host this list prefers setting from the
>interface, then mails are started to bounce saying
>user unknown in virtual mailbox table. I will explain
>my problem with the example...
>I have three virtual domain dom1.com,
>dom2.com,dom3.com
>in mm_cfg.py i have
>POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
>add_virtualhost('lists.bijayant.com', 'dom1.com')
>
>It works fine. lists created takes the address
>[EMAIL PROTECTED]
>
>But when i add a new list say list2 like
>
>POSTFIX_STYLE_VIRTUAL_DOMAINS =
>['dom1.com','dom2.com']
>add_virtualhost('lists.bijayant.com', 'dom1.com')
>add_virtualhost('lists.bijayant.com', 'dom2.com')
>
>The newly created list2 takes the address
>[EMAIL PROTECTED]
>
>when i update hostname setting from the list2
>Administrative interface, mail start bouncing.
>
>I hope i am able to convey my problem.
>
>My question is how to achieve this, i have read some
>articles and tried to follow those but without any
>success. Please guide me to achieve this.

How do you create the new list?  If via the command line

 /usr/sbin/newlist  LISTNAME

then you need a first parameter

 /usr/sbin/newlist -e DOMAIN LISTNAME

for example,

 /usr/sbin/newlist -e dom2.com  mynewlist

Use

 /usr/sbin/newlist -h

to get the help information for the newlist command.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
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] clarification on virtual domains

[bijayant kumar]

Hi list,

I have postfix configure for virtual domain. Whenever
i add a new list for a new domain, it takes the
[EMAIL PROTECTED] as a email address for
newly created list and all the aliases being generated
on the basis of previousdomain.com. When i change the
default host this list prefers setting from the
interface, then mails are started to bounce saying
user unknown in virtual mailbox table. I will explain
my problem with the example...
I have three virtual domain dom1.com,
dom2.com,dom3.com
in mm_cfg.py i have
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom1.com']
add_virtualhost('lists.bijayant.com', 'dom1.com')

It works fine. lists created takes the address
[EMAIL PROTECTED]

But when i add a new list say list2 like

POSTFIX_STYLE_VIRTUAL_DOMAINS =
['dom1.com','dom2.com']
add_virtualhost('lists.bijayant.com', 'dom1.com')
add_virtualhost('lists.bijayant.com', 'dom2.com')

The newly created list2 takes the address
[EMAIL PROTECTED]

when i update hostname setting from the list2
Administrative interface, mail start bouncing.

I hope i am able to convey my problem.

My question is how to achieve this, i have read some
articles and tried to follow those but without any
success. Please guide me to achieve this.


Bijayant Kumar

Send instant messages to your online friends http://uk.messenger.yahoo.com 
--
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