public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] ezmlm-like single command to subscribe an user?
Date: Fri, 28 Jan 2011 06:03:48 +0000	[thread overview]
Message-ID: <4D425C44.5050105@yahoo.com.au> (raw)
In-Reply-To: <4d39f5ea.47f3d80a.0fcc.fffff1c2@mx.google.com>

On 28/01/11 4:13 PM, Mads Martin Jørgensen wrote:
> On Fri, Jan 28, 2011 at 12:28 AM, Ben Schmidt
> <mail_ben_schmidt@yahoo.com.au>  wrote:
>>> Those risks simply do not exist if one forwards an empty email to
>>> some_list+subscribe-any.user=example.com@domain.tld , using the
>>> system's mail server.
>>
>> Some of the web interfaces bundled with Mlmmj make use of similar
>> workarounds already, too.
>
> Why all the commandline stuff? I still fail to see what the problem
> with sending an empty mail through the system mail server, where the
> envelope from is set to any.user@example.com.

I expect that's what the current mlmmj web interface does. All I was
referring to was the use of the mail system rather than the commandline
to avoid having to deal with permissions etc..

As far as I can tell, the only real benefit to the Ezmlm way rather than
the current Mlmmj way is that it leverages the support of existing Ezmlm
plugins for CMSes, as the OP mentioned.

Ben.



> mlmmj uses the envelope from to determine who sent the subscription
> request.



  parent reply	other threads:[~2011-01-28  6:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 21:08 [mlmmj] ezmlm-like single command to subscribe an user? Mark Alan
2011-01-27 10:32 ` Ben Schmidt
2011-01-27 17:14 ` Thomas Goirand
2011-01-27 17:22 ` Mads Martin Jørgensen
2011-01-28  5:13 ` Mads Martin Jørgensen
2011-01-28  6:03 ` Ben Schmidt [this message]
2011-01-28  8:59 ` Mark Alan

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=4D425C44.5050105@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --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