[Mailman-Users] how to revert back to local domain only?

[Graham Young]

This is my first time posting. I am a relatively inexperienced Mailman 
administrator but have no trouble with CLI. 

Context is that I have version 2.1.14 installed on an Apple Mac mini running 
client Mac OS 10.6.8. I used Larry Stone's instructions (dated May 2, 2010) for 
installing into /usr/local/mailman. 

MTA is Postfix. I believe that integration with Postfix in my case does NOT 
require postfix-to-mailman.py, but I do not understand enough about that to say 
more. 

My goal is to learn more about how Mailman works, how to administer it. I am 
trying different configurations--getting my feet wet so to speak. 

Above question arises out of curiosity. Having successfully implemented virtual 
domains I now arbitrarily wish to revert this installation to local-domain 
only. 

(It's not so arbitrary: I learn by undoing. Born analyst, I guess.) 

I fully expect to have to delete from main.cf and mm_cfg.py what I had to 
insert there to enable virtual domains. Postfix's virtual_alias_maps 
configuration in main.cf comes to mind. Likewise, I'm thinking Mailman's 
add_virtualhost configuration in from mm_cfg.py would be another. 

But what about Mailman's VIRTUAL_HOSTS.clear config in mm_cfg.py? Do I take 
that out too?

Furthermore, I am aware that once configured for virtual domains, mailman 
automatically generates certain files: /usr/local/mailman/data/virtual_mailman, 
among others. However, it is not clear to me whether these files will 
automatically be removed or whether their removal requires my intervention. 
Indeed I don't even know that they would need to be removed. 

Finally, there is bound to be more to this than I merely anticipate. Perhaps 
there are other files to modify or remove. 

Someone please advise. 

Many thanks,
Graham Young 
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] problem with Mailman on Mac OS X Snow Leopard client

[Graham Young]

Mail generated by Mailman hangs in my dedicated, on-board MTA's queue unless I 
remove a certain bit of custom Postfix configuration that I entered following 
instructions kindly posted here by one Larry Stone. The instruction in question 
are those for building Mailman on above platform directly from code downloaded 
from a source referenced on list.org and the configuration in question is one 
involving alias maps. 

Everything about this build of Mailman seems to be working fine. I can create 
lists and add or remove members. New members receive the expected mail--but 
here's the catch: only if I remove the above mentioned bit of custom Postscript 
configuration.

I came to suspect this bit of custom Postscript configuration exactly because 
Postfix reported an error involving it. Therefore I removed the bit of custom 
Postscript configuration to see if the queue would clear and it did. 

Everyone got their mail.  

However and of course, I question whether I can just remove this bit of custom 
Postscript configuration without consequences. Mailman-users may seem unlikely 
as a place to inquire about this; but, again, the instruction to use this bit 
of custom Postfix configuration came from a poster to this list whose 
particular posting is cited on list.org as authoritative. 

I am running Mailman on an Intel Mac mini with the client version of Mac OS X 
Snow Leopard installed. I will gladly post more details about my platform 
although I am not sure what might be needed.

The bit of custom Postfix configuration that I've experimented with removing is 
exactly as follows:
hash:/etc/postfix/aliases

The context in which this bit is supposed to appear is as follows:
alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases.

I just remove the bit, leaving:
alias_maps = hash:/usr/local/mailman/data/aliases.
Again, with just this as remnant of my custom Postscript configuration, 
Mailman-generated mail gets sent. 

The error message that Postfix repeatedly issues when I don't have the suspect 
portion of this bit of custom Postscript configuration removed is as follows:
Oct 10 21:10:05 email postfix/local[75578]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:10:06 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75578 exit status 1
Oct 10 21:10:06 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:11:06 email postfix/local[75583]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:11:07 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75583 exit status 1
Oct 10 21:11:07 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:12:07 email postfix/local[75584]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:12:08 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75584 exit status 1
Oct 10 21:12:08 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling
Oct 10 21:13:08 email postfix/local[75593]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory
Oct 10 21:13:09 email postfix/master[141]: warning: process 
/usr/libexec/postfix/local pid 75593 exit status 1
Oct 10 21:13:09 email postfix/master[141]: warning: /usr/libexec/postfix/local: 
bad command startup -- throttling

One can see why I investigated Postscript alias maps upon seeing these log 
entries. I obviously don't understand them, though. 

Finally, inasmuch as it may be relevant, I next post feedback that I get from a 
certain postconf command, specifically postconf alias_maps:
alias_maps = hash:/etc/aliases

Seeing this as the feedback to said command, makes we wonder: Wouldn't the 
correct feedback here include reference to Mailman's own aliases file given 
what remains of my custom Postscript configuration? 

Anyway, something is certainly wrong. Assistance, if offered, will be much 
appreciated. Indeed thanks for even reading this since its the first thing I 
hope for that people read about my problem. 

Hopefully, I have posted well for starters but i am more than happy to take 
hints about what else I need to submit. I am a first time poster. 

Graham

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org