Is Mailmanctl running?

FAQ 3.14 covers a lot of ground in this area. You might find it
helpful... if not, you might add to it after you fix your problem :-)

Jon Carnes

On Thu, 2003-12-25 at 21:48, Jamie Penman-Smithson wrote:
> Hey all,
> 
> I've got postfix{-tls,-mysql}, Mailman, and postfix-to-mailman 2.1 
> (http://www.gurulabs.com/files/postfix-to-mailman-2.1.py) setup on Debian Sid 
> (unstable):
> 
> lorien:~# dpkg -l postfix* | grep ^ii
> ii  postfix        2.0.16-4       A high-performance mail transport agent
> ii  postfix-ldap   2.0.16-4       LDAP map support for Postfix
> ii  postfix-mysql  2.0.16-4       MYSQL map support for Postfix
> ii  postfix-pcre   2.0.16-4       PCRE map support for Postfix
> ii  postfix-tls    2.0.16-4       TLS and SASL support for Postfix
> 
> lorien:~# dpkg -l mailman* | grep ^ii
> ii  mailman        2.1.3-2        Powerful, web-based mailing list manager
> 
> I've setup a list using the web interface, and it's been added successfully:
> 
> lorien:/var/lib/mailman/bin# ./list_lists
> 2 matching mailing lists found:
>         Mailman - [no description available]
>     sd-announce - Silverdream IS news
> lorien:/var/lib/mailman/bin# ./list_admins sd-announce
> List: sd-announce,      Owners: [EMAIL PROTECTED]
> 
> Postfix shows that the mail has been sent to postfix-to-mailman:
> 
> Dec 26 01:47:25 lorien amavis[2532]: (02532-02) Passed, <[EMAIL PROTECTED]> -> 
> <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]>, Hits: 0.048
> Dec 26 01:47:26 lorien postfix/smtp[2786]: 376707846: to=<[EMAIL PROTECTED]>, 
> relay=192.168.1.6[192.168.1.6], delay=101, status=sent (250 2.6.0 Ok, id=02532-02, 
> from MTA: 250 Ok: queued as 5175F7849)
> Dec 26 01:47:26 lorien amavis[2532]: (02532-02) ESMTP: NOTICE: client broke the 
> connection without a QUIT
> Dec 26 01:47:29 lorien postfix/pipe[2799]: 5175F7849: to=<[EMAIL PROTECTED]>, 
> relay=mailman, delay=6, status=sent (lists.silverdream.org)
> 
> Dec 26 02:33:39 lorien postfix/qmgr[2879]: E6558785E: from=<[EMAIL PROTECTED]>, 
> size=1374, nrcpt=1 (queue active)
> Dec 26 02:33:44 lorien amavis[2387]: (02387-05) Passed, <[EMAIL PROTECTED]> -> 
> <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]>, Hits: 0.051
> Dec 26 02:33:45 lorien postfix/pipe[3122]: E6558785E: to=<[EMAIL PROTECTED]>, 
> relay=mailman, delay=7, status=sent (lists.silverdream.org)
> Dec 26 02:33:45 lorien postfix/smtp[3119]: 9FB6C7849: to=<[EMAIL PROTECTED]>, 
> relay=192.168.1.6[192.168.1.6], delay=36, status=sent (250 2.6.0 Ok, id=02387-05, 
> from MTA: 250 Ok: queued as E6558785E)
> Dec 26 02:33:53 lorien cyrus/master[17529]: process 3108 exited, status 0
> 
> ...and all the mail is sitting in Mailman's queue:
> 
> From: Jamie Penman-Smithson <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> X-Mailer: PocoMail 3.03 (1740) - EVALUATION VERSION
> X-URL: http://www.pocomail.com/
> Date: Fri, 26 Dec 2003 02:33:10 GMT
> Message-ID: <[EMAIL PROTECTED]>
> Subject: subscribe
> 
> It appears the mail is getting delivered to postfix-to-mailman.py and then to 
> mailman, but after that nothing appears to happen. I've checked 
> /var/log/mailman/errors, and it's empty.
> 
> I did show-qfiles on the qfiles/virgin directory and it shows two outbound messages:
> 
> ====================> 
> /var/lib/mailman/qfiles/virgin/1072096291.5388401+f84a04ab843bf8cd7c1dca80b94fe25fc58b3b4f.pck
> MIME-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Subject: Your new mailing list: mailman
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Date: Mon, 22 Dec 2003 12:31:31 +0000
> Precedence: bulk
> 
> ====================> 
> /var/lib/mailman/qfiles/virgin/1072401079.214362+11df5743f51e4cdca44869ec30d1dfde28869388.pck
> MIME-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Subject: Your new mailing list: sd-announce
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Date: Fri, 26 Dec 2003 01:11:19 +0000
> Precedence: bulk
> 
> But none of it is ever getting back to postfix. I've checked my settings in 
> /etc/mailman/mm_cfg.py
> 
> # Use Postfix as the MTA
> MTA = 'Postfix'
>  
> # How to deliver mail
> DELIVERY_MODULE = 'SMTPDirect'
> 
> # Deliver to mailhost on port 25
> SMTPHOST = 'lorien.silverdream.hq'
> SMTPPORT = 25                                      # default from smtplib
> 
> I double-checked that my DNS was still okay (just to rule it out):
> lorien:/var/lib/mailman/bin# host lorien.silverdream.hq
> lorien.silverdream.hq has address 192.168.1.6
> 
> In case it was a permissions problem I ran check_perms:
> 
> lorien:/var/lib/mailman/bin# ./check_perms
> /var/lib/mailman/data/aliases.db owned by www-data (must be owned by list
> 
> Problems found: 1
> Re-run as list (or root) with -f flag to fix
> 
> AFAIK this shouldn't stop mail from being delivered?
>  
> Can anyone offer any suggestions? Help would be appreciated - I'm running out of 
> ideas(!)
> 
> Thanks in advance
> 
> Happy Holidays,
> 
> Jamie
> 
> ---
> -jamie <[EMAIL PROTECTED]>
> w: http://silverdream.org | p: [EMAIL PROTECTED]
> Support The Blue Ribbon Campaign - http://eff.org/brl
> 
> 
> ------------------------------------------------------
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com


------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to