From: G Stansfield <gstansfield@isat.co.za>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] testing mlmmj using Sendmail on a CentOS server
Date: Tue, 14 Oct 2014 12:26:39 +0000 [thread overview]
Message-ID: <543D167F.6060603@isat.co.za> (raw)
In-Reply-To: <54356DBC.9020609@vlsc.org>
On 08-Oct-14 7:00 PM, webmaster@vlsc.org wrote:
> I looked through the documentation, and installed mlmmj per the readme
> and install documents on a virtual CentOS server.
>
> I have created a test email list - sail2@vlsc.org - and added 2
> subscribers using mlmmj-sub. All appears to be setup properly, but when
> I send an email to the list using one of the subscribed addresses
> (webmaster@vlsc.org), my mail log file shows the following:
>
> Oct 7 23:14:21 cloud sendmail[1390]: s97NEL7Z001390: from=<webmaster@vlsc.org>, size\x1250, class=0, nrcpts=1, msgid=<54347310.8030905@vlsc.org>, proto=ESMTP, daemon=MSA, relay=c-24-22-61-28.hsd1.or.comcast.net [24.22.61.28]
>
> Oct 7 23:14:22 cloud sendmail[1390]: s97NEL7Z001390: Milter insert (1): header: DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vlsc.org; sÞfault;\n\tt\x1412723662; bh=SrfRFSC5LbQjGOAy8L6/MImtgtMNuon//Nkbtb0XVZI=;\n\thÚte:From:To:Subject;\n\tb=oKK6sefKYUbo7sC8oIAK0bnVA92vas8lkpOYQsVd//ru+cu5Eyg13wGRlZ+vyAUH2\n\t ko/f+ma6dQdizl1mVIq35h62m1tS+THd8LMZtadOFT1kiyG2HHyasmiqK1UuVjCbxO\n\t 6RfbPTriyZKsXnZfDK4y4pcoAqRextw+ZdKOrDU8>
> Oct 7 23:14:22 cloud opendkim[771]: s97NEL7Z001390: DKIM-Signature field added (sÞfault, d=vlsc.org)
>
> Oct 7 23:14:22 cloud sendmail[1392]: s97NEL7Z001390: to=/dev/null, ctladdr=<sail2@vlsc.org> (8/0), delay\0:00:01, xdelay\0:00:00, mailer=*file*, pri1824, dsn=2.0.0, stat=Sent
>
>
> The entry "to=/dev/null, ctladdr=<sail2@vlsc.org>" seems suspicious,
> like the email is being dumped to /dev/null instead of being delivered
> to the list.
>
> Can anyone help me by letting me know if I've missed some piece in my
> setup, or at least how to interpret this log entry correctly?
>
> I'm a refugee from majordomo who is trying to get our new server running
> with mlmmj so our organization can continue to run several small
> in-house email lists.
>
> Thanks for any help!
>
> Philip
Hi Philip!
Did you come right with this? If so, please tell me how!
I tried this some years ago in a home / test environment (using
OpenSUSE) before rolling out to a small production LAN - and failed
miserably! The only documentation I found was from mlmmj. Asked the
mlmmj list and still did not come right. Perhaps I was misunderstanding
something on the sendmail side of things.
I toyed with the idea of switching to postfix, but have some custom
rules in sendmail so did not want to take on a new learning curve for
what was essentially a functionality for which the users were not
clamouring at that time.
Regards,
Geoff
next prev parent reply other threads:[~2014-10-14 12:26 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 [this message]
2014-10-14 18:16 ` webmaster
2014-10-15 6:02 ` Ben Schmidt
2014-10-15 20:04 ` webmaster
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=543D167F.6060603@isat.co.za \
--to=gstansfield@isat.co.za \
--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.