All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Goirand <thomas@goirand.fr>
To: mlmmj@mlmmj.org
Subject: MLMMJ and qmail
Date: Wed, 11 Jan 2006 04:16:45 +0000	[thread overview]
Message-ID: <43C486AD.30501@goirand.fr> (raw)

Hi !

As said before, we got MLMMJ working with dtc (see 
http://www.gplhost.com/software-dtc.html). It now works perfectly with 
postfix, and I'm trying to make it work with qmail.

At my first tries, it seems there are serious right problems with the 
mlmmj binaries when running with qmail, and I still didn't make it work. 
Here is what I did, I hope somebody can help us to make it work 
automatically with DTC and qmail.

I don't use vpopmail. I think it's a stupid program that doesn't add 
anything to qmail. Qmail understand virtual domains out of the box, so 
vpopmail gives only an alternative auth, and there are plenty of 
alternative checkpassword available.

DTC doesn't use any system accounts, it uses all in nobody:nogroup 
because it's a mess if you use it for large web hosting and thousands of 
accounts you need to move from one server to another. Here is how it is 
setup:

/var/qmail/control:
xen010503.gplhost.com:xen010503-gplhost-com

/var/qmail/rcpthosts:
xen010503.gplhost.com

/var/qmail/users/assign:
+xen010503-gplhost-com-test:nobody:65534:65534:/var/www/sites/dtc/xen010503.gplhost.com/lists/xen010503.gplhost.com_test:::

/var/www/sites/dtc/xen010503.gplhost.com/lists/xen010503.gplhost.com_test/.qmail-default:
|preline /usr/bin/mlmmj-recieve -L 
/var/www/sites/dtc/xen010503.gplhost.com/lists/xen010503.gplhost.com_test

Just right after installing this setup, I had nothing working. When 
sending to test-subscribe@xen010503.gplhost.com qmail says it's 
delivered in the logs, but then it does nothing (it doesn't even try to 
send the confirmation message). After investigations, I've noticed that 
the procmail binary didn't had the same permissions as the mlmmj-recieve 
one. So I did "chown mail /usr/bin/mlmmj-recieve && chmod +s 
/usr/bin/mlmmj-recieve". After I did that, I had the following message 
in my qmail log:

Jan 11 03:43:38 xen010503 /usr/bin/mlmmj-recieve[3147]: 
mlmmj-recieve.c:130: could not create mail file in 
/var/spool/mlmmj/xen010503.gplhost.com_test/incoming directory: 
Permission denied

So I did chmod 777 on that folder, just to see if it works, then had the 
same problem with the queue folder, then did a chmod 777 on all the 
files of the list folder and the same chmod/chown on all the mlmmj 
binaries. The result is the same as at the begining: mlmmj doesn't send 
any confirmation request (and I think it doesn't send anything at 
all...). I believe there is still something wrong with the rights...

All I did is a unix rights mess, and I need to understand more deeply 
how all that works. Any help would be very appreciated.

Other topic: if one of you have it already setup, I'd like to have a 
look at the mlmmj web admin (please contact me in private if you can 
give me an access to it so I can have a quick look).

Best regards, and thanks all of you for you nice MLM,

    Thomas Goirand


             reply	other threads:[~2006-01-11  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  4:16 Thomas Goirand [this message]
2006-01-11 22:59 ` MLMMJ and qmail Morten K. Poulsen
2006-01-11 23:35 ` Morten K. Poulsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43C486AD.30501@goirand.fr \
    --to=thomas@goirand.fr \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.