can my list have multiple email addresses?

[angell]

We are using nabble2 to archive our open source community mailing lists (housed externally) and people email those lists using one of two similar email addresses, eg:
[e-mail]
[e-mail]

Is there a way to archive messages sent to either address?

[Will <Nabble>]

You can try put the same nabble archive address on the subscriber list for both lists. A potential problem is that if an email is sent to both lists, it will get double archived on Nabble.

[angell]

There aren't two different lists, just one list that one can address with two different email addresses.

Is there a way to get the nabble to archive messages whether they are addressed to either address?

Right now, messages are being ignored if they are addressed to [e-mail], because the nabble archive is subscribed to the list at [e-mail].

Return-path: <[e-mail]>
Envelope-to: [e-mail]
Delivery-date: Fri, 31 Oct 2008 17:23:07 -0700
Received: from gwrg.uhi.ac.uk ([194.35.192.18] helo=relay.uhi.ac.uk)
        by kuber.nabble.com with esmtp (Exim 4.63)
        (envelope-from <[e-mail]>)
        id 1Kw4Ge-0007Kt-Ro
        for [e-mail]; Fri, 31 Oct 2008 17:23:07 -0700
Received: from paploo.uhi.ac.uk [10.131.1.134]
        by relay.uhi.ac.uk; Sat, 01 Nov 2008 00:22:21 +0000
Message-ID: <[e-mail]>
Mime-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_Part_44892_21691538.1225498910203"
Received: from prod.collab.uhi.ac.uk ([194.35.219.182])
          by paploo.uhi.ac.uk (JAMES SMTP Server 2.1.3) with SMTP ID 707;
          Sat, 1 Nov 2008 00:15:10 +0000 (GMT)
Received: from smtp-out1.berkeley.edu (smtp-out1.Berkeley.EDU [128.32.61.106])
        by shmi.uhi.ac.uk (Postfix) with ESMTP id E0A982C7822;
        Sat,  1 Nov 2008 00:15:09 +0000 (GMT)
Received: from dhcp-169-229-212-8.lips.berkeley.edu ([169.229.212.8] helo=[192.168.1.100])
        by fe4.calmail with esmtpsa (TLSv1:AES128-SHA:128)
        (Exim 4.68)
        (auth plain:[e-mail])
        (envelope-from <[e-mail]>)
        id 1Kw48p-0005GP-FP; Fri, 31 Oct 2008 17:15:00 -0700
From: Kevin Chan <[e-mail]>
To: [e-mail]
X-Content-Type-Outer-Envelope: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Date: Fri, 31 Oct 2008 17:14:59 -0700
Cc: [e-mail]
X-Mailer: Apple Mail (2.929.2)
X-Content-Type-Message-Body: text/plain; charset=US-ASCII; format=flowed; delsp=yes
X-Content-Type-Message-Body: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Precedence: bulk
X-SA-Exim-Connect-IP: 194.35.192.18
X-SA-Exim-Mail-From: [e-mail]
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on kuber.nabble.com
X-Spam-Level:
X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,
        MSGID_FROM_MTA_HEADER autolearn=no version=3.2.3
Subject: Feedback on network configuration modifications to Sakai
 Jira/Confluence
X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000)
X-SA-Exim-Scanned: Yes (on kuber.nabble.com)
X-Nabble-Original-Envelope-To: [e-mail]

------=_Part_44892_21691538.1225498910203
Content-Type: text/plain ; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Hi all,

After some testing between our sysadmin and Michael Korcuska (thanks  
for volunteering!), the service that is hosting the Sakai Jira/
Confluence has undergone some network modifications that will  
hopefully smooth the way for those of you who have had trouble  
accessing these sites.

So if you experience any access issues starting today, please let us  
know at [e-mail] and we will pass those along to  
our sysadmin for further evaluation.

Thanks,

   Kevin Chan
   [e-mail]

   Operations Team
   Educational Technology Services
   University of California, Berkeley





----------------------
This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.

------=_Part_44892_21691538.1225498910203
Content-Type: text/html ; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
<html>  <head><title>Feedback on network configuration modifications to Sakai Jira/Confluence</title></head>  <body>Hi all,
<br />

<br />
After some testing between our sysadmin and Michael Korcuska (thanks  
<br />
for volunteering!), the service that is hosting the Sakai Jira/
<br />
Confluence has undergone some network modifications that will  
<br />
hopefully smooth the way for those of you who have had trouble  
<br />
accessing these sites.
<br />

<br />
So if you experience any access issues starting today, please let us  
<br />
know at [e-mail] and we will pass those along to  
<br />
our sysadmin for further evaluation.
<br />

<br />
Thanks,
<br />

<br />
   Kevin Chan
<br />
   [e-mail]
<br />

<br />
   Operations Team
<br />
   Educational Technology Services
<br />
   University of California, Berkeley
<br />

<br />

<br />

<br />

<br />
<br/><hr/><br/>This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org//portal) from the DG: Development (a.k.a. sakai-dev) site.<br/>You can modify how you receive notifications at My Workspace > Preferences.<br/>  </body></html>

------=_Part_44892_21691538.1225498910203--

[tomi]

We currently don't support multiple email aliases for the same list. When the nabble archiver receives an email, we look at the headers for the list address to make sure it is a mailing list email, otherwise we will end up archiving random spam too. Most listservers add some headers like X-BeenThere, X-Mailing-List, or List-Id, if you have control over the listserver, can you add one of those headers and have it always set to [e-mail]? This will be the simplest fix until we add support for multiple list addresses.