Re: [Mailman-Users] moderator page behind nginx with SSL

[John Griessen]

On 06/24/2016 10:29 AM, Mark Sapiro wrote:

put

DEFAULT_URL_PATTERN = 'https://%s/mailman/'


That fixed it.

The nginx folks were quick to spot this also in just a few minutes.

Thanks,  John Griessen
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] moderator page behind nginx with SSL

[John Griessen]

On 06/21/2016 12:10 PM, Mark Sapiro wrote:

On 06/21/2016 10:01 AM, John Griessen wrote:

> I could not find any examples of people using mailman behind TLS cert so
> I disabled the redirecting to https and the moderator function works
> that way.
> Either way the general admin pages including membership work as expected.


See the reply at
<https://mail.python.org/pipermail/mailman-users/2016-June/080916.html>
which tells you exactly how to fix this.


I checked and my configuration had:
DEFAULT_URL_HOST   = 'cibolo.us'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_EMAIL_HOST = 'cibolo.us'
MTA='Postfix'

nginx was set to serve www.cibolo.us and cibolo.us by redirecting to  
https://cibolo.us

the subdirectories are set to be rewritten as in
https://www.nginx.com/resources/wiki/start/topics/recipes/mailman/


location /mailman
location /images/mailman
location /pipermail


After noting these settings, I reran

sudo /usr/sbin/withlist -l -r fix_url sandbox

then cleared the browser cache,
then browsed
https://cibolo.us/mailman/listinfo

where I see an overall lists list

I use those links to navigate to

https://cibolo.us/mailman/listinfo/sandbox
https://cibolo.us/mailman/admin/sandbox
https://cibolo.us/mailman/admindb/sandbox

and when I change action to take to discard
and click submit,

a security warning pops up saying info will not be encrypted,
I click continue,

The radio button for discard goes back to Defer, the state it was in before.

All other functions of the admin pages work normally except for this.

===
If I change nginx to not redirect, but serve http without TLS certs when asked,
the user interface for moderation works normally.


Is there some special rewrite needed for

https://cibolo.us/mailman/admindb/sandbox
?




--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] moderator page behind nginx with SSL

[John Griessen]

I could not find any examples of people using mailman behind TLS cert so
I disabled the redirecting to https and the moderator function works that way.
Either way the general admin pages including membership work as expected.

There must be a problem with the nginx rewrites used to handle

http://cibolo.us/mailman/admindb/mailman-list-name

as opposed to

http://cibolo.us/mailman/listinfo/mailman-list-name

I'll ask the nginx list about it, and probably stay with no https for mailman 
lists.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] moderator page behind nginx with SSL

[John Griessen]

On 06/18/2016 05:39 AM, Stephen J. Turnbull wrote:

 > The rest of mailman version 2.1.22
 > is working fine with SSL and some rewriting by nginx and yet
 > https://cibolo.us/mailman/admindb/open_electroporator  gives a message
 > "will be sent over an insecure connection" when I seta button to
 > discard and then do the submit all data button.

Do you have a proper certificate for the host, rooted in a well-known
service?  I suppose you do, but it's the first thing to check.


it is from letsencrypt.org

The

second is whether that root service is listed in your browser's list
of trusted roots.


It works fine for my webpages I set up such as
http://cibolo.us/mailman/listinfo/open_electroporator  that URl is rewritten 
and permenanetly directed to below:
https://cibolo.us/mailman/listinfo/open_electroporator



Third, is this actually SSL and not TLS?  SSL is in fact considered
insecure by many experts; many libraries implementing these protocols
now refuse to use SSL (even v3), and some issue a warning if the
server forces it.


I suppose it is TLS.  I followed very recent guides to set it up.

Yes, as far as behind nginx it is TLS:

 # SSL Settings

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;
ssl_session_cache   shared:SSL:10m;
ssl_session_timeout 10m;
ssl_certificate /etc/ssl/xxx;
ssl_certificate_key /etc/ssl/xx;
# Diffie-Hellman parameter for DHE ciphersuites, recommended 2048 bits
ssl_dhparam /etc/ssl/private/dhparam2048.pem;

Only admin of pending moderation is affected.
Maybe I have an operator error -- I'll check for setting the moderator name and 
password -- it may be blank or
from an older version of mailman  that this installation was migrated from...
fix_url has been run on the affected list.  That was after some restoring of 
data dirs and
there could be permissions problems...so maybe I still need to run fix_url 
again...

Thanks for the suggestions.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] moderator page behind nginx with SSL

[John Griessen]

The rest of mailman version 2.1.22
is working fine with SSL and some rewriting by nginx and yet
https://cibolo.us/mailman/admindb/open_electroporator  gives a message
"will be sent over an insecure connection" when I seta button to discard and 
then do
the submit all data button.

Is there a way to use SSL here?

Or... will I need to disable SSL for this page to get that submit to work?
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman postfix connection on debian

[John Griessen]

On 05/21/2016 06:28 PM, John Griessen wrote:

Try setting

VERP_CONFIRMATIONS = Yes

in mm_cfg.py. this will make the message have

Reply-To: catjuggling-confirm+<@cibolo.us
Subject: Your confirmation is required to join the catjuggling mailing list

That may help.


That works when I do a list mass subscription invite, reply via 
smtp.sendgrid.net,
otherwise sendgrid.net silently drops it, and I don't
even see it in bounce logs when logged into sendgrid.net.

So sendgrid.net is anti mailman.
Sendgrid.net is a consolidator like we are seeing so many of in web services 
vs. DIY internet
servers operated by people like us.  Could be bad for DIY internet.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman postfix connection on debian

[John Griessen]

On 05/20/2016 12:28 PM, Mark Sapiro wrote:

Could sendgrid ahve something to do with this?   Are they filtering my
>mails of a pattern that has been failing before?


Possibly.

Your confirmations are

Reply-To:catjuggling-requ...@cibolo.us
Subject: confirm 

There have been reports, e.g.,
<https://mail.python.org/pipermail/mailman-users/2016-May/080805.html>,
that this Subject: triggers spam filters.

Try setting

VERP_CONFIRMATIONS = Yes

in mm_cfg.py. this will make the message have

Reply-To: catjuggling-confirm+<@cibolo.us
Subject: Your confirmation is required to join the catjuggling mailing list

That may help.


I have not changed VERP_CONFIRMATIONS yet, but I enabled smtp sending via 
dovecot sasl authorization
and the mail was handled, delivered, and the list state updated to having that 
new member.

The new member was one of the virtual mailbox users on the same server with 
postfix, mailman, dovecot
so there was not much chance of catjuggling-request behaving differently than a 
catjuggling post.

I'll try VERP_CONFIRMATIONS = Yes and send via sendgrid again to test that.

Thanks,

John Griessen
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman postfix connection on debian

[John Griessen]

On 05/20/2016 05:11 AM, John Griessen wrote:


Any ideas what would cause catjuggling-request: to fail where
catjuggling: "|/var/lib/mailman/mail/mailman post catjuggling"
works?


Here is the log from starting a new invite to j...@griessen.com.  the mail 
arrives as usual
from catjuggling-requ...@cibolo.us, and says "just reply".

May 20 10:12:32 localhost dovecot: lmtp(3639): Disconnect from local: 
Successful quit
May 20 10:12:32 localhost postfix/qmgr[1066]: 067D2618FF: removed
May 20 10:12:32 localhost postfix/smtpd[3632]: disconnect from 
mail-lb0-f191.google.com[209.85.217.191]
May 20 10:13:05 localhost postfix/smtpd[3636]: connect from localhost[::1]
May 20 10:13:05 localhost postfix/smtpd[3636]: 11BCC618FF: client=localhost[::1]
May 20 10:13:05 localhost postfix/cleanup[3637]: 11BCC618FF: 
message-id=
May 20 10:13:05 localhost postfix/qmgr[1066]: 11BCC618FF: 
from=, size=1855, nrcpt=1 (queue active)
May 20 10:13:05 localhost dovecot: lmtp(3639): Connect from local
May 20 10:13:05 localhost postfix/smtpd[3636]: disconnect from localhost[::1]
May 20 10:13:05 localhost dovecot: lmtp(3639, j...@griessen.com): wnEeIg3jPlc3DgAA0J78UA: 
msgid=: saved mail to INBOX

May 20 10:13:05 localhost dovecot: lmtp(3639): Disconnect from local: 
Successful quit
May 20 10:13:05 localhost postfix/lmtp[3638]: 11BCC618FF: to=, relay=mail1[private/dovecot-lmtp], delay=0.02, 
delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 2.0.0  wnEeIg3jPlc3DgAA0J78UA Saved)

May 20 10:13:05 localhost postfix/qmgr[1066]: 11BCC618FF: removed

When I reply I see nothing in the log.

Soon after, I send another list mail from  an established subscriber and see it 
immediately

May 20 10:21:39 localhost postfix/qmgr[1066]: B787C61956: from=, 
size=1986, nrcpt=1 (queue active)

May 20 10:21:39 localhost dovecot: lmtp(3695): Connect from local
May 20 10:21:39 localhost dovecot: lmtp(3695, j...@cottagematic.com): aDfeMzPlPldvDgAA0J78UA: 
msgid=<573ee531.2050...@kitmatic.com>: saved mail to INBOX
May 20 10:21:39 localhost postfix/lmtp[3694]: B787C61956: to=, relay=mail1[private/dovecot-lmtp], 
delay=0.19, delays=0.17/0.01/0/0.01, dsn=2.0.0, status=sent (250 2.0.0  aDfeMzPlPldvDgAA0J78UA Saved)

May 20 10:21:39 localhost dovecot: lmtp(3695): Disconnect from local: 
Successful quit
May 20 10:21:39 localhost postfix/qmgr[1066]: B787C61956: removed


Could sendgrid ahve something to do with this?   Are they filtering my mails of 
a pattern that has been failing before?
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman postfix connection on debian

[John Griessen]

On 05/19/2016 10:20 PM, John Griessen wrote:

I am setting up 2.1 on debian and get no receive of a mail to the server that 
is not a virtual_mailbox_domain address in postfix.


More specifically, I am replying to the confirmation message ( to 
catjuggling-requ...@cibolo.us)  after inviting a user to the list.
It seems to not work -- no hint of it in the logs.

I can send a message to a different related address, and see in the logs -- ( 
to catjuggl...@cibolo.us)
(delivered to command: /var/lib/mailman/mail/mailman post catjuggling)
I can use the link to start a subscription via the web interface.

/etc/aliases has these lines:

# STANZA START: catjuggling
# CREATED: Thu May 19 23:07:53 2016
catjuggling: "|/var/lib/mailman/mail/mailman post catjuggling"
catjuggling-admin:   "|/var/lib/mailman/mail/mailman admin catjuggling"
catjuggling-bounces: "|/var/lib/mailman/mail/mailman bounces catjuggling"
catjuggling-confirm: "|/var/lib/mailman/mail/mailman confirm catjuggling"
catjuggling-join:"|/var/lib/mailman/mail/mailman join catjuggling"
catjuggling-leave:   "|/var/lib/mailman/mail/mailman leave catjuggling"
catjuggling-owner:   "|/var/lib/mailman/mail/mailman owner catjuggling"
catjuggling-request: "|/var/lib/mailman/mail/mailman request catjuggling"
catjuggling-subscribe:   "|/var/lib/mailman/mail/mailman subscribe catjuggling"
catjuggling-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe 
catjuggling"
# STANZA END: catjuggling

/etc/aliases has been updated with
sudo newaliases

Any ideas what would cause catjuggling-request: to fail where
catjuggling: "|/var/lib/mailman/mail/mailman post catjuggling"
works?
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] mailman postfix connection on debian

[John Griessen]

I am setting up 2.1 on debian and get no receive of a mail to the server that 
is not a virtual_mailbox_domain address in postfix.
For instance, a reply to a subscribe request doesn't get received or even 
mentioned much by the MTA logs in /var/log/mail.log,
but a email to a virtual address, not local to the server, goes fine.

There are so many uids and gids I can't figure it:

This is  ll /run/dovecot-->

srw--- 1 rootroot   0 May 20 02:26 anvil
srw--- 1 rootroot   0 May 20 02:26 anvil-auth-penalty
srw--- 1 dovecot root   0 May 20 02:26 auth-client
srw--- 1 dovecot root   0 May 20 02:26 auth-login
srw--- 1 rootroot   0 May 20 02:26 auth-master
-rw--- 1 rootroot  32 May 20 02:18 auth-token-secret.dat
srw--- 1 vmail   root   0 May 20 02:26 auth-userdb
srw--- 1 dovecot root   0 May 20 02:26 auth-worker
srw--- 1 rootroot   0 May 20 02:26 config
srw--- 1 rootroot   0 May 20 02:26 dict
srw--- 1 rootroot   0 May 20 02:26 director-admin
srw-rw-rw- 1 rootroot   0 May 20 02:26 dns-client
srw--- 1 rootroot   0 May 20 02:26 doveadm-server
lrwxrwxrwx 1 rootroot  25 May 20 02:26 dovecot.conf -> 
/etc/dovecot/dovecot.conf
drwxr-xr-x 2 rootroot  40 May 20 02:18 empty
srw-rw-rw- 1 rootroot   0 May 20 02:26 imap-urlauth
srw--- 1 dovecot root   0 May 20 02:26 imap-urlauth-worker
srw-rw-rw- 1 rootroot   0 May 20 02:26 indexer
srw--- 1 dovecot root   0 May 20 02:26 indexer-worker
srw--- 1 rootroot   0 May 20 02:26 ipc


 ll /run/mailman/

rw-rw 1 list list 4 May 20 02:18 mailman.pid


There's no telling what postfix is running as...


I tried a simplifying test and it seems not simple enough:

I wanted to send a test email, so I could see it in the logs:
I have a list called catjuggling for testing things out.  No users in it but 
me, no one to bother...

$ sudo echo "test email" | /var/lib/mailman/mail/mailman post catjuggling
Group mismatch error.  Mailman expected the mail
wrapper script to be executed as group "daemon", but
the system's mail server executed the mail script as
group "cibolo".  Try tweaking the mail server to run the
script as group "daemon", or re-run configure,
providing the command line option `--with-mail-gid=cibolo'.

If I su root I can send a message, and get a reponse from mailman that it is 
from no one, so needs approval,
so that tests that mailmanis intalled somewhat, and postfix is the hangup.

list and vmail are no login users, so can't test this that way...


$ postconf -n
-bash: postconf: command not found
cibolo@mail1:/etc/dovecot$ sudo postconf -n
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = all
mailbox_size_limit = 0
mydestination = cibolo.us, mail1.cibolo.us, localhost
mydomain = cibolo.us
myhostname = mail1
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
myorigin = $mydomain
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated 
defer_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = private/auth
smtpd_sasl_type = dovecot
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/xx
smtpd_tls_key_file = /etc/xxx
smtpd_tls_security_level = may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
virtual_alias_maps = hash:/etc/postfix/virtual_aliases
virtual_mailbox_domains = casaxx.com, casita.com, etc.com
virtual_mailbox_maps = hash:/etc/postfix/vmailboxes
virtual_transport = lmtp:unix:private/dovecot-lmtp

mm_cfg.py changes===
MTA='Postfix'
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'cibolo.us'
#-
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST   = 'mail1.cibolo.us'

Thanks,

John Griessen
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] digest mode links

[John Griessen]

Why do digest mode links rename a .jpg file?  A Mac OS X user can't see 
attachments.


URL: 

-- next part --
A non-text attachment was scrubbed...
Name: DSC04246.JPG
Type: application/octet-stream
Size: 153072 bytes
Desc: not available


Thanks,

John
--
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] digest attachments

[John Griessen]

One of my digest list members wishes they could see photo attachments in some
clicky way using links in the digest email, but all I've figured out
is to set archiving to on, and tell them to look there.  They won't
jump through that many hoops, and still whine occasionally...

Is there any way to have photo MIME attachments linked to in a digest email?

thanks,

John Griessen
--
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] mailman-postfix-mysql virtual bounces with unknownuser: "sandbox-request"

[John Griessen]

Mark Sapiro wrote:

John Griessen wrote:



#mailman setup related:
relay_domains =  lists.metalartists.org lists.cibolo.us


If this postfix is on the Mailman machine, these are not relay domains.
The addresses in these domains will be mapped to local addresses by
Mailman's virtual-mailman in virtual_alias_maps, but then you need
aliases to map those local addresses into pipes to the mailman
wrapper. This is the hash:/var/lib/mailman/data/aliases that's missing
from alias_maps


#relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
transport_maps = hash:/etc/postfix/transport
mailman_destination_recipient_limit = 1



This all looks like postfix_to_mailman.py stuff. "You must pick one or
the other, though neither of them are to be what they claim" B. Dylan



I took all that out and works fine.  Thanks for clearing confusion of 
postfix_to_mailman.py

I'm still not sure what enables it except for it being put in the dir:
/usr/lib/mailman/scripts/

Is that all?  If so, I've disabled it.

thanks,

John G
--
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] How to reduce memory use?

[John Griessen]

I've just started being the list server for a low volume list
that runs on a OpenVZ virtual server where memory is limited to 256MB RAM
and when you hit various barriers your programs can't allocate more memory.

Unless you upgrade to a more expensive OpenVZ virtual server...

Apache2 seems to be failing with the least grace -- just locking up sometimes,
but adding mailman was what got me so close to my memory limits.

Suggestions?

I'm already reducing apache2 memory use by directions like:
   StartServers  1
MinSpareServers   1
MaxSpareServers   2


Is there anything like those directives in mailman?

Thanks,

John Griessen
--
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] How to alias the listinfo page to lists.site.com?

[John Griessen]

I have a working installation with listinfo at

http://lists.metalartists.org/mailman/listinfo/

I'd like to see that page when I web browse to http://lists.metalartists.org

Is that easy?

John
--
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] mailman-postfix-mysql virtual bounces with unknown user: "sandbox-request"

[John Griessen]

sandbox-request is one of the mailman generated addressed for list 
sand...@lists.cibolo.us

I'm using debian with

postfix2.5.5-1.1
mailman1:2.1.12-3
mysql-server   5.1.40-1
mysql-client-5.1   5.1.40-1
apache2-mpm-worker 2.2.14-1
apache22.2.14-1

I've gotten the install to work up to the point of a new list member's conf 
email bouncing:
-
The mail system

 (expanded from
): unknown user: "sandbox-request"

Reporting-MTA: dns; mail.cibolo.us
-

Permission check showed no trouble.

I think it is a postfix config problem where I've added too much information.
If you can spot trouble in either of these config files, I'd appreciate it.

postfix main.cf
===
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
#hostname of the server without any subdomain parts.
mydomain = cibolo.us
#Try out this process_limit to reduce memory used on server
default_process_limit = 40
minimal_backoff_time = 2500

#number of SMTP sends to the same place at once
#SMTP process limit server wide is set at 9 in master.cf
default_destination_concurrency_limit = 4

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# DOS limiting by error behavior
smtpd_error_sleep_time = 2
smtpd_soft_error_limit = 3
smtpd_hard_error_limit = 8
# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
delay_warning_time = 20m

# jg's restrictions
smtpd_helo_required = yes
smtpd_client_restrictions =
smtpd_helo_restrictions =
smtpd_sender_restrictions =

smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_invalid_hostname,
reject_unauth_pipelining,
reject_non_fqdn_sender,
reject_unknown_sender_domain,
reject_non_fqdn_recipient,
reject_unknown_recipient_domain,
check_client_access cdb:/etc/postfix/access_client_ipaddr_checks,
check_helo_access cdb:/etc/postfix/access_helo_checks,
check_sender_access cdb:/etc/postfix/access_sender_checks,
#check_recipient_access hash:/etc/postfix/access_recipient_checks,
reject_rbl_client bl.spamcop.net,
reject_rbl_client zen.spamhaus.org
permit

myhostname = mail.cibolo.us
alias_maps = cdb:/etc/aliases
alias_database = cdb:/etc/aliases
myorigin = /etc/mailname
mydestination = localhost mail.cibolo.us localhost.cibolo.us
mynetworks = 76.191.252.85 127.0.0.0/8
relayhost =
mailbox_size_limit = 8000
recipient_delimiter = +
notify_classes = resource, software
#virtual mailbox method
virtual_mailbox_base = /var/mail/vhosts
virtual_minimum_uid = 1999
virtual_uid_maps = cdb:/etc/postfix/virtual_uid
virtual_gid_maps = cdb:/etc/postfix/virtual_gid

virtual_mailbox_limit = 5120

#virtual alias method
#virtual_mailbox_domains = polymerlogic.com industromatic.com
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf
#virtual_alias_maps = cdb:/etc/postfix/virtual
virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
   hash:/var/lib/mailman/data/virtual-mailman
#virtual_mailbox_maps = cdb:/etc/postfix/vmailbox
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf
virtual_transport = virtual
# Additional for quota support
#virtual_create_maildirsize = yes
#virtual_mailbox_extended = yes
#virtual_mailbox_limit_maps = 
mysql:/etc/postfix/mysql_virtual_mailbox_limit_maps.cf
#virtual_mailbox_limit_override = yes
#virtual_maildir_limit_message = Sorry, the user's maildir has overdrawn his 
diskspace quota, please try again later.
#virtual_overquota_bounce = yes

#If you want to use MySQL also to store your Backup MX domains add this
#relay_domains = mysql:/etc/postfix/mysql_relay_domains_maps.cf

#mailman setup related:
relay_domains =  lists.metalartists.org lists.cibolo.us
#relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
transport_maps = hash:/etc/postfix/transport
mailman_destination_recipient_limit = 1

=

mm_cfg.py
=
# -*- python -*-

# Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
# 02110-1301 USA


"""This is the module which takes your site-specific settings.

From a raw distribution it should be copied to 

[Mailman-Users] Recommended howto for using with postfix apache2 mysql virtual hosts

[John Griessen]

I find some howtos that are close to my situation using debian, but there are 
differences
from there to the comments in files like:

/etc/mailman/postfix-to-mailman.py
/etc/mailman/apache.conf



I'm using versions:

apache2-mpm-worker 2.2.14-1
apache2-utils  2.2.14-1
mailman1:2.1.12-3
postfix2.5.5-1.1
postfix-mysql  2.5.5-1.1
mysql-client-5.1   5.1.40-1
mysql-server-5.1   5.1.40-1

Any recommendations for installation on debian?

thanks,

John Griessen

--
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] Recommended howto for using with postfix apache2 mysql virtual hosts

[John Griessen]

I find some howtos that are close to my situation using debian, but there are 
differences
from there to the comments in files like:

/etc/mailman/postfix-to-mailman.py
/etc/mailman/apache.conf



I'm using versions:

apache2-mpm-worker 2.2.14-1
apache2-utils  2.2.14-1
mailman1:2.1.12-3
postfix2.5.5-1.1
postfix-mysql  2.5.5-1.1
mysql-client-5.1   5.1.40-1
mysql-server-5.1   5.1.40-1

Any recommendations for installation on debian?

thanks,

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