Skip to contentSkip to conversation

feature: resending capability

mlmmj Sebastian Lipp 2 participants 7 messages Mar 4, 2013 – Mar 18, 2013

lore
Share & tools
lore
#0 lore raw

Hey there

I'm running several mailing lists with mlmmj and absolutely satisfied with this great piece of software. But there is one capability that would make me love mlmmj even more.

Theres a project where several people are involved. At the moment I'm the only one receiving it's mail. I'd like to have all mails forwarded to the project's mailing list to rise transparency and distribute the burden of dealing with mail to everyone involved. The problem with just forwarding and then cc-ing replies to outside people is that their replies won't be directed to the list but to the sender of the original reply.

I can think of a solution. If mlmmj parsed the mail's body and added $external_recipient to the list of recipients if the first non-empty body line was

X-RESEND-TO: $external_recipient

I'd be satisfied. Unfortunately my understanding of C is far from beeing good enough to make such a change to mlmmj's code, though I can imagine that this would just add a few lines of code while introducing a great new use case by empowering mlmmj to act as a gateway to contact a whole group transparently.

Is my assumption about the effort needed to introduce this feature right and is anybody willing to invest some minutes on this?

As an alternative: Is there any way to hook a filter (script) between the MTA and mlmmj that makes a copy of the mail and adds a Reply-To:
header or can you imagine any other solution for this that does not involve setting up another mailing list software? Perhaps by telling my MTA (postfix) to add the respective header line to any mail with a certain string in the To: field.

Signature · 1 line
basti
#1 lore raw

I don't think I fully understand the problem.

Wouldn't a traditional mailing list with a Reply-To header be sufficient for your needs? Those on the mailing list would know to use the Reply-All button to reply to both the list and the external sender, and the external sender could just use Reply to reply to the list.

Is there something I am missing?

Ben.

Quoted 36 lines · Sebastian Lipp

Hey there

I'm running several mailing lists with mlmmj and absolutely satisfied with this great piece of software. But there is one capability that would make me love mlmmj even more.

Theres a project where several people are involved. At the moment I'm the only one receiving it's mail. I'd like to have all mails forwarded to the project's mailing list to rise transparency and distribute the burden of dealing with mail to everyone involved. The problem with just forwarding and then cc-ing replies to outside people is that their replies won't be directed to the list but to the sender of the original reply.

I can think of a solution. If mlmmj parsed the mail's body and added $external_recipient to the list of recipients if the first non-empty body line was

X-RESEND-TO: $external_recipient

I'd be satisfied. Unfortunately my understanding of C is far from beeing good enough to make such a change to mlmmj's code, though I can imagine that this would just add a few lines of code while introducing a great new use case by empowering mlmmj to act as a gateway to contact a whole group transparently.

Is my assumption about the effort needed to introduce this feature right and is anybody willing to invest some minutes on this?

As an alternative: Is there any way to hook a filter (script) between the MTA and mlmmj that makes a copy of the mail and adds a Reply-To:
header or can you imagine any other solution for this that does not involve setting up another mailing list software? Perhaps by telling my MTA (postfix) to add the respective header line to any mail with a certain string in the To: field.

#2 lore raw
In reply to Sebastian Lipp
Quoted 8 lines · Ben Schmidt

I don't think I fully understand the problem.

Wouldn't a traditional mailing list with a Reply-To header be sufficient for your needs? Those on the mailing list would know to use the Reply-All button to reply to both the list and the external sender, and the external sender could just use Reply to reply to the list.

Is there something I am missing?

Yes. I already thought about that setup. The Problem here is that the external sender will get a mail that never went to the mailing list and thus won't have the Reply-To header unless all subscribers set it manually. I suspect that this will work without problems. So the reply of the external guy will not reach the list.

I really appreciate that you think about this.

Signature · 1 line
basti
#3 lore raw
In reply to Sebastian Lipp
Quoted 8 lines · Sebastian Lipp
Quoted 7 lines · Ben Schmidt

I don't think I fully understand the problem.

Wouldn't a traditional mailing list with a Reply-To header be sufficient for your needs? Those on the mailing list would know to use the Reply-All button to reply to both the list and the external sender, and the external sender could just use Reply to reply to the list.

Quoted 7 lines
Quoted 1 line

Is there something I am missing?

Yes. I already thought about that setup. The Problem here is that the external sender will get a mail that never went to the mailing list and thus won't have the Reply-To header unless all subscribers set it manually. I suspect that this will work without problems. So the reply of the external guy will not reach the list.

Ah, yes. That is a problem.

This is an interesting use case indeed.

However, doesn't your solution also require subscribers to take manual action? They would need to add the

X-RESEND-TO: $external_recipient

directive to the mail body.

It's also not completely easy to parse mail bodies. They can be base64 encoded, etc., have multiple MIME alternatives (e.g. plain text and HTML, and the order isn't always the same), and it all depends on the user's MUA.

I wonder if we can think of a better solution.

One thought I have is this: Make Mlmmj, for *non-subscribers only* set a variable Reply-To header including the extra recipient. So the external sender would send a message to Mlmmj, and Mlmmj would send that message to all list subscribers with a header something like

Reply-To: [email protected]

so when someone replies, it would go to the list address with additional information after the delimiter. Mlmmj would receive the reply along with the additional information, and include the extra address in the recipient list when distributing the post.

Mlmmj already has the ability to check for non-subscribers for the subonlypost and modnonsubposts options, manages the '+' delimiter in many scenarios, and can 'escape' and 'unescape' addresses for VERP bounce processing, so I don't suppose adding a CC ability would be too hard; might just need some fancy listcontrol logic and extra commandline switches for passing the extra recipient along.

How does this idea sound to you (and others)?

Ben.

#4 lore raw
In reply to Sebastian Lipp
Quoted 6 lines · Ben Schmidt

However, doesn't your solution also require subscribers to take manual action? They would need to add the

X-RESEND-TO: $external_recipient

directive to the mail body.

It would. But that way every subscriber is able to instantly see the mistake and step in.

Quoted 4 lines

It's also not completely easy to parse mail bodies. They can be base64 encoded, etc., have multiple MIME alternatives (e.g. plain text and HTML, and the order isn't always the same), and it all depends on the user's MUA.

Didn't think about that...

Quoted 7 lines

I wonder if we can think of a better solution.

One thought I have is this: Make Mlmmj, for *non-subscribers only* set a variable Reply-To header including the extra recipient. So the external sender would send a message to Mlmmj, and Mlmmj would send that message to all list subscribers with a header something like

Quoted 6 lines

Reply-To: [email protected]

so when someone replies, it would go to the list address with additional information after the delimiter. Mlmmj would receive the reply along with the additional information, and include the extra address in the recipient list when distributing the post.

Nice idea. But I want the possibility to discuss stuff from external people to find an appropriate answer and afterwards send out the reply on request. Your solution is only half way by having several people being able to reply and seeing each other's reply.

As I understand your suggestion any reply to such a mail from outside would also go outside.

Signature · 1 line
basti
#5 lore raw
In reply to Sebastian Lipp
Quoted 32 lines · Sebastian Lipp
Quoted 6 lines · Ben Schmidt

However, doesn't your solution also require subscribers to take manual action? They would need to add the

X-RESEND-TO: $external_recipient

directive to the mail body.

It would. But that way every subscriber is able to instantly see the mistake and step in.

Quoted 4 lines

It's also not completely easy to parse mail bodies. They can be base64 encoded, etc., have multiple MIME alternatives (e.g. plain text and HTML, and the order isn't always the same), and it all depends on the user's MUA.

Didn't think about that...

Quoted 7 lines

I wonder if we can think of a better solution.

One thought I have is this: Make Mlmmj, for *non-subscribers only* set a variable Reply-To header including the extra recipient. So the external sender would send a message to Mlmmj, and Mlmmj would send that message to all list subscribers with a header something like

Quoted 6 lines

Reply-To: [email protected]

so when someone replies, it would go to the list address with additional information after the delimiter. Mlmmj would receive the reply along with the additional information, and include the extra address in the recipient list when distributing the post.

Quoted 7 lines

Nice idea. But I want the possibility to discuss stuff from external people to find an appropriate answer and afterwards send out the reply on request. Your solution is only half way by having several people being able to reply and seeing each other's reply.

As I understand your suggestion any reply to such a mail from outside would also go outside.

Yes, that's correct.

I suggest that if you want to have a separate discussion without the external user, though, the correct thing to do would be to forward their message to the mailing list, discuss it on-list, and then have someone reply to the *original message* when the discussion is complete. If the external user is not actually involved in the discussion, they won't be replying all that often, so it shouldn't be a big hassle if they reply to an individual rather than to the list address; but the internal replyer can always set a Reply-To header to ensure subsequent replies go to the list if they want to. By replying to the external user's original message, you also ensure it appears in the correct thread/conversation from their point of view. Most MUAs these days have separate 'Reply List', 'Reply' and 'Reply All' buttons, so this is fairly easy for internal users--you can hand out the list address to external users who may have questions, and the internal users can discuss by using 'Reply List' or give the final response using 'Reply' or 'Reply All'. The only thing they need to do is remember to set the Reply-To header when sending the final response, if necessary.

This is less problematic than other alternatives. Requiring internal users to add a directive to the mail body is error prone: they could easily get the syntax or the address wrong, particularly if they are looking up the address from an earlier message. They will not have any support from their MUA, such as address autocompletion. Errors will sometimes be silently ignored, and other times result in bounce messages, but delivery to the list will succeed in both cases. That means to fix the problem, an additional message will need to be sent to the list, clogging people's inboxes. And that's if the problem is even noticed, rather than the external user simply never receiving anything. To fix this, Mlmmj would need to be able to detect errors, which is difficult, since Mlmmj wouldn't know whether the user intended the first line of the body to be a directive or not. Even if it could detect errors reliably, it would still need logic added to send bounce messages to the user in error. To be able to do any of this, it needs to parse mail bodies, which is not trivial either.

It would be possible to get both behaviours if the solution I suggested were implemented, but internal users would need to change the address if they wanted to discuss the issue internally, removing the local part of the address from the '+' delimiter. To deliver the final response, they could just reply as normal to the original message. If that solution is any good, we can explore it further.

But that's all I can really think of for now.

Ben.

#6 lore raw
In reply to Sebastian Lipp
Quoted 19 lines · Sebastian Lipp
Quoted 9 lines · Ben Schmidt

I suggest that if you want to have a separate discussion without the external user, though, the correct thing to do would be to forward their message to the mailing list, discuss it on-list, and then have someone reply to the *original message* when the discussion is complete. If the external user is not actually involved in the discussion, they won't be replying all that often, so it shouldn't be a big hassle if they reply to an individual rather than to the list address; but the internal replyer can always set a Reply-To header to ensure subsequent replies go to the list if they want to. By replying to the external user's original

Quoted 8 lines

message, you also ensure it appears in the correct thread/conversation from their point of view. Most MUAs these days have separate 'Reply List', 'Reply' and 'Reply All' buttons, so this is fairly easy for internal users--you can hand out the list address to external users who may have questions, and the internal users can discuss by using 'Reply List' or give the final response using 'Reply' or 'Reply All'. The only thing they need to do is remember to set the Reply-To header when sending the final response, if necessary.

Quoted 4 lines

Then I will live with that "solution". I'm convinced that any other option is not really practical. :D

Thanks.

OK, cool.

Sorry I couldn't be any more help!

Smiles,

Ben.