Ben,

Thanks for the feedback!

I was able to use chown to change the ownership for all the list files as you suggested, and now I've moved several steps closer to getting mlmmj working!  (for anyone interested, uid = 8 on my server turned out to be user = "mail" )

mlmmj-receive is beginning to process posts sent to my test list, but so far they are ending up in

../listname/queue/discarded

and the maillog is reporting this as:
Oct 16 18:29:59 cloud sendmail[5502]: STARTTLS=server, relay=eapps-spx02.vm.eapps.com [69.89.2.76], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-SHA, bits=256/256
Oct 16 18:29:59 cloud sendmail[5502]: s9GITxnP005502: from=<philip@parshley.net>, size=6474, class=0, nrcpts=1, msgid=<54400DD3.3020404@parshley.net>, proto=ESMTP, daemon=MTA, relay=eapps-spx02.vm.eapps.com [69.89.2.76]
Oct 16 18:30:00 cloud sendmail[5504]: s9GITxnP005502: to="|mlmmj-receive -L /var/spool/mlmmj/sail2", ctladdr=<listname@mydomain.com> (8/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=36735, dsn=2.0.0, stat=Sent
Oct 16 18:30:00 cloud /etc/smrsh/mlmmj-process[5506]: mlmmj-process.c:811: Discarding /var/spool/mlmmj/listname/incoming/6386743745f1a098 due to missing envelope from address: Success

I understand the "due to missing envelope from address" error is a reference to an (empty) envelope from address, but I'm not sure why this is being triggered.  I've seen some references to this being a problem if the envelope from address is in < >  brackets, but its unclear to me how I can address this. Here's the header from the post file that ended up in ../discarded

From philip@parshley.net Thu Oct 16 18:29:59 2014

Received: from eapps-spx02.vm.eapps.com (eapps-spx02.vm.eapps.com [69.89.2.76])

    by cloud.mydomain.com (8.14.4/8.14.4) with ESMTP id s9GITxnP005502

    (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)

    for <listname@mydomain.com>; Thu, 16 Oct 2014 18:29:59 GMT

Received: from sagediagram.com ([216.154.217.29])

    by eapps-spx02.vm.eapps.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)

    (Exim 4.84)

    (envelope-from <philip@parshley.net>)

    id 1Xepnz-0006F6-M5

    for listname@mydomain.com; Thu, 16 Oct 2014 14:29:56 -0400

Received-SPF: softfail (sagediagram.com: domain of transitioning philip@parshley.net does not designate 24.22.61.28 as permitted sender) receiver=sagediagram.com; client-ip=24.22.61.28; helo=[192.168.1.104]; envelope-from=philip@parshley.net; x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with libspf2-1.0.0;

Received: from [192.168.1.104] (c-24-22-61-28.hsd1.or.comcast.net [24.22.61.28])

    by sagediagram.com (8.14.2/8.14.2) with ESMTP id s9GITgEh026480

    for <listname@mydomain.com>; Thu, 16 Oct 2014 14:29:42 -0400

Message-ID: <54400DD3.3020404@parshley.net>

Date: Thu, 16 Oct 2014 11:26:27 -0700

From: Philip <philip@parshley.net>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

MIME-Version: 1.0

To: listname@mydomain.com

Subject: re. test results

Content-Type: multipart/alternative;

 boundary="------------030407040502070403070707"

Received-SPF: pass (eapps-spx02.vm.eapps.com: domain of parshley.net designates 216.154.217.29 as permitted sender) client-ip=216.154.217.29; envelope-from=philip@parshley.net; helo=sagediagram.com;

X-SPF-Result: eapps-spx02.vm.eapps.com: domain of parshley.net designates 216.154.217.29 as permitted sender

X-Filter-ID: s0sct1PQhAABKnZB5plbIQgsumjrb/qn8pvMb0r31ZUkfdChetB4bt5LiDYVEZByx1wTMkEUUoeb

 KIhkyzl2dF32XZvZInsoHjme/WxkkRcTakFHLT/0qfWMlO3/QqSFNUDTyjn1ef5evEDDyypLgbJU

 gtOJAkXSMx9YVHdPqxKcv/HxuQ3Apsj8YeBnVa1ZUAt8TTxonK45J05twrVY/P1GDNZ9gBCIxxGx

 VFpn7AN/U/jsH4EXGgfUT7LIXyPec67TIvOBTd6L1MGTcnqLu/y5q0C++Lv/QUF02g1+DZxb5wxw

 q6a5JGTNj4jSCHVb8vzKnEie5ViFLOjCzG8IF5e2XAcAqWhPNQt97ku/DxR4FjctpFCe7sYB5/us

 QEK/UJK+F9HDeJw2f5+jo8HgFDRtF2Igz0UWV+HgG70TkVxp7cowWC4sdJbvT/6MXLfExH4YaDRm

 graL79jkgrbL24PAgTtUp75uqlx0KezvZHVB9dYBSu5jRStj6zksZS+oTOevt9oQNLQ4Wz40vjTd

 BGiH1Wgh6RAenBR+licROGZUa05SLII8ZnNgIPr9luPC4iXwjlL8lh+/xwVCxffWBA==

X-Report-Abuse-To: spam@eapps-spx01.vm.eapps.com

X-Filter-Fingerprint: IFrWXGses7OKB5S5G8/dJRn/7L7+nnclbWGk7OJ1jHJA3cTUQ1R++keuE7RDJ8Kg3RbMLUalw1oC

 mj99/u+PoqoVy8a3lsStJtAvpObFX0XnhRv/ZJ3kEy8bfiAr+Fb/UpndEJ0YoaLytXXo8BMTaX2p

 Mk7LBarWD9Fj4R3eIu6C5spubTEXAEkuBKN3yOZvUxf7JO+oAUByCkP7cAJnEooJtGZFyF6tI/I5

 CWVQH2sjWUvnt4XQmbZjx+Gtm4/p

Authentication-Results: vm.eapps.com; spf=pass smtp.mailfrom=philip@parshley.net

X-eAppsHosting-Class: ham

X-eAppsHosting-Evidence: Combined (0.20)

X-Recommended-Action: accept

This is a multi-part message in MIME format.

--------------030407040502070403070707

I can see

envelope-from <philip@parshley.net>

in the header, but not sure why this would trigger the discard action, and how to fix this... any ideas?

I greatly appreciate all the help you've been providing, and I feel like I'm nearly there, but it's still just out of reach...

Philip




On 10/15/2014 2:53 PM, Ben Schmidt wrote:
Oct 15 18:45:22 cloud smrsh: uid 8: attempt to use "mlmmj-receive -L /var/spool/mlmmj/listname" (stat failed)

Unfortunately, I'm now getting the following bounce-error message:

    ----- The following addresses had permanent fatal errors -----
"|mlmmj-receive -L /var/spool/mlmmj/listname"
     (reason: 1)
     (expanded from:<listname@mydomain.com>)

Have to invoke either as root or as the user owning listdir
554 5.3.0 unknown mailer error 1

The symlinks and the actual mlmmj-xxxx files are all chmod as 755, but
I'm not sure how or where to effect a permissions change to get
sendmail to "invoke" mlmmj-receive with the proper permissions.

As you can see, this is progress from where I was before... any ideas
on how I should address the permissions error coming from
mlmmj-receive?

This may do it (but obviously understand it; don't execute it blindly!).
8 is the UID/user indicated in the sendmail log.

sudo chown 8 /var/spool/mlmmj/listname

Make sure Mlmmj through smrsh can also get to that dir (do you need more
symlinks, e.g. because you're chrooted?).

Ben.







-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4040/8394 - Release Date: 10/15/14