You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org> on 2009/07/27 10:31:15 UTC

[jira] Commented: (INFRA-2109) EZMLM is messed up!

    [ https://issues.apache.org/jira/browse/INFRA-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735524#action_12735524 ] 

#asfinfra IRC Bot commented on INFRA-2109:
------------------------------------------

<pquerna> We have discussed migrating to mlmmj from ezmlm, but it really lacks active volunters to undergo such a large change to the email infrastructure.


> EZMLM is messed up!
> -------------------
>
>                 Key: INFRA-2109
>                 URL: https://issues.apache.org/jira/browse/INFRA-2109
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Mailing Lists
>            Reporter: Niclas Hedhman
>
> I am using mail aliases, so that I can send email FROM:niclas@hedhman.org using the GMail client. This is a documented feature at GMail.
> Now, when I am sending subscription emails to Apache MLs, I need to use the extended version (annoying but have been working often) as dev-subscribe-niclas=hedhman.org@abc.apache.org and emails will arrive.
> However, whenever I send an email from the GMail client, EZMLM will use the "Return-Path:" header to determine if I am subscribed or not. So, for mailing lists with a moderator, they end up adding my GMail address to the allowed posters list, but for lists without moderator, I am just not allowed to post, message bounces and if I am at that point trying to subscribe again (like above) it will tell me that I am already subscribed.
> I have no idea why the FROM field is not used, but I have reached the boiling point of what to tolerate. I don't know if this is a configuration of EZMLM or if it is hard coded into it, but whatever it is, I need to change this. I am cut out from posting to community@apache.org for this same reason (subscribed as niclas@apache.org as stipulated by instructions given) and now at least one other list is in the same situation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.