From: "webmaster@vlsc.org" <webmaster@vlsc.org>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] testing mlmmj using Sendmail on a CentOS server
Date: Wed, 15 Oct 2014 20:04:53 +0000 [thread overview]
Message-ID: <543ED365.2050506@vlsc.org> (raw)
In-Reply-To: <54356DBC.9020609@vlsc.org>
[-- Attachment #1: Type: text/plain, Size: 4426 bytes --]
Hi Ben!
Thanks to your reply, I was able to make great headway in getting this
to work :)
I still have one error message I can't solve - but first, this is what I
did to move things along...
As I mentioned offline to Geof, I already figured out the Sendmail MTA
wasn't getting the mlmmj program call, as you suspected. I've made all
references to my domain and email list below generic, to make things
easier to read.
I tried your suggestion by replacing the aliases entry program-call for
mlmmj, with a simple "cat" command to determine if this was a Sendmail
issue, or mlmmj... turns out the "cat" command would not fire either.
Here's what I did to get Sendmail to successfully fire the basic "cat"
command:
- I added an entry to the /etc/mail/virtusertable file:
listname@mydomain.com listname.mydomain.com
- then I changed the entry in the /etc/aliases file:
from:
listname: "|cat > /tmp/mailtest.txt"
to:
listname.mydomain.com: "|cat > /tmp/mailtest.txt"
Presto! The "cat" command fired when I sent an email to
listname@mydomain.com.
(*NOTE: this differs from the README documentation on the mlmmj website;
which has the aliases entry displayed as "listname: xxxxxxxx" instead of
"listname.mydomain.com: xxxxxxx" - I'm not sure if this is Sendmail
specific, or if this may be important for other MTAs as well... )
So now I had Sendmail set correctly to potentially fire the mlmmj
program, so I tried this /etc/aliases entry:
listname.mydomain.com: "|/usr/local/bin/mlmmj-receive -L
/var/spool/mlmmj/listname"
It did get as far as trying to call mlmmj-receive, but it failed to
start mlmmj-receive:
Oct 15 18:45:22 cloud smrsh: uid 8: attempt to use "mlmmj-receive -L /var/spool/mlmmj/listname" (stat failed)
Oct 15 18:45:22 cloud sendmail[4560]: s9FIjLBe004558: to="|/etc/smrsh/mlmmj-receive -L /var/spool/mlmmj/listname", ctladdr=<listname@mydomain.com> (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=35725, dsn=5.0.0, stat=Service unavailable
Oct 15 18:45:22 cloud sendmail[4560]: s9FIjLBe004558: s9FIjMBe004560: DSN: Service unavailable
smrsh: "mlmmj-receive" not available for sendmail programs (stat failed)
554 5.0.0 Service unavailable
So here's what I did to get mlmmj-receive to fire through the restricted
shell utility smrsh:
- I created symlinks for the mlmmj-xxx executables in the /etc/smrsh
directory:
ln -s /usr/local/bin/mlmmj-xxxxx
Now mlmmj-receive executes when I send an email to listname@mydomain.com!
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>)
----- Transcript of session follows -----
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?
Philip
On 10/14/2014 11:02 PM, Ben Schmidt wrote:
> Hi, Philip,
>
> Yes, we are definitely still here! Development has slowed a bit
> recently, but not stopped, and the mailing list is small, but friendly;
> we help when we can.
>
> Looks like not many people know how to configure Sendmail. I toyed with
> it many years ago, and can remember nothing.
>
> Perhaps if you send some configuration snippets we will have a better
> chance helping.
>
> It seems to me like the mail is never even getting to Mlmmj, i.e. that
> it is a Sendmail issue, not an Mlmmj issue. Maybe the Sendmail mailing
> list would be a better source of help.
>
> Perhaps worth a try is putting some other program in place of Mlmmj,
> e.g. a script that just does cat > /tmp/mymail. Perhaps even temporarily
> replacing the mlmmj-receive binary with that script is smartest, as you
> are changing fewest things in the system, then. Then you can send an
> email to the list address and see if it ends up in /tmp/mymail. If so,
> it looks more like an Mlmmj-related issue. If not, get that working
> first, and then replace with Mlmmj and see if you have more luck.
>
> Let us know how you go!
>
> Ben.
>
[-- Attachment #2: Type: text/html, Size: 6983 bytes --]
next prev parent reply other threads:[~2014-10-15 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 17:00 [mlmmj] testing mlmmj using Sendmail on a CentOS server webmaster
2014-10-14 12:26 ` G Stansfield
2014-10-14 18:16 ` webmaster
2014-10-15 6:02 ` Ben Schmidt
2014-10-15 20:04 ` webmaster [this message]
2014-10-15 21:53 ` Ben Schmidt
2014-10-16 10:13 ` Ben Schmidt
2014-10-16 19:02 ` webmaster
2014-10-17 4:39 ` Ben Schmidt
2014-10-17 20:41 ` Ben Schmidt
2014-10-17 20:56 ` webmaster
2014-10-17 21:30 ` webmaster
2014-10-19 20:33 ` Ben Schmidt
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=543ED365.2050506@vlsc.org \
--to=webmaster@vlsc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox