Testing from a "+" email address.
I want to see if <john+gtalug-talk@example.org> would work with mailman. Or would the person on the other end have to register with both email addresses. -- Myles Braithwaite | http://mylesb.ca/e/miys
On 18 August 2014 13:21, Myles Braithwaite <myles@monkeyinyoursoul.com> wrote:
I want to see if <john+gtalug-talk@example.org> would work with mailman. Or would the person on the other end have to register with both email addresses.
-- Myles Braithwaite | http://mylesb.ca/e/miys
--- GTALUG Talk Mailing List - talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
I registered with a "+" in my gmail address earlier today. It appears to be working fine as I clearly received your message ... -- Giles http://www.gilesorr.com/ gilesorr@gmail.com
On Mon, Aug 18, 2014 at 1:33 PM, Giles Orr <gilesorr@gmail.com> wrote:
I registered with a "+" in my gmail address earlier today. It appears to be working fine as I clearly received your message ...
The problem is with sending the email. If you setup with <alex+gtalug@example.org> you have to send using that as while or get caught in the moderation and a moderator has to approve your second email for sending only (not receiving) and will not show up in the membership area of mailman. The issue I'm trying to figure out is in the scenario where an email address get hijacked and starts sending mail to the list. How can we modorate that email if it's not in the membership area of mailman. Working on it over here: <https://github.com/gtalug/infrastructure/issues/30>.
On 2014-08-18 1:47 PM, Myles Braithwaite wrote:
On Mon, Aug 18, 2014 at 1:33 PM, Giles Orr <gilesorr@gmail.com> wrote:
I registered with a "+" in my gmail address earlier today. It appears to be working fine as I clearly received your message ...
The problem is with sending the email. If you setup with <alex+gtalug@example.org> you have to send using that as while or get caught in the moderation and a moderator has to approve your second email for sending only (not receiving) and will not show up in the membership area of mailman.
The issue I'm trying to figure out is in the scenario where an email address get hijacked and starts sending mail to the list. How can we modorate that email if it's not in the membership area of mailman.
Working on it over here: <https://github.com/gtalug/infrastructure/issues/30>.
For a use case like this where there are a few thousand subscribers, is it worth supporting sub-address sending, where it has not been supported since the inception of the list (at least I think this is the case). Perhaps limit subscriber addresses using ban_list and then it is a non-issue. Admittedly, I like sub-addressing and use it everywhere. An option to make that work would be to use an umbrella list with accept_these_nonmembers. The process would be something like: user+subaddress@domain.com signs up to subaddress specific list, with their subaddress. user@domain.com signs up to top level list with normal address. Now, with accept_these_nonmembers including the subaddress list of subscribers, the top level list will accept a message from user+subaddress@domain.com. I'm not sure how to control duplicate messages, or what the gain is here since the user could just subscribe to the top level list with their subaddress, but perhaps there's some moderation bits that could be set to limit delivery? Just a thought, Jamon
This can be handled in gmail: https://productforums.google.com/forum/#!topic/gmail/Jifa7JPNH_I (Follow the first answer link). Essentially you have to set up the name+subaddress@gmail.com as another email address (even though, strictly speaking, it's not), and then every time you email the list you have to look for "From" (next to CC and BCC) and change to the appropriate subaddress. Kind of a PITA, but I guess it'll have to do as gmail only has incoming email filters, not outgoing ones (that I can see). On 18 August 2014 14:05, Jamon Camisso <jamon.camisso@utoronto.ca> wrote:
On 2014-08-18 1:47 PM, Myles Braithwaite wrote:
On Mon, Aug 18, 2014 at 1:33 PM, Giles Orr <gilesorr@gmail.com> wrote:
I registered with a "+" in my gmail address earlier today. It appears to be working fine as I clearly received your message ...
The problem is with sending the email. If you setup with <alex+gtalug@example.org> you have to send using that as while or get caught in the moderation and a moderator has to approve your second email for sending only (not receiving) and will not show up in the membership area of mailman.
The issue I'm trying to figure out is in the scenario where an email address get hijacked and starts sending mail to the list. How can we modorate that email if it's not in the membership area of mailman.
Working on it over here: < https://github.com/gtalug/infrastructure/issues/30>.
For a use case like this where there are a few thousand subscribers, is it worth supporting sub-address sending, where it has not been supported since the inception of the list (at least I think this is the case).
Perhaps limit subscriber addresses using ban_list and then it is a non-issue.
Admittedly, I like sub-addressing and use it everywhere. An option to make that work would be to use an umbrella list with accept_these_nonmembers. The process would be something like:
user+subaddress@domain.com signs up to subaddress specific list, with their subaddress.
user@domain.com signs up to top level list with normal address.
Now, with accept_these_nonmembers including the subaddress list of subscribers, the top level list will accept a message from user+subaddress@domain.com.
I'm not sure how to control duplicate messages, or what the gain is here since the user could just subscribe to the top level list with their subaddress, but perhaps there's some moderation bits that could be set to limit delivery?
Just a thought, Jamon
participants (5)
-
Giles Orr -
Giles Orr -
Jamon Camisso -
Myles Braithwaite -
Myles Braithwaite