Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fine on SMTP)

[Adam McGreggor]

On Tue, Jun 16, 2009 at 11:37:30PM -0700, Rick Moen wrote:
> Greetings, good people.  Problem summary:  After server rebuild, 
> virtual hosts work for SMTP, but Mailman's Web pages are appearing
> for the main host only and _not_ the virtual host.

[...]

> After some fussing about concerning exim4/mailman integration, I
> stumbled on details about POSTFIX_STYLE_VIRTUAL_DOMAINS and its use even
> with non-Postfix MTAs.  (I put the required plumbing into
> /etc/exim4/conf.d/*.  It works.)  I did read the Debian folks'
> /usr/share/doc/mailman/README.Exim4.Debian , which includes in part:

I would not touch that. Even with the travesty that is Pkg-exim4, I
still use something along the lines (pretty much) of that per


>   Here's a way to integrate mailman with Exim4 that will automatically
>   play nice with mailman's virtual domains support and VERP. It does not
>   require dedicating domain(s) to mailman.

My kludges don't care about subdomains/"list only" domains.

> http://files.technomage.net/postfix_mailman.txt -- and, consequently, 
> completed Exim integration by running /var/lib/mailman/bin/genaliases, 
> and, lo!  /var/lib/mailman/data/{aliases|virtual-mailman} came into
> existence, and Exim stopped generating errors.  More important, the
> Exim/Mailman jointly [re-]started processing mail for the mailing lists
> within both domains.  Life was good.  Almost.

IMO, life's waaay too short to genaliases. the configs in
Nigel's doc makes that a thing of the past (it's probably worth
noting, I am a lazy sysadmin, and i automate as much as possible, and
just couldn't make sense of Postfix when i inherited a box with
postfix as its MTA: that got changed).

> There remains the matter of Mailman's Web pages:  Those for domain
> linuxmafia.com are present.  (See: http://linuxmafia.com/mailman/listinfo/)
> Those for domain lists.linuxgazette.net are not.  See:
> http://lists.linuxgazette.net/mailman/listinfo/ -- as you'll notice,
> Apache2 does recognise the domain.  The Apache document root for that
> location, /var/www/gazette, has an .htaccess file in it, as follows:
> 
>   # cat /var/www/gazette/.htaccess 
>   redirect 301 /index.html
>   http://lists.linuxgazette.net/mailman/listinfo/

that 404's for me: have you got the Mailman Apache stanzas set-up in
lists.linuxgazette.net's vhost config? I've not had issues using
ServerAlias directives, fwiw.

[...]

You may need a 'clear' clause before the line below: search the
archives of this list for discussions/thoughts/advice thereto.

>   VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}
[...]

>   MTA = 'Postfix'

I'd change that, as you're using Exim.

HTH

-- 
"We used to quip that "password" is the most common password. Now 
 it's "password1." Who said users haven't learned anything about 
 security?"
  (Bruce Schneier, December 2006)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman 2.1.9 incorrectly holding messages for "Reason: Message has implicit destination"

[Barry Finkel]

"Schmitt, Gordon A."  wrote:

>We had been using mailman 2.1.5 installed on Redhat Enterprise v3.n for
>several years .  A few months ago, we installed a new Redhat system for
>our mailing list server, Redhat Enterprise Linux Server release 5.3
>(Tikanga) which has Mailman 2.1.9 installed. I followed various
>instructions on migrating the mailing lists and everything seemed to be
>working just fine. However, within the past few weeks we noticed that
>some users sending to their favorite lists are having a lot of trouble
>with their messages being held as: "Reason:Message has implicit
>destination" . Many users do not have this happen.  I have been
>investigating and testing and I can not figure out why. Our main campus
>mail system is Exchange 2007.  They have put the address in the correct
>place, i.e. The To: or CC: fields.
>
>We create exchange contacts for each mailing list that forwards the
>message to the mailing list server, e.g. listn...@stcloudstate.edu
>forwards to listn...@lserver.stcloudstate.edu and there was never any
>problems for the past several years before our upgrade.  Below is the
>header info from a message that is being held that should have passed
>through. Can anyone think of what is causing this behavior for certain
>messages? One person mentioned that it  happenes when he did a
>reply-all to a message and it worked after  creatomg a new message. I
>do not know if this could be related because I tried doing this and all
>my messages went through fine. I may have to experiment more with what
>email client software the messages are being sent from, I mostly use
>Entourage on a Mac. The majority of campus use Outlook on some version
>of Windows.

Have you set

 listn...@stcloudstate.edu

as an acceptable_alias for

 listn...@lserver.stcloudstate.edu

via

 o Privacy options...
  o Recipient filters

If not, then Mailman does not know that the shorter name is actually
an acceptable name for the real list name.
--
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: bsfin...@anl.gov
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman 2.1.9 incorrectly holding messages for"Reason: Message has implicit destination"

[Mark Sapiro]

Schmitt, Gordon A. wrote:

> Below is the header info from a message that is being held that should have 
> passed through. Can anyone think of what is causing this behavior for certain 
> messages? One person mentioned that it  happenes when he did a reply-all to a 
> message and it worked after  creatomg a new message. I do not know if this 
> could be related because I tried doing this and all my messages went through 
> fine. I may have to experiment more with what email client software the 
> messages are being sent from, I mostly use Entourage on a Mac. The majority 
> of campus use Outlook on some version of Windows.

[...]

>To: "Olagunju, Am O." ,
>"listn...@stcloudstate.edu"
>
> 


Are the HTML entities (", < and >) actually in the message
header or are they artifacts from some web copy/paste operation? Even
assuming those are just an artifact, the above header is

To: "Olagunju, Am O." ,
"listn...@stcloudstate.edu"
   


What is all that
"IMCEAEX-_O=SCSU_OU=First+20Administrative+20Group_cn=Recipients_cn="
prepended to "listname" If that is what the To: header actially looked
like, that's the problem.

I would not be surprised to find that Outlook did something to the
address in the To: header of the reply that could cause this, but I
haven't heard of it.

In another reply, Barry Finkel suggests adding
listn...@stcloudstate.edu to acceptable_aliases for the
listn...@lserver.stcloudstate.edu list. While this is a good idea, it
will not solve the problem in this case, because as a deprecated,
backwards compatibility feature, Mailman 2.1.x will accept any address
as the list address if the list name matches even if the domains don't.


-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] attachments renamed in archives

[Mark Sapiro]

Gruver, Sandi wrote:

>I have this line in the  mm_cfg.py file:
>SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True, but attachments (.pdf) are 
>being renamed to .obj.
>
>Can you please give a big hint as to what do I need to do to fix this?


Do the MIME headers of the attachment have a Content-Disposition:
header with a filename= or name= parameter with the .pdf extension. If
so, Scrubber should use it. Even if not, Scrubber will normally guess
'.pdf' for the extension if the Content-Type is application/pdf.

The fact that the attachment is saved with a .obj extension indicates
the sending MUA may be giving it MIME type application/octet-stream
rather than application/pdf, and not giving it a filename.

To say more, we would need the actual MIME headers from the attachment.
You can find these in the archives/private/LISTNAME.mbox/LISTNAME.mbox
file.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Virtual domain not quite working on HTTP (but fineon SMTP)

[Mark Sapiro]

Rick Moen wrote:
>
>There remains the matter of Mailman's Web pages:  Those for domain
>linuxmafia.com are present.  (See: http://linuxmafia.com/mailman/listinfo/)
>Those for domain lists.linuxgazette.net are not.  See:
>http://lists.linuxgazette.net/mailman/listinfo/ -- as you'll notice,
>Apache2 does recognise the domain.  The Apache document root for that
>location, /var/www/gazette, has an .htaccess file in it, as follows:
>
>  # cat /var/www/gazette/.htaccess 
>  redirect 301 /index.html
>  http://lists.linuxgazette.net/mailman/listinfo/
>
>If I mv .htaccess to .htacces-save for diagnostic purposes, I _do_ 
>see the contents of /var/www/gazette/ in my browser, so this is not 
>an Apache vhost problem.


Yes it is. 'listinfo' is a CGI. You need a

ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/"

(or whatever the correct path is) in your httpd.conf where it will
apply to the lists.linuxgazette.net host. I.e. it needs to be in the
VirtualHost block for each host with lists or it needs to be outside
of the virtual hosts section so it applies globally.


>Here is what I imagine is the relevant part of my current
>/var/lib/mailman/Mailman/mm_cfg.py :
>
>  # Default domain for email addresses of newly created MLs
>  DEFAULT_EMAIL_HOST = 'linuxmafia.com'
>  #-
>  # Default host for web interface of newly created MLs
>  DEFAULT_URL_HOST   = 'linuxmafia.com'
>  #-
>  # Required when setting any of its arguments.
>  add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>  add_virtualhost('lists.linuxgazette.net', 'lists.linuxgazette.net')
>[...]


This looks good, but is not relevant to your issue, at least not until
you fix Apache so that http://lists.linuxgazette.net/mailman/listinfo/
gets you to the Mailman listinfo CGI.


>  # Uncomment if you use Postfix virtual domains, but be sure to
>  # see /usr/share/doc/mailman/README.Debian first.
>  # MTA='Postfix'
>  MTA = 'Postfix'
>  POSTFIX_ALIAS_CMD = '/bin/true'
>  POSTFIX_MAP_CMD = 'chgrp Debian-exim'
>  POSTFIX_STYLE_VIRTUAL_DOMAINS = ['linuxmafia.com', 'lists.linuxgazette.net']
>  VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}


Get rid of the above line. It undoes everything you did with
add_virtualhost directives above.


>  VIRTUAL_HOST_OVERVIEW = 1
>
>
>Here is what I imagine is the relevant part of my current
>/var/lib/mailman/Mailman/Default.py:
>
>  
>  # Virtual domains
>  #
>
>  # Set up your virtual host mappings here.  This is primarily used for the
>  # thru-the-web list creation, so its effects are currently fairly limited.
>  # Use add_virtualhost() call to add new mappings.  The keys are strings as
>  # determined by Utils.get_domain(), the values are as appropriate for
>  # DEFAULT_HOST_NAME.
>  VIRTUAL_HOSTS = {'lists.linuxgazette.net':'lists.linuxgazette.net'}


Where did this come from. If you put it there, you shouldn't be
changing Defaults.py at all. If it's part of the Debian package, I
don't know what to say.


[...]
>  # MTA = 'Manual'
>  MTA = 'Postfix'
>
[...]
>  #POSTFIX_STYLE_VIRTUAL_DOMAINS = []
>  POSTFIX_STYLE_VIRTUAL_DOMAINS = ['linuxmafia.com', 'lists.linuxgazette.net'


DON'T CHANGE Defaults.py

Make all your changes in mm_cfg.py.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman 2.1.9 incorrectly holding messagesfor"Reason: Message has implicit destination"

[Mark Sapiro]

Schmitt, Gordon A. wrote:
>
>The text '.."listn...@stcloudstate.edu"..' is copied from Mailman's 
>Message Headers textbox of a held message and that is exactly how it appears 
>in that textbox.


Yeah, That's Mailman being overprotective against XSS attacks. The HTML
entities are seen in the text box in the admindb interface, but the
received message contains the actual characters, so that's not the
problem.


>The "IMCEAEX-_O=SCSU_OU=First+20Administrative+20Group_cn=Recipients_cn=" 
>comes from the exchange server. It seems to  show up that why for held 
>moderated messages too(that pass through without problems).


If you're saying you see this in messages held for some other reason
(moderated member), and those messages pass through OK after approval,
that means nothing. Moderation and non-member tests are done first
followed by administrivia and "too many recipients" before "implicit
destination. Once approved, a held message will not be held again for
any reason. Thus, a message that meets the test for "implicit
destination" can be held for "moderated member", "non-member post",
"administrivia" or "too big", and if approved will then go to the list.

If that string is the problem, you could try adding to
acceptable_aliases

^.*listname@(lserver\.)?stcloudstate\.edu$

(a regexp that matches anything ending in listn...@stcloudstate.edu or
listn...@lserver.stcloudstate.edu) or if the last "=" is always there

^(.*=)?listname@(lserver\.)?stcloudstate\.edu$

which will match listn...@stcloudstate.edu or
listn...@lserver.stcloudstate.edu possibly preceded with anything
ending in "=".


>I found out from another user today that it happens to them when they reply of 
>forward a message to listn...@stcloudstate.edu, but not if they create a new 
>message. This is the second person that has informed me of this behavior. I 
>plan to visit his office and observe what his Outlook is doing.


Also, have him Cc or Bcc you on an original message and a reply/forward
so you can see what the To: and Cc: headers look like in the two cases.


[...]
>Are there any log files worth looking at, or additional mailman logging that I 
>can setup that might be helpful?


The only logging is Mailman's Vette log, and that doesn't show anything
that isn't already in the admindb interface.


>Do you think the HTML entities could be causing the problem? Or more likely 
>the 
>?
> Do either of these contain characters that would cause Mailman to not match 
>"listn...@stcloudstate.edu" even though it is in the string?


The test is a match against the whole address so the only way to ignore
the leading junk is with a regexp in acceptable_aliases such as the
ones above that explicitly skips stuff at the beginning.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] clear messages held for moderation ..

[Khalil Abbas]

hello ..

 

is there a way to delete all the messages that are held for moderation via 
command prompt i.e. SSH ??

 

thanks ..

 

_
Drag n’ drop—Get easy photo sharing with Windows Live™ Photos.

http://www.microsoft.com/windows/windowslive/products/photos.aspx
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] clear messages held for moderation ..

[Terri Oda]

Khalil Abbas wrote:

is there a way to delete all the messages that are held for moderation via 
command prompt i.e. SSH ??


The short answer is use bin/discard

See the FAQ entry at http://wiki.list.org/x/nIA9 for more details.

 Terri
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Virtual Domains for Mailing Lists in MailMan

[Mark Sapiro]

Bryan Harrison wrote:
>
>I've found the resources you recommended helpful, but am stymied  
>nonetheless.  I'm bright but not expert with Postfix or Mailman, and  
>have been butting my head against this for days.
>
>As a test, I'm trying to install mailman on the server gilded- 
>bat.laughingboot.net, and create functioning lists mail...@laughingboot.net 
>  and gal...@gurgitate.org.  Virtual domains are humming along nicely  
>in both Apache and Postfix.
>
>Mailman's processes run and I can browse the interface site, but all  
>my tests now bounce with:
>
><"|/usr/share/mailman/mail/mailman post galaxy"@gilded- 
>bat.laughingboot.net>:
>data format error. Command output: |/usr/share/mailman/mail/ 
>mailman post
>galaxy: Bad protocol


See below


>If you're feeling particularly saintly, I've P.S.'d install_mailman.sh  
>below –  the very rough script I'm using to install and configure  
>mailman.
>
>Relevant lines from main.cf are
>
>virtual_alias_maps = hash:/etc/postfix/virtual,hash:/var/mailman/data/ 
>aliases,hash:/var/mailman/data/virtual-mailman


The entry "hash:/var/mailman/data/aliases" should be in alias_maps, not
virtual_alias_maps.


>virtual_mailbox_domains = hash:/etc/postfix/virtual_domains


Your Mailman domains should be virtual_alias_domains.
virtual_mailbox_domains can't deliver properly to Mailman aliases.


>mm_cfg.pys looks like this:
>
># Include Defaults:
>
>from Defaults import *
>
># Site-specific overrides:
>
>MTA = 'Postfix'
>DEFAULT_EMAIL_HOST = 'laughingboot.net'
>DEFAULT_URL_HOST = 'gilded-bat.laughingboot.net'


Probably not absolutely necessary, but put

VIRTUAL_HOSTS.clear()

here to remove the add_virtualhosts entry from Defaults.py.


>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>add_virtualhost('gurgitate.org', 'gurgitate.org')
>POSTFIX_STYLE_VIRTUAL_DOMAINS = 'gurgitate.org'
>DEFAULT_MAX_MESSAGE_SIZE = 1   # KB
>
>I'm running OS X Server 10.5.7.
>
>I'll burn an SUV to the Gods on your behalf if you care to help me out.
>
>Best regards,
>Bryan
>
>
># !/bin/tcsh
># INSTALL MAILMAN TEST
># Last Updated:  2009-06-15
># Assumes prior installation of Xcode.
>
>serveradmin stop mail
>/usr/share/mailman/bin/mailmanctl stop
>
>rm -Rf /var/mailman/*
>rm -Rf /usr/share/mailman/*
>mkdir -p -m ug=rwx,o=rx /var/mailman
>mkdir -p -m a+rx,g+ws /usr/share/mailman
>chown _mailman:_mailman /var/mailman
>chown _mailman:_mailman /usr/share/mailman
>chmod -R 2777 /var/mailman
>chmod -R 2777 /usr/share/mailman


These are a bit permissive - should be 2775.


>
>mkdir -p /Library/TemporaryItems
>cd /Library/TemporaryItems
>
>curl -O 
>http://superb-west.dl.sourceforge.net/sourceforge/mailman/mailman-2.1.12.tgz
>tar -xzf mailman-2.1.12.tgz
>cd mailman-2.1.12
>
># Pick One, anyone, none of them work:
>
># ./configure --prefix=/usr/share/mailman --with-var-prefix=/var/ 
>mailman --with-username=_mailman --with-groupname=_mailman --with-cgi- 
>gid=_www
># ./configure --prefix=/usr/share/mailman --with-var-prefix=/var/ 
>mailman --with-username=_mailman --with-groupname=_mailman --with-mail- 
>gid=_mailman --with-cgi-gid=_www --without-permcheck


The one above should be correct. With Postfix integration, the
"mail-gid" is the primary group of the owner of
/var/mailman/data/aliases.db which should be _mailman. It shouldn't
need --without-permcheck


>./configure --prefix=/usr/share/mailman --with-var-prefix=/var/mailman  
>--with-username=_mailman --with-groupname=_mailman --with-mail- 
>gid=_postfix --with-cgi-gid=_www --without-permcheck
>
>make
>make install
>
>chown _www:_mailman /var/mailman/archives/private
>chmod o-r-x /var/mailman/archives/private
>touch /var/mailman/data/aliases
>touch /var/mailman/data/virtual-mailman


The above two touch shouldn't be needed.



>scp #copy mm_cfg.py from where I'm working on it to its proper home.
>
>/usr/share/mailman/bin/newlist -q mailman br...@laughingboot.net  
>mypassword
>/usr/share/mailman/bin/config_list -i /var/mailman/data/sitelist.cfg  
>mailman
>
>/usr/share/mailman/bin/newlist -q galaxy br...@gurgitate.org mypassword
>/usr/share/mailman/bin/config_list -i /var/mailman/data/sitelist.cfg  
>galaxy


/var/mailman/data/sitelist.cfg is only intended for the site list named
'mailman' (unless you set something different for MAILMAN_SITE_LISTin
mm_cfg.py). You need something like

/usr/share/mailman/bin/newlist -q mailman br...@gurgitate.org mypassword
/usr/share/mailman/bin/config_list -i /var/mailman/data/sitelist.cfg
mailman 

Yo don't want the config_list for other lists.


>/usr/share/mailman/bin/withlist -l -r fix_url galaxy -- 
>urlhost=gurgitate.org


Instead of the above, just create it with

/usr/share/mailman/bin/newlist -q -u gurgitate.org  galaxy
br...@gurgitate.org mypassword



>cd /usr/share/mailman/bin
>./genaliases


If you create the lists in the proper domain with newlist, you don't
need genaliases at this point.


>serveradmin start mail
>./mailmanctl -s start
>./check_perms -f


Do the check_pe

Re: [Mailman-Users] Virtual Domains for Mailing Lists in MailMan

[Mark Sapiro]

Bryan Harrison 
>
>A minor puzzle, just in case you're interested:
>
>You'll be unsurprised that I found virtual_mailbox_domains and  
>virtual_alias_domains will fight over any domain common to both.   
>Since OS X Server is dependent on virtual_mailbox_domains , I did my  
>usual blind monkey try-this-and-that and discovered it works fine  
>without virtual_alias_domains.  I won't pretend to understand, but am  
>wondering if I've created something that will be less than robust.


I'm far from a Postfix expert, and I'm not sure what's going on in your
case. My understanding is that with virtual_mailbox_domains, mail to
such a domain is always delivered to a mailbox or mail directory, and
aliases such as those which pipe the mail to a mailman wrapper do not
apply. So, I'm not sure what you have that enables this mail to be
delivered to Mailman.


>And one more question, if you don't mind:
>
>In addition to hosting lists for virtual domains, I need to host  
>listname at the address listn...@laughingboot.net on the server gilded- 
>bat.laughingboot.net.  Is this sufficient?
>
># mm_dfg.py
># 2009-06-16
>
># Include Defaults:
>
>from Defaults import *
>
># Site-specific overrides:
>
>MTA = 'Postfix'
>DEFAULT_EMAIL_HOST = 'laughingboot.net'
>DEFAULT_URL_HOST = 'gilded-bat.laughingboot.net'
>VIRTUAL_HOSTS.clear()
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>add_virtualhost('gurgitate.org', 'gurgitate.org')
>POSTFIX_STYLE_VIRTUAL_DOMAINS = 'gurgitate.org'


The above is sufficient and (almost) correct if laughingboot.net is a
local (non-virtual) domain as far as Postfix is concerned. Yhe last
line should be

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['gurgitate.org']

POSTFIX_STYLE_VIRTUAL_DOMAINS is a list even if it has only one entry.


>DEFAULT_MAX_MESSAGE_SIZE = 1   # KB
>
>I've read that I need to do this as well...
>
># /etc/postfix/virtual
># 2009-06-09
>
>laughingboot.net   IGNORE
>@laughingboot.net  @mail.laughingboot.net
>
>...but feel like a cargo cult member worshipping a ball point pen when I  
>look at it.  Of course gilded-bat.laughingboot.net needs to continue  
>to handle non-mailing list mail for laughingboot.net as well.


If /etc/postfix/virtual is a virtual_alias_maps file, the first line
above says laughingboot.net is a virtual_alias_domain and is not
required if laughingboot.net is listed explicitly in
virtual_alias_domains in main.cf. The second line says all mail to the
domain laughingboot.net should be routed to mail.laughingboot.net.

If it is a virtual_mailbox_maps file, The first line may work
analogously, but I'm not sure and the second line specifies a mailbox
name to which to deliver laughingboot.net mail.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

[Mailman-Users] Mailman vs OSX vs launchd

[Bryan Harrison]

I've built and installed Mailman 2.12 from current source code and  
have it running just fine under OS X Server 10.5.7, with on exception,  
which is not properly speaking a Mailman problem at all.


If I start Mailman from the CLI, using /usr/share/mailman/bin/ 
mailmanctl -s start, all is well.


If I allow launchd to start it using the following Launch Daemon…


http://www.apple.com/DTDs/PropertyList-1.0.dtd 
">



Label
org.list.mailmanctl
OnDemand

Program
/usr/share/mailman/bin/mailmanctl
ProgramArguments

mailmanctl
-s
start

ServiceIPC




…I get an endless succession of…

Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master  
qrunner.
Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):  
Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling  
respawn: Will start in 9 seconds


…complete with dawn-of-the-dead respawning processes.

I configured Mailman to replicate OSXS's default locations, and it  
runs fine.  It doesn't even break Server Admin, aside from my use of  
virtual domains which ServerAdmin can't handle.


The only difference between my org.list.mailmanctl.plist and Apple's  
is my verb *start*, as opposed to Apple's *startf*.  I'm baffled by  
*startf*, which is not supported by mailman and does nothing, either  
in the CLI or in org.list.mailmanctl.plist.


Obviously this isn't fatal and there are even other ways to insure an  
automatic startup, but I use launchd for such things, Apple more or  
less deprecates other approaches, and it drives me nuts not to  
understand what's going on.


Speak, oh voices of wisdom!

-Bryan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman vs OSX vs launchd

[Larry Stone]

On 6/18/09 7:11 PM, Bryan Harrison at br...@bryanharrison.com wrote:

> I've built and installed Mailman 2.12 from current source code and
> have it running just fine under OS X Server 10.5.7, with on exception,
> which is not properly speaking a Mailman problem at all.
> 
> If I start Mailman from the CLI, using /usr/share/mailman/bin/
> mailmanctl -s start, all is well.
> 
> If I allow launchd to start it
> ŠI get an endless succession ofŠ
> 
> Jun 18 16:50:26 org.list.mailmanctl[1697]: Starting Mailman's master
> qrunner.
> Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl[1697]):
> Stray process with PGID equal to this dead job: PID 1698 PPID 1 Python
> Jun 18 16:50:26 com.apple.launchd[1] (org.list.mailmanctl): Throttling
> respawn: Will start in 9 seconds

Known issue, no idea why. I've been running Mailman on Client OS X since the
Tiger days. As soon as I upgraded to Leopard, I started seeing this happen
intermittently. I have a launchd plist almost identical to yours.

It is intermittent for me. Probably happens about 1 in 3 boots. I try to
remember to check that it's running after reboots. If not, I have a cron job
that runs hourly to check for the proper number of qrunners and send me
e-mail if any or all are missing.

-- 
Larry Stone
lston...@stonejongleux.com
http://www.stonejongleux.com/


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9