feature requests
I am seeing your new mailing list manager and I am all excited because I like ezmlm, want something not as bloated as mailman, and given that mlmmj is still young, I hope I can contribute to get important features in.
One such feature is the ability to add and remove mailing lists without the need to edit /etc/aliases. The best way to do this would be to provide transport/directors that take messages at stdin and handle them accordingly. Then I could set, e.g. postfix to have lists.my.domain use the mlmmj transport, which would be this script.
The next feature that I think is paramount is the ability to add aliases to an account, like majordomo2. With subscriber-only lists, it is a pain to be restricted to a single address for posting. mailman "solves" this by allowing subscriptions to be NOMAIL. this is also painful. majordomo2 is nice. you subscribe, then register a bunch of aliases with your address, which can also post.
The last feature was sent to Mads privately. Here is is for completeness. Not sure whether this can be done, or should rather be done in a separate programme. But I think it's a cool idea (it's mine...) ;^>
Here it is:
Quoted 6 lines
Also, please make sure you implement a nice moderation interface as it's the only thing that mailman is lacking, really. i suggest an IMAP server with subfolders for accept, reject, discard. then you simply move messages in the queue accordingly. Only remaining
problem: locking for multiple moderators, and the possibility to undo, or to do batched commits.
For your information, I am a mailing list administrator with quite some experience in majordomo, ezmlm, and mailman, even with sympa... I use mailman and I hate it. All the others are worse though. ezmlm mainly because of its licence.
I am particularly looking for a special mailing list manager to handle:
http://marc.theaimsgroup.com/?l=mailman-users&m=109508403307185&w=2
Maybe mlmmj can be made flexible enough from the start to be able to support this.
Cheers,
Signature · 8 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] the only difference between a car salesman and a computer salesman is that the car salesman knows he's lying.
Quoted 6 lines · martin f krafft
The next feature that I think is paramount is the ability to add aliases to an account, like majordomo2. With subscriber-only lists, it is a pain to be restricted to a single address for posting. mailman "solves" this by allowing subscriptions to be NOMAIL. this is also painful. majordomo2 is nice. you subscribe, then register a bunch of aliases with your address, which can also post.
High on the TODO is the ability when posting to a subscribers only posting list to get a reply whether one wants to be able to post from this address in the future. A simple reply to that mail will subscribe the address to the nomail list which is already implemented, just not released yet.
This way one can have one address subscribed getting the mail, and a bunch of addresses subscribed without getting any mail.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2133 +0200]:
Quoted 5 lines
High on the TODO is the ability when posting to a subscribers only posting list to get a reply whether one wants to be able to post from this address in the future. A simple reply to that mail will subscribe the address to the nomail list which is already implemented, just not released yet.
Yeah, that would be nice.
However, please take care with automatic replies and the like. Challenge Response systems (of which this is one) are very painful if not done right; and I know not aof a single one done right.
http://kmself.home.netcom.com/Rants/challenge-response.html
Quoted 2 lines
This way one can have one address subscribed getting the mail, and a bunch of addresses subscribed without getting any mail.
Please allow for manual setting of such aliases as well. The nice thing about majordomo2's approach is that the addresses lose their right to post when someone unsubscribes. I don't think you can do that with the challenge system.
Signature · 8 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] gentoo: for when you finally find out that overclocking can kill your processor.
Quoted 6 lines · martin f krafft
Quoted 5 lines
High on the TODO is the ability when posting to a subscribers only posting list to get a reply whether one wants to be able to post from this address in the future. A simple reply to that mail will subscribe the address to the nomail list which is already implemented, just not released yet.
Quoted 7 lines
Yeah, that would be nice.
However, please take care with automatic replies and the like. Challenge Response systems (of which this is one) are very painful if not done right; and I know not aof a single one done right.
We send mails to the envelope from (Return-Path:) for confirmation of subscription. I'm sure you want that?
Quoted 7 lines
Quoted 2 lines
This way one can have one address subscribed getting the mail, and a bunch of addresses subscribed without getting any mail.
Please allow for manual setting of such aliases as well. The nice thing about majordomo2's approach is that the addresses lose their right to post when someone unsubscribes. I don't think you can do that with the challenge system.
With mlmmj there's a seperate 'version' of the list, just like the way digests are done in ezmlm.
If you send a mail to [email protected] you subscribe to the list without getting any email from it ever. Handy if you read your lists via the web, or through a news gateway.
So what could be done simply treat postings to a subscribers only list from emails not subscribed, as if they were trying to subscribe to the nomail version of it.
This way they only need one reply, and they are allowed to post from this address.
To do it right, the mail that was originally sent, will of course be posted to the list, if the person subscribes to the nomail version--a little bit like moderation.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2204 +0200]:
Quoted 2 lines
We send mails to the envelope from (Return-Path:) for confirmation of subscription. I'm sure you want that?
it does not matter. Automatic replies are evil. Moreover, too many legitimate users have invalid Return-Paths. But it is a far better means than using the From header. I am just saying: do not rely on the challenges only.
Quoted 10 lines
So what could be done simply treat postings to a subscribers only list from emails not subscribed, as if they were trying to subscribe to the nomail version of it.
This way they only need one reply, and they are allowed to post from this address.
To do it right, the mail that was originally sent, will of course be posted to the list, if the person subscribes to the nomail version--a little bit like moderation.
Wait, you said it would automatically subscribe them? I also think that's a bad idea. If I get a confirmation request when I did not consciously subscribe anywhere, I will delete it.
Whatever you do, please allow majordomo2-style aliases. You can do challenges on top. Power-users will want to set aliases. In fact, I have scripts to set it all up for me.
That said, I subscribed to the mailing list and have not received a confirmation yet. Nor am I getting mail. What could be wrong? The address I used was [email protected]
You are using cryptographic confirmations for subscriptions, right?
Thanks,
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] "one should never trust a woman who tells her real age. if she tells that, she will tell anything." -- oscar wilde
[ forgot to Cc: list, so resend ]
Quoted 8 lines · martin f krafft
also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2204 +0200]:
Quoted 2 lines
We send mails to the envelope from (Return-Path:) for confirmation of subscription. I'm sure you want that?
it does not matter. Automatic replies are evil. Moreover, too many legitimate users have invalid Return-Paths. But it is a far better means than using the From header. I am just saying: do not rely on the challenges only.
I'm not going to subscribe people without them confirming.
Quoted 7 lines
Quoted 7 lines
So what could be done simply treat postings to a subscribers only list from emails not subscribed, as if they were trying to subscribe to the nomail version of it.
This way they only need one reply, and they are allowed to post from this address.
Quoted 7 lines
Quoted 3 lines
To do it right, the mail that was originally sent, will of course be posted to the list, if the person subscribes to the nomail version--a little bit like moderation.
Wait, you said it would automatically subscribe them? I also think that's a bad idea. If I get a confirmation request when I did not consciously subscribe anywhere, I will delete it.
Sure, so delete it. But IF you want to be able to post from this address you can reply to it, and be able to.
Quoted 3 lines
Whatever you do, please allow majordomo2-style aliases. You can do challenges on top. Power-users will want to set aliases. In fact. I have scripts to set it all up for me.
What does majordomo2 style aliases look like?
Quoted 3 lines
That said, I subscribed to the mailing list and have not received a confirmation yet. Nor am I getting mail. What could be wrong? The address I used was [email protected]
There was no mail from mass.madduck.net delivered to the mmj.dk MX, are you sure you sent it to the right address? You can subscribe such an email just fine.
Quoted 1 line
You are using cryptographic confirmations for subscriptions, right?
No.
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.Quoted 7 lines · Mads Martin Joergensen
Quoted 3 lines
That said, I subscribed to the mailing list and have not received a confirmation yet. Nor am I getting mail. What could be wrong? The address I used was [email protected]
There was no mail from mass.madduck.net delivered to the mmj.dk MX, are you sure you sent it to the right address? You can subscribe such an email just fine.
Correction; it was recieved, but no To: header was present, so it was discarded.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2228 +0200]:
Quoted 2 lines
Correction; it was recieved, but no To: header was present, so it was discarded.
Is that necessary? I always use /usr/sbin/sendmail for mailing list subscriptions. The To header is completely useless anyway, isn't it? Why require it?
Anyway, I resent the subscription request.
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] during the voyage of life, remember to keep an eye out for a fair wind; batten down during a storm; hail all passing ships; and fly your colours proudly!
Quoted 7 lines · martin f krafft
also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2228 +0200]:
Quoted 2 lines
Correction; it was recieved, but no To: header was present, so it was discarded.
Is that necessary? I always use
/usr/sbin/sendmailfor mailing list subscriptions. The To header is completely useless anyway, isn't it? Why require it?
No, it's not not necessary. It's a bug--allthough quite harmless. It'll be fixed in next version--we already use Delivered-To: for sanity checks, so might as well use it exclusively if present.
Quoted 1 line
Anyway, I resent the subscription request.
Welcome :)
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2254 +0200]:
Quoted 3 lines
No, it's not not necessary. It's a bug--allthough quite harmless. It'll be fixed in next version--we already use Delivered-To: for sanity checks, so might as well use it exclusively if present.
Right. Please consider that Delivered-To is non-standard. Postfix and qmail do it. exim and sendmail don't, I think.
Signature · 8 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] "alle vorurteile kommen aus den eingeweiden." - friedrich nietzsche
Quoted 7 lines · martin f krafft
also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2254 +0200]:
Quoted 3 lines
No, it's not not necessary. It's a bug--allthough quite harmless. It'll be fixed in next version--we already use Delivered-To: for sanity checks, so might as well use it exclusively if present.
Right. Please consider that Delivered-To is non-standard. Postfix and qmail do it. exim and sendmail don't, I think.
Yeah, if it's there it's used, if not fallback to To: is done. It's a shame it didn't make it into the standards.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2300 +0200]:
Quoted 2 lines
Yeah, if it's there it's used, if not fallback to To: is done. It's a shame it didn't make it into the standards.
Why don't you just rely on the envelope recipient?
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] it may look like i'm just sitting here doing nothing. but i'm really actively waiting for all my problems to go away.
Quoted 5 lines · martin f krafft
also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2300 +0200]:
Quoted 2 lines
Yeah, if it's there it's used, if not fallback to To: is done. It's a shame it didn't make it into the standards.
Why don't you just rely on the envelope recipient?
Which header is that? I've looked through the RFCs but didn't find it, so please educate me, there's nothing I would rather do.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2305 +0200]:
Quoted 2 lines
Which header is that? I've looked through the RFCs but didn't find it, so please educate me, there's nothing I would rather do.
Return-Path, I think.
Alternatively, you could not go via /etc/aliases and pass recipient as argument to a transport/director script.
Signature · 10 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] "not the truth in whose possession any man is, or thinks he is, but the honest effort he has made to find out the truth, is what constitutes the worth of man." -- gotthold lessing
Quoted 5 lines · martin f krafft
also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2305 +0200]:
Quoted 2 lines
Which header is that? I've looked through the RFCs but didn't find it, so please educate me, there's nothing I would rather do.
Return-Path, I think.
Return-Path is the envelope from. RFC{,2}821.
Quoted 2 lines
Alternatively, you could not go via
/etc/aliasesand pass recipient as argument to a transport/director script.
In that case you might as well set the Delivered-To: in case you don't have, because in case you do have it, it's the envelope to.
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.also sprach Mads Martin Joergensen <[email protected]> [2004.09.20.2317 +0200]:
Quoted 3 lines
Quoted 1 line
Return-Path, I think.
Return-Path is the envelope from. RFC{,2}821.
ah, right. sorry, i mixed that up.
Quoted 5 lines
Quoted 2 lines
Alternatively, you could not go via
/etc/aliasesand pass recipient as argument to a transport/director script.In that case you might as well set the Delivered-To: in case you don't have, because in case you do have it, it's the envelope to.
True. But how will you make it work reliably with exim and sendmail (and zmailer, I think)?
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] "sometimes the urge to do bad is nearly overpowering" -- ben horne
Quoted 8 lines · martin f krafft
Quoted 5 lines
Quoted 2 lines
Alternatively, you could not go via
/etc/aliasesand pass recipient as argument to a transport/director script.In that case you might as well set the Delivered-To: in case you don't have, because in case you do have it, it's the envelope to.
True. But how will you make it work reliably with exim and sendmail (and zmailer, I think)?
When Delivered-To: is not there, I'm relying on the To: header.
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.Quoted 2 lines · martin f krafft
Quoted 2 lines
Quoted 2 lines
Alternatively, you could not go via
/etc/aliasesand pass recipient as argument to a transport/director script.
How do you do that? Remember, we need the extended part (+stuff) as well.
Quoted 5 lines
Quoted 2 lines
In that case you might as well set the Delivered-To: in case you don't have, because in case you do have it, it's the envelope to.
True. But how will you make it work reliably with exim and sendmail (and zmailer, I think)?
When you configure your mail server for mlmmj, just make sure to set it up to add a Delivered-To: header. Thats reliable.
Morten
Signature · 2 lines
Morten K. Poulsen <[email protected]> http://www.afdelingp.dk/
also sprach Morten K. Poulsen <[email protected]> [2004.09.21.1242 +0200]:
Quoted 6 lines · martin f krafft
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Alternatively, you could not go via
/etc/aliasesand pass recipient as argument to a transport/director script.How do you do that? Remember, we need the extended part (+stuff) as well.
The mailers can pass arguments to the transporters. For an example of how I do it with postfix/mailman right now:
http://mail.python.org/pipermail/mailman-users/2004-January/033730.html
Quoted 2 lines
When you configure your mail server for mlmmj, just make sure to set it up to add a Delivered-To: header. Thats reliable.
I don't think sendmail/exim/zmailer can do that. But I would be happy to be proven wrong.
In any case, this was just a heads-up. I am never going to use anything but postfix anyway.
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] it is better to have loft and lost than to never have loft at all. -- groucho marx
Quoted 1 line · martin f krafft
The mailers can pass arguments to the transporters.
OK, so adding an optional argument to mlmmj-receive with the envelope-to will solve this issue for all mailers. If your mailer does not support adding Delivered-To: you can pass it as an argument and have mlmmj-receive add it. That should work for all cases, right?
Quoted 5 lines
Quoted 2 lines
When you configure your mail server for mlmmj, just make sure to set it up to add a Delivered-To: header. Thats reliable.
I don't think sendmail/exim/zmailer can do that. But I would be happy to be proven wrong.
I know Exim can, but I think sendmail needs to be patched to do it. I don't know about zmailer.
Quoted 2 lines
In any case, this was just a heads-up. I am never going to use anything but postfix anyway.
Some people might be using sendmail, and we want them to be able to use mlmmj too :-)
Morten
Signature · 2 lines
Morten K. Poulsen <[email protected]> http://www.afdelingp.dk/
also sprach Morten K. Poulsen <[email protected]> [2004.09.21.1654 +0200]:
Quoted 4 lines
OK, so adding an optional argument to mlmmj-receive with the envelope-to will solve this issue for all mailers. If your mailer does not support adding Delivered-To: you can pass it as an argument and have mlmmj-receive add it. That should work for all cases, right?
Yeah, sure. And that argument should be available by the time of /etc/aliases.db parsing.
Quoted 5 lines
Quoted 2 lines
In any case, this was just a heads-up. I am never going to use anything but postfix anyway.
Some people might be using sendmail, and we want them to be able to use mlmmj too :-)
Clearly a necessity. I mean, people seem to like retro-technology.
/me ducks
(Eric Allman is a good acquaintance of mine)
Signature · 9 lines
martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver! spamtraps: [email protected] "computer science is no more about computers than astronomy is about telescopes." -- edsgar w. dijkstra