All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Ehnes <chris@filmkreis.tu-darmstadt.de>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Allowing specific addresses with subonlypost
Date: Thu, 12 Jan 2017 18:03:27 +0000	[thread overview]
Message-ID: <20170112190327.5f0c7b29@localhost> (raw)
In-Reply-To: <13b7eecf-62da-b77b-4685-ddae6cc0ee39@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

Hi,

yep, this thread is quite old, but in case someone needs this later
on...

On Fri, 23 Dec 2016 08:05:46 +1100
Ben Schmidt <mail_ben_schmidt@yahoo.com.au> wrote:

> 
> On 22/12/2016 11:51 pm, Morten Shearman Kirkegaard wrote:
> > On 2016-12-22, at 13:24:10 +0100, David Demelier wrote:
> >> However to stop spam I've enabled the subonlypost option to only
> >> allow subscribers to post mails. The problem is that I also would
> >> like to add specific addresses so my own mail server can also send
> >> mails to people subscribed.
> >
> > The easiest way of allowing that, is adding them in nomailsubs.d/.
> 
> This is absolutely right. But using 'send' in an access file should
> have worked, too. I might have to look into that.

It works, but only if the send statement is followed by an allow. For
me it looks therefore like this:

send ^Return-Path:.*@domain.tld
allow


Regards
Chris

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

      parent reply	other threads:[~2017-01-12 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 12:24 [mlmmj] Allowing specific addresses with subonlypost David Demelier
2016-12-22 12:51 ` Morten Shearman Kirkegaard
2016-12-22 13:16 ` David Demelier
2016-12-22 21:05 ` Ben Schmidt
2017-01-12 18:03 ` Christoph Ehnes [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=20170112190327.5f0c7b29@localhost \
    --to=chris@filmkreis.tu-darmstadt.de \
    --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.