Skip to contentSkip to conversation

ezmlm-like single command to subscribe an user?

mlmmj Mark Alan 4 participants 7 messages Jan 21, 2011 – Jan 28, 2011

lore
Share & tools
lore

Mark Alan

author
#0 lore raw

Hello list,

I am not being able to find info about the proper command to subscribe an user like ezmlm does:
[email protected]

Meaning: subscribe user [email protected] to list [email protected]

We would like to migrate from ezmlm to mlmmj, but keeping in place the Drupal ezmlm module <http://drupal.org/project/ezmlm> to let our users subscribe to our mailing lists.
Given an user email address that module changes the @ in the user's address into a = , then adds prefix 'listname+subscribe-' and then adds a trailing '@domain.tld', producing the canonical ezmlm/qmail format:
[email protected]

Regards,

M.

#1 lore raw
Quoted 8 lines · Mark Alan

Hello list,

I am not being able to find info about the proper command to subscribe an user like ezmlm does:
[email protected]

Meaning: subscribe user [email protected] to list [email protected]

I'm fairly new to Mlmmj myself, so I'm not sure about this...but...I don't think Mlmmj does this. Can somebody else confirm it?

I wouldn't mind adding this functionality, though it would probably not make it into the next release but only the one after.

Ben.

#2 lore raw
In reply to Mark Alan
Quoted 10 lines · Ben Schmidt
Quoted 8 lines · Mark Alan

Hello list,

I am not being able to find info about the proper command to subscribe an user like ezmlm does:
[email protected]

Meaning: subscribe user [email protected] to list [email protected]

Quoted 7 lines

I'm fairly new to Mlmmj myself, so I'm not sure about this...but...I don't think Mlmmj does this. Can somebody else confirm it?

I wouldn't mind adding this functionality, though it would probably not make it into the next release but only the one after.

Ben.

I see this as a way to get spams... Let's say somebody that doesn't like me sends 1000 messages to this address, then I might receive 1000 requests to register to the list.

I don't want this feature on my servers. Only the legitimate owner of [email protected] should be able to register, and the others should be filtered with something like DKIM or spf, or whatever you like that can provide a kind of auth. So if you want to add such a dangerous feature, make sure it's disabled by default.

Thomas

#3 lore raw
In reply to Mark Alan
Quoted 17 lines · Thomas Goirand
Quoted 4 lines
Quoted 4 lines

I am not being able to find info about the proper command to subscribe an user like ezmlm does:
[email protected]

Quoted 8 lines
Quoted 2 lines

Meaning: subscribe user [email protected] to list [email protected]

I'm fairly new to Mlmmj myself, so I'm not sure about this...but...I don't think Mlmmj does this. Can somebody else confirm it?

I wouldn't mind adding this functionality, though it would probably not make it into the next release but only the one after.

I see this as a way to get spams... Let's say somebody that doesn't like me sends 1000 messages to this address, then I might receive 1000 requests to register to the list.

Quoted 5 lines

I don't want this feature on my servers. Only the legitimate owner of [email protected] should be able to register, and the others should be filtered with something like DKIM or spf, or whatever you like that can provide a kind of auth. So if you want to add such a dangerous feature, make sure it's disabled by default.

And systems wanting to automate this can just send a mail with the envelope from being email in question. It's dead simple, actually. If you don't know what I mean, let me know and I'll explain.

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                 -- A. P. J.
#4 lore raw
In reply to Mark Alan
Quoted 6 lines · Ben Schmidt
Quoted 3 lines

Those risks simply do not exist if one forwards an empty email to [email protected] , 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 [email protected].

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

Signature · 4 lines
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
 and totally illogical, with just a little bit more effort?"
                                 -- A. P. J.
#5 lore raw
In reply to Mark Alan
Quoted 6 lines · Mads Martin Jørgensen
Quoted 4 lines · Ben Schmidt
Quoted 3 lines

Those risks simply do not exist if one forwards an empty email to [email protected] , using the system's mail server.

Quoted 6 lines
Quoted 2 lines

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 [email protected].

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.

Quoted 2 lines

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

author
#6 lore raw
In reply to Mark Alan
Quoted 6 lines · Mads Martin Jørgensen

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 [email protected].

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

Changing the envelope, that's what we need to do now in order to make it work. But that is fundamentally wrong. It is hardly good practice to let the system itself act as a spammer, i.e., faking 'From:' envelopes.

In the Drupal CMS code that I mentioned in the first post, at the file sites/all/modules/ezmlm/ezmlm.module,

we REPLACE the original:
// subscribe address for list formatted below
$to = trim($list_name) . '-subscribe-' . trim($user_name) .
'=' . trim($user_domain) . '@' . trim($list_domain);
$lang = language_default();
drupal_mail('ezmlm', 'subscribe', $to, $lang);

FOR this code:
// subscribe address for list formatted below
$to = trim($list_name) . '+subscribe' .'@' . trim($list_domain); $from = trim($user_name) . '@' . trim($user_domain); $lang = language_default();
drupal_mail('ezmlm', 'subscribe', $to, $lang, '', $from);

I am not talking of quick fixes "to just make it working for now", I am talking of fundamentally sound decisions involving best practices.

Why should we have to fake envelopes or, for that matter, have users that own a mailing list and at the same time need to members of the web server group and of the mail server group,
if we could have the much simpler and system/application agnostic:
[email protected]

Regards,

M.