Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

2011-01-03 Thread Jim Wright
On Jan 3, 2011, at 1:34 PM, Mark Sapiro wrote:

> In order for aliases to be consulted, delivery must be 'local' not
> 'virtual'
> 
> The solution in your case is to put
> hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to
> mydestination and put
> 
> VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'
> 
> in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman
> mappings like
> 
> t...@wrightthisway.com  t...@localhost

Hi, Mark.  I appreciate the suggestions, but I was hesitant to reconfigure my 
postfix that way, for fear of borking my working virtual domains.  I should 
have mentioned earlier that I have my site configured using postfix admin, and 
after seeing your mention of changing the delivery, that got me thinking about 
the problem in more depth.

I did some new googling using postfixadmin and mailman, and came across this 
page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just 
needed to track down the most recent postfix-to-mailman.py script, make the 
required edits for my site, and I have now successfully created and sent email 
to my test list.

Thanks!

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


Re: [Mailman-Users] A basic filtering MIME question

2011-01-03 Thread yahoo

On 1/3/11 10:34 PM, Mark Sapiro wrote:



Maybe it's 2.1.13? Or maybe it's 2.1.9 which is the RedHat el5 RPM version.



My bad; that it is...


I'll add a comment. FAQ 1.8 is confusing because it does not make it
clear what comments relate to 2.0, and what to 2.1.

Further, it's discussing both HTML&  MIME issues.


Agreed.





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


Re: [Mailman-Users] A basic filtering MIME question

2011-01-03 Thread Mark Sapiro
On 1/3/2011 6:28 PM, yahoo wrote:
> On 1/3/11 2:06 PM, Mark Sapiro wrote:

>> filter_content - Yes
>> filter_mime_types - empty
>> pass_mime_types -
>>multipart
>>message/rfc822 (allows plain text and converted HTML from attached
>>messages. Remove to filter attached messages)
>>text/plain
>>text/html
>> filter_filename_extensions -
>>exe bat cmd com pif scr vbs cpl
>>(these are defaults - this setting doesn't exist in 2.1.3)
>> pass_filename_extensions - empty; default; this setting doesn't exist
>>in 2.1.3)
>> collapse_alternatives - Yes (this setting doesn't exist in 2.1.3)
>> convert_html_to_plaintext - Yes
> 
> Err, I see all those in our 2.1.3...


Then it's not 2.1.3 because the *_filename_extensions settings didn't
appear until 2.1.6 and collapse_alternatives first appeared in 2.1.7.

Maybe it's 2.1.13? Or maybe it's 2.1.9 which is the RedHat el5 RPM version.

> I'll add a comment. FAQ 1.8 is confusing because it does not make it
> clear what comments relate to 2.0, and what to 2.1.
> 
> Further, it's discussing both HTML & MIME issues.


Agreed.

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


Re: [Mailman-Users] A basic filtering MIME question

2011-01-03 Thread yahoo

On 1/3/11 2:06 PM, Mark Sapiro wrote:





I've been reading the FAQ's etc and asking local advice; but I must be
doing something stoopid.

MM2.1.3 under Linux, 2.6.18-164.el5



2.1.3? This is quite old. Current is 2.1.14.


I'll ask the local maintainer to upgrade. Ooops, he says there's no RPM we 
can use {until we fix something else, I assume.}



My goal is:

a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers
&  archives.

b) /dev/null the attachments, both in delivery and archives.




filter_content - Yes
filter_mime_types - empty
pass_mime_types -
   multipart
   message/rfc822 (allows plain text and converted HTML from attached
   messages. Remove to filter attached messages)
   text/plain
   text/html
filter_filename_extensions -
   exe bat cmd com pif scr vbs cpl
   (these are defaults - this setting doesn't exist in 2.1.3)
pass_filename_extensions - empty; default; this setting doesn't exist
   in 2.1.3)
collapse_alternatives - Yes (this setting doesn't exist in 2.1.3)
convert_html_to_plaintext - Yes


Err, I see all those in our 2.1.3...


(I've been helped by Brad who has pointed out some issues I need to better 
understand.)


Thank you.



I'll add a comment. FAQ 1.8 is confusing because it does not make it clear 
what comments relate to 2.0, and what to 2.1.


Further, it's discussing both HTML & MIME issues.





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


Re: [Mailman-Users] Pruning archived messages

2011-01-03 Thread Rick Morrison
On Thu, Dec 9, 2010 at 11:53 PM, Mark Sapiro  wrote:

> Rick Morrison wrote:
>
> >I've been asked to restrict our group's Mailman list to showing only the
> >last six months of archives. Is there any way to remove archived messages
> >older than a certain date and reflect that removal in the archive header's
> >"index.html" file?
>
>
> Edit the archives/private/listname.mbox/listname.mbox file to remove
> all the older messages. If you don't care about keeping the older
> messages at all, just edit the file in place and then run Mailman's
>
> bin/arch --wipe listname
>

Thanks to both repliers - this worked well. I ended up using "archivemail" (
http://archivemail.sourceforge.net/manpage.html) for the mbox handling and
running the whole thing from a cron-launched Python script.
--
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


Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

2011-01-03 Thread Mark Sapiro
Jim Wright wrote:

>However, I cannot send email to this list without the mail being rejected back 
>as being to an unknown user.
>
>Based on all of my reading, I think I've done everything correctly.  From my 
>Postfix log, it doesn't appear that the aliases file is being consulted at 
>all, but I am seeing a line indicating that the virtual-mailman file was 
>referenced.


That is correct. Aliases are not consulted because the virtual mapping
in virtual-mailman is

t...@wrightthisway.com  test


This maps 't...@wrightthisway.com' to 'test'. The unqualified address
'test' is assumed by Postfix to be qualified with $myorigin, which
defaults to $myhostname which is 'wrightthisway.com' which is a
virtual domain. Aliases only apply to local domains, i.e., those in
$mydestination.

[...]
>sh-3.2# postconf -n
>address_verify_sender = <>
>alias_database = hash:/etc/postfix/aliases, 
>hash:/usr/local/mailman/data/aliases


The above should be in alias_maps, not alias_database. Fixing this may
solve your problem, but it I suspect it will not be sufficient.


>alias_maps = hash:/etc/postfix/aliases
[...]
>mydestination = 


At a minimum, mydestination should include localhost.


>mydomain = wrightthisway.com
>myhostname = wrightthisway.com
[...]
>virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf, 
>hash:/usr/local/mailman/data/virtual-mailman
[...]
>Jan  2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: 
>to=, relay=virtual, delay=0.1, 
>delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: 
>"t...@wrightthisway.com")


In order for aliases to be consulted, delivery must be 'local' not
'virtual'

The solution in your case is to put
hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to
mydestination and put

VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'

in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman
mappings like

t...@wrightthisway.com  t...@localhost

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


Re: [Mailman-Users] A basic filtering MIME question

2011-01-03 Thread Mark Sapiro
yahoo  wrote:

>I've been reading the FAQ's etc and asking local advice; but I must be
>doing something stoopid.
>
>MM2.1.3 under Linux, 2.6.18-164.el5


2.1.3? This is quite old. Current is 2.1.14.


>My goal is:
>
>a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers 
>& archives.
>
>b) /dev/null the attachments, both in delivery and archives.



filter_content - Yes
filter_mime_types - empty
pass_mime_types -
  multipart
  message/rfc822 (allows plain text and converted HTML from attached
  messages. Remove to filter attached messages)
  text/plain
  text/html
filter_filename_extensions -
  exe bat cmd com pif scr vbs cpl
  (these are defaults - this setting doesn't exist in 2.1.3)
pass_filename_extensions - empty; default; this setting doesn't exist
  in 2.1.3)
collapse_alternatives - Yes (this setting doesn't exist in 2.1.3)
convert_html_to_plaintext - Yes

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


Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

2011-01-03 Thread Jim Wright
On Jan 3, 2011, at 12:15 AM, Jim Wright wrote:

> Jan  2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: 
> to=, relay=virtual, delay=0.1, 
> delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: 
> "t...@wrightthisway.com")

Hi, just a followup to my previous message, I have confirmed that the 'test' 
mailing list I created seems to be listed correctly in the virtual-mailman db, 
using the following command:

sh-3.2# postmap -q t...@wrightthisway.com 
hash:/usr/local/mailman/data/virtual-mailman
test

sh-3.2# postmap -s hash:/usr/local/mailman/data/virtual-mailman
test-conf...@wrightthisway.com  test-confirm
test-j...@wrightthisway.com test-join
test-subscr...@wrightthisway.comtest-subscribe
mailman-l...@wrightthisway.com  mailman-loop
t...@wrightthisway.com  test
test-ad...@wrightthisway.comtest-admin
test-boun...@wrightthisway.com  test-bounces
test-le...@wrightthisway.comtest-leave
test-ow...@wrightthisway.comtest-owner
test-requ...@wrightthisway.com  test-request
test-unsubscr...@wrightthisway.com  test-unsubscribe

--
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 Postfix/virtual setup, unknown user

2011-01-03 Thread Jim Wright
Hi, all.  I'm a new user, but I've searched the archives and so far haven't 
been able to find a fix for my issue.  I've set up mailman with postfix and I'm 
using virtual domains.  I've created a test mailing list, and Mailman has 
successfully emailed me that the list was created.  However, I cannot send 
email to this list without the mail being rejected back as being to an unknown 
user.

Based on all of my reading, I think I've done everything correctly.  From my 
Postfix log, it doesn't appear that the aliases file is being consulted at all, 
but I am seeing a line indicating that the virtual-mailman file was referenced.


Here are the relevant Mailman files:

>From mm_cfg.py:

# Put YOUR site-specific settings below this line.
MTA = "Postfix"
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['wrightthisway.com', 'themailshack.com']
add_virtualhost('wrightthisway.com', 'wrightthisway.com')
add_virtualhost('themailshack.com', 'themailshack.com')


sh-3.2# cat aliases
# This file is generated by Mailman, and is kept in sync with the
# binary hash file aliases.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE
# unless you know what you're doing, and can keep the two files properly
# in sync.  If you screw it up, you're on your own.

# The ultimate loop stopper address
mailman-loop: /usr/local/mailman/data/owner-bounces.mbox

# STANZA START: test
# CREATED: Sat Dec 25 18:26:51 2010
test: "|/usr/local/mailman/mail/mailman post test"
test-admin:   "|/usr/local/mailman/mail/mailman admin test"
test-bounces: "|/usr/local/mailman/mail/mailman bounces test"
test-confirm: "|/usr/local/mailman/mail/mailman confirm test"
test-join:"|/usr/local/mailman/mail/mailman join test"
test-leave:   "|/usr/local/mailman/mail/mailman leave test"
test-owner:   "|/usr/local/mailman/mail/mailman owner test"
test-request: "|/usr/local/mailman/mail/mailman request test"
test-subscribe:   "|/usr/local/mailman/mail/mailman subscribe test"
test-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe test"
# STANZA END: test

# STANZA START: mailman
# CREATED: Sun Jan  2 22:08:00 2011
mailman: "|/usr/local/mailman/mail/mailman post mailman"
mailman-admin:   "|/usr/local/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman"
mailman-join:"|/usr/local/mailman/mail/mailman join mailman"
mailman-leave:   "|/usr/local/mailman/mail/mailman leave mailman"
mailman-owner:   "|/usr/local/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/local/mailman/mail/mailman request mailman"
mailman-subscribe:   "|/usr/local/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman


sh-3.2# cat virtual-mailman
# This file is generated by Mailman, and is kept in sync with the binary hash
# file virtual-mailman.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you
# know what you're doing, and can keep the two files properly in sync.  If you
# screw it up, you're on your own.
#
# Note that you should already have this virtual domain set up properly in
# your Postfix installation.  See README.POSTFIX for details.

# LOOP ADDRESSES START
mailman-l...@wrightthisway.com  mailman-loop
# LOOP ADDRESSES END

# STANZA START: test
# CREATED: Sat Dec 25 18:26:51 2010
t...@wrightthisway.com  test
test-ad...@wrightthisway.comtest-admin
test-boun...@wrightthisway.com  test-bounces
test-conf...@wrightthisway.com  test-confirm
test-j...@wrightthisway.com test-join
test-le...@wrightthisway.comtest-leave
test-ow...@wrightthisway.comtest-owner
test-requ...@wrightthisway.com  test-request
test-subscr...@wrightthisway.comtest-subscribe
test-unsubscr...@wrightthisway.com  test-unsubscribe
# STANZA END: test


Below is my Postfix config, and a sample of the log when a message is sent to 
the list.  

sh-3.2# postconf -n
address_verify_sender = <>
alias_database = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases
alias_maps = hash:/etc/postfix/aliases
body_checks = regexp:/etc/postfix/maps/body_checks
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debug_peer_list = 70.116.91.238
default_process_limit = 20
default_rbl_reply = $rbl_code Service unavailable; $rbl_class [$rbl_what] 
blocked using $rbl_domain${rbl_reason?; $rbl_reason} - see http://$rbl_domain 
for additional info. If this was actually a legitimate email to a real user, 
please forward this message to postmas...@wrightthisway.com for assistance.
disable_vrfy_command = yes
header_checks = regexp:/etc/postfix/maps/header_checks
html_directory = no
inet_interfaces = all
mail_owner = _postfix
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
max_use = 18
me

[Mailman-Users] A basic filtering MIME question

2011-01-03 Thread yahoo

I've been reading the FAQ's etc and asking local advice; but I must be
doing something stoopid.

MM2.1.3 under Linux, 2.6.18-164.el5

My goal is:

a) Accept text/MIME/HTML message bodies, but deliver as text to subscribers 
& archives.


b) /dev/null the attachments, both in delivery and archives.

FAQ 1.8 says:


In Mailman 2.1, on the admin page, go to the Content Filtering section.
Change "Should Mailman filter ..." to Yes. If you leave the rest at
default values, including Yes for "Should Mailman convert text/html
parts to plain text?", your list will only distribute plain text
messages with no attachments.



And I did so, but I suspect that filter_mime_types &/or pass mime type 
originally had values that before/in my muddling, have been lost; both are 
empty now.


Suggestions?




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