From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] initial setup/exim sender verification
Date: Mon, 10 Mar 2014 03:50:23 +0000 [thread overview]
Message-ID: <4053985.5cUk1xF9hJ@trelane> (raw)
In-Reply-To: <87vbvn8hf0.fsf@zancas.localnet>
On Sunday, March 09, 2014 23:25:23 Chris Knadle wrote:
> On Sunday, March 09, 2014 23:50:46 David Bremner wrote:
> > Chris Knadle <Chris.Knadle@coredump.us> writes:
> > > And I'm assuming you have an "mlmmj-test" alias in /etc/aliases that
> > > looks
> > > like this?
> > >
> > > mlmmj-test: "|/usr/bin/mlmmj-recieve -L /var/spool/mlmmj/mlmmj-test/"
> >
> > It seems that the problem was that the listaddress was set to
> > point mlmmj-test@yantan.tethera.net and not
> > mlmmj-test@lists.tethera.net. Once I fixed that, the correct router is
> > invoked, without needing an alias in /etc/aliases (as far as I
> > understand, that's the point of defining the router).
>
> Oh. Yeah, you've probably set relay_domains = +mlmmj_domains. This means
> that Exim is accepting any mail to lists.tethera.net, /without/ checking the
> local_part of destination addresses. That's not exactly a good thing; it
> can cause backscatter. All one needs to do is send an email with the
> sending email address faked to nonexistent@lists.tethera.net, then the mail
> will be accepted based on the domain alone but then bounced back to the
> false sender.
Actually I think the above isn't true; Exim would normally accept the mail,
but due to the routing I believe MLMMJ ends up checking if the address matches
one of the addresses of its mailing lists, and the mail gets rejected
otherwise.
-- Chris
--
Chris Knadle
Chris.Knadle@coredump.us
prev parent reply other threads:[~2014-03-10 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 16:29 [mlmmj] initial setup/exim sender verification David Bremner
2014-03-09 19:21 ` Chris Knadle
2014-03-09 19:51 ` Chris Knadle
2014-03-10 2:50 ` David Bremner
2014-03-10 3:25 ` Chris Knadle
2014-03-10 3:50 ` Chris Knadle [this message]
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=4053985.5cUk1xF9hJ@trelane \
--to=chris.knadle@coredump.us \
--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.