Re: [Mailman-Users] Virtual hosts

2007-04-09 Thread Ira Goldstein
Mark --
  Hi.  The list's host_name on the web page does reflect the desired virtual 
host name.  I've tried the add_virtualhost as

add_virtualhost('dom2.ain', 'dom2.ain')

both with and without:

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

but did not see any difference in the system response.

I've spent the weekend reading up on postfix, but can not see where postfix is 
rewriting the header (I'm not saying that it isn't doing this, just that with 
my limited knowledge, I don't see it). 
The  local_header_rewrite_clients  in canonical is commented out (as is every 
line in the file).
The alias_database and local_recipient_maps are commented out in main.cf
The relocated and generic files also contains just comments

The masquerade* and virtual commands in main.cf are:
masquerade_exceptions = root
masquerade_classes = envelope_sender, header_sender, header_recipient
masquerade_domains = 
virtual_alias_maps = hash:/etc/postfix/virtual, 
hash:/var/lib/mailman/data/virtual-mailman, 
hash:/var/lib/mailman/data/virt-mailman2
virtual_alias_domains = hash:/etc/postfix/virtual
virtual_mailbox_domains = dom2.ain
virtual_uid_maps = static:1001
virtual_gid_maps = static:1050
virtual_mailbox_base = /var/spool/virtual_mailboxes

Interestingly, the lists from dom2.ain appear in both 
/var/lib/mailman/data/aliases as well as in 
/var/lib/mailman/data/virtual-mailman, for example, for the list nine:
aliases:nine-request: |/usr/lib/mailman/mail/mailman request nine
virtual-mailman:[EMAIL PROTECTED]  nine-request

I tried /usr/sbin/sendmail -bv [EMAIL PROTECTED] and saw the following

Enclosed is the mail delivery report that you requested.

The Postfix program

[EMAIL PROTECTED] (expanded from [EMAIL PROTECTED]): delivery
via local: delivers to command: /usr/lib/mailman/mail/mailman post nine


 Any suggestions as to which postfix parameters to change would be greatly 
appreciated.

Thanks
--Ira
 Mark Sapiro [EMAIL PROTECTED] 4/6/2007 1:51 PM 
Ira Goldstein wrote:

Is there a way that mail to  lists on dom2.ain appears as if it comes from
dom2.ain, while keeping mail to lists at dom1.ain appearing as if it comes
from dom1.ain?


If the list's host_name attributes on the General Options page (Host
name this list prefers for email. near the bottom of the page)
reflect the correct virtual domain, then the issue is that your
outgoing MTA is rewriting the domain.


If the host_name attributes are not correct, then you need to look at
your add_virtualhost() directives and perhaps run fix_url (Mailman's
bin/fix_url.py).

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


BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:Ira Goldstein
EMAIL;WORK;PREF:[EMAIL PROTECTED]
TEL;WORK:518-862-5393
ORG:NERIC;e-Tech
TEL;PREF;FAX:518-862-5305
N:Goldstein;Ira
TITLE:Manager
ADR;INTL;WORK;PARCEL;POSTAL:;;1031 Watervliet Shaker Road;Albany;NY;12205;USA
LABEL;INTL;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Ira Goldstein=0A=
1031 Watervliet Shaker Road=0A=
Albany, NY  12205=0A=
USA
LABEL;DOM;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Ira Goldstein=0A=
1031 Watervliet Shaker Road=0A=
Albany, NY  12205
TEL;CELL:178*6111*16
TEL;PREF:518-862-5305
X-GWUSERID:igoldste
X-GWDOMAIN:crb5
X-GWPO:neric5
UID:9749B070-3410--BE83-0060080443B7
X-GWIDOMAIN:gw.neric.org
AOL:aim:ijg57
END:VCARD

--
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=showamp;file=faq01.027.htp

[Mailman-Users] message archiving problem

2007-04-09 Thread Rick Pasotto
I have a couple of lists that I send a weekly message to. This message
has sections that I separate using a line of 60 hyphens. When the
message gets archived the sections are archived separately but only
the first has the correct subject line and the others show 'No Subject'.

Why is this happening?

-- 
Government should be concerned with anti-social conduct,
 not with utterances. -- Justice William Orville Douglas
Rick Pasotto[EMAIL PROTECTED]http://www.niof.net
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] Problem with Installing Mailman 2.1.9 on Solaris

2007-04-09 Thread vancleef
The esteemed David Devereaux-Weber, P.E. has said:
 
 Hank,
 
 I'm still not succeeding in building Mailman.  I'd like to follow 
 another path.  Can you explain why Tcl/TK don't build?  The Python make 
 install command fatals there, and doesn't complete copying some of the 
 modules into the right places.
 
 Dave
 
You're running into problems I haven't encountered, if you can't
install Python without tcl and ssl.  I'd suggest clearing the build
and install directories, doing a fresh unpack of the Python sources, 
and running through the build process again.  My recollection is that
both Python and Mailman will build with the gcc 3.4.2 that is in the
Solaris 10 distribution /usr/sfw directory tree, but that you have to
do some jiggery-pokery with LD_RUN_PATH, LD_LIBRARY_PATH, or crle to
get the builds to find the GNU libraries.  My installations were built
with the Sun development system (Studio 11, installs in
/opt/SUNWspro), so I haven't explored the implications of running with
a GNU build on Solaris 10 very far.

Why Python won't build with the extensions in Solaris is that the
build process doesn't look in /opt/sfw.  I've done enough porting
exploration to see that a fix involves adding a search to those
directories in setup.py (in the Python build base directory), but
haven't explored everything I need to know to assure that I've got an
appropriate fix.  Some queries to the Python users and Python
developers mail lists didn't produce meaningful results, and I'm left
with the feeling that yer on yer own with Python reliability.  What
I can tell you is that my builds of Python 2.4.4 and 2.5, using the
Sun devsys, and without doing any porting work, install and support
Mailman on my systems.  

I'd suggest capturing the outputs of the configure and make steps and
reviewing them.  Also, the various log, makefile, and status files that 
configure generates.  I'm not really prepared to wear a Python
developer hat and try to work Python-on-Solaris problems beyond
getting a Python that will support Mailman.

Hank
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] Problem with Installing Mailman 2.1.9 on Solaris

2007-04-09 Thread David Devereaux-Weber
Hank,

I finally succeeded in getting python and mailman to build and install.  
There were a series of issues.  I had an error in the path for the root 
user, and I had an error in PYTHONHOME for my user.  Since I was using 
the standard location for python, I removed PYTHONHOME, and I fixed the 
path for root (used for make install for python).

Thanks for your patience!

Dave

[EMAIL PROTECTED] wrote:
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] Virtual hosts

2007-04-09 Thread Mark Sapiro
Ira Goldstein wrote:

  Hi.  The list's host_name on the web page does reflect the desired
virtual host name.


Then this is an issue with the outgoing MTA. I can't tell you what you
need to do to fix it, but I can tell you that Mailman is already using
the host_name attribute as the domain in list email addresses.


I've tried the add_virtualhost as

add_virtualhost('dom2.ain', 'dom2.ain')

both with and without:

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

but did not see any difference in the system response.


If DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST are correct in Defaults.py,
then

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py would be redundant and make no difference, but

add_virtualhost('dom2.ain', 'dom2.ain')

is required in mm_cfg.py, but it only affects newly created lists
unless you run fix_url. See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.htp.


I've spent the weekend reading up on postfix, but can not see where
postfix is rewriting the header (I'm not saying that it isn't doing this,
just that with my limited knowledge, I don't see it).

I'm sorry, but I probably know less about Postfix than you. Perhaps
someone else on this list can help, but the best resource for this
issue is probably one dedicated to Postfix.

-- 
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] content filtering problem

2007-04-09 Thread Mark Sapiro
Rick Pasotto wrote:

Today I received a message that had been rejected by the content
filtering system and I'm not sure why. The sections of the message were:

 I  1 no description [text/plain, 7bit, us-ascii, 0.2K]
 I  2 Toastmaster Meeting for Tmrw[message/rfc822, 7bit, 26K]
 I  3   no description[multipa/related, 7bit, 24K]
 I  4 no description  [multipa/alternativ, 7bit, 3.7K]
 I  5   no description[text/plain, quoted, us-ascii, 0.5K]
 I  6   no description [text/html, quoted, us-ascii, 2.9K]
 I  7 NewCiscoLogo.jpg [image/jpeg, base64, 20K]

In the pass_mime_types I have:

multipart/mixed
multipart/alternative
text/plain

Was the message rejected because the text/plain was quoted?


No.

You have two problems.

What is the overall message type in the main message headers? I suspect
it was not multipart/mixed or multipart/alternative; possibly
multipart/related or some such which would cause all of its sub-parts
to be skipped because multipart/whatever is not accepted.

Further, even if the main message is multipart/mixed, you don't accept
the message/rfc822 part so the only thing left would be the initial
0.2K text/plain part.

You need to accept every multipart/ type that could possibly contain a
sub-part of interest. A better choice for pass_mime_types is

multipart
message/rfc822
text/plain

In your example above, this would pass all the multipart types
regardless of sub-type as well as the message/rfc822 part. This
doesn't mean the entire message will be passed. It just means that the
various sub-parts of those parts will be examined and the text/plain
parts accepted.

Even though the above seems very liberal, it ultimately only accepts
text/plain and elemental message/rfc822 parts, in this case only the
two text/plain parts.

-- 
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] Virtual hosts

2007-04-09 Thread Brad Knowles
At 5:08 PM -0700 4/9/07, Mark Sapiro wrote:

  Then this is an issue with the outgoing MTA. I can't tell you what you
  need to do to fix it, but I can tell you that Mailman is already using
  the host_name attribute as the domain in list email addresses.

Most likely the desired virtual host name is a CNAME alias for the 
real canonical name.  The RFCs require that all CNAME aliases be 
resolved into their true canonical names, before delivering the 
message.  The solution is to remove the CNAME records and have the 
desired virtual host name resolve directly to an IP address record 
(either an IPv4 A record, or an IPv6  record).

I believe that all this is documented in the FAQ.

I've spent the weekend reading up on postfix, but can not see where
postfix is rewriting the header (I'm not saying that it isn't doing this,
just that with my limited knowledge, I don't see it).

  I'm sorry, but I probably know less about Postfix than you. Perhaps
  someone else on this list can help, but the best resource for this
  issue is probably one dedicated to Postfix.

It's not just postfix.  Sendmail does this too.  As does Exim.  And 
all other MTAs that are operating correctly according to the RFCs on 
this subject.

-- 
Brad Knowles [EMAIL PROTECTED], Consultant  Author
LinkedIn Profile: http://tinyurl.com/y8kpxu
Slides from Invited Talks: http://tinyurl.com/tj6q4
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] Mailman web interface does not save changes

2007-04-09 Thread Brad Knowles
At 11:03 AM -0300 4/9/07, Fernando Barros wrote:

  I've search Mailman FAQ and find a related issue
  (http://www.python.org/cgi-bin/faqw-mm.py?req=all#4.45) which points
  that the access to the site via redirect is tossing away the POST
  changes. The workaround would be to capture the POST data from the
  original request, convert it to a GET and redirect to that.

  Can anybody show me how to configure that ?

You don't.  You eliminate the redirect instead.

See all the other FAQ entries and linked archive articles from the 
mailman-users list.

-- 
Brad Knowles [EMAIL PROTECTED], Consultant  Author
LinkedIn Profile: http://tinyurl.com/y8kpxu
Slides from Invited Talks: http://tinyurl.com/tj6q4
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] content filtering problem

2007-04-09 Thread Rick Pasotto
On Mon, Apr 09, 2007 at 05:24:13PM -0700, Mark Sapiro wrote:
 Rick Pasotto wrote:
 
 Today I received a message that had been rejected by the content
 filtering system and I'm not sure why. The sections of the message were:
 
  I  1 no description [text/plain, 7bit, us-ascii, 0.2K]
  I  2 Toastmaster Meeting for Tmrw[message/rfc822, 7bit, 26K]
  I  3   no description[multipa/related, 7bit, 24K]
  I  4 no description  [multipa/alternativ, 7bit, 3.7K]
  I  5   no description[text/plain, quoted, us-ascii, 0.5K]
  I  6   no description [text/html, quoted, us-ascii, 2.9K]
  I  7 NewCiscoLogo.jpg [image/jpeg, base64, 20K]
 
 In the pass_mime_types I have:
 
 multipart/mixed
 multipart/alternative
 text/plain
 
 Was the message rejected because the text/plain was quoted?
 
 No.
 
 You have two problems.
 
 What is the overall message type in the main message headers? I suspect
 it was not multipart/mixed or multipart/alternative; possibly
 multipart/related or some such which would cause all of its sub-parts
 to be skipped because multipart/whatever is not accepted.

I can see that I was insufficiently clear. What I posted above is the
sections of the reject message that Mailman sent me. The
'message/rfc822' appears to be Mailman's encapsulation of the original
message. From your explanation I see that the problem was that the
original message was 'multipart/related'.

 Further, even if the main message is multipart/mixed, you don't accept
 the message/rfc822 part so the only thing left would be the initial
 0.2K text/plain part.
 
 You need to accept every multipart/ type that could possibly contain a
 sub-part of interest. A better choice for pass_mime_types is
 
 multipart
 message/rfc822
 text/plain
 
 In your example above, this would pass all the multipart types
 regardless of sub-type as well as the message/rfc822 part. This
 doesn't mean the entire message will be passed. It just means that the
 various sub-parts of those parts will be examined and the text/plain
 parts accepted.
 
 Even though the above seems very liberal, it ultimately only accepts
 text/plain and elemental message/rfc822 parts, in this case only the
 two text/plain parts.

Excellent. This is what I want. Thanks.

-- 
Only one thing can conquer war - that attitude of mind which can see
 nothing in war but destruction and annihilation -- Ludwig von Mises
Rick Pasotto[EMAIL PROTECTED]http://www.niof.net
--
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=showamp;file=faq01.027.htp