www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <j...@apache.org>
Subject [jira] Closed: (INFRA-2041) Stale DNS / MX Entries somewhere in the Apache servers?
Date Fri, 08 May 2009 01:51:45 GMT

     [ https://issues.apache.org/jira/browse/INFRA-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joe Schaefer closed INFRA-2041.
-------------------------------

    Resolution: Fixed

I've verified that the dns entries are current on hermes, so there's
nothing to fix at this point.  Keep in mind that those ezmlm messages
take more than a week to be delivered, so the problem has long since
passed since you received them.

> Stale DNS / MX Entries somewhere in the Apache servers?
> -------------------------------------------------------
>
>                 Key: INFRA-2041
>                 URL: https://issues.apache.org/jira/browse/INFRA-2041
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Henning Schmiedehausen
>
> I get these messages:
> Hi! This is the ezmlm program. I'm managing the
> party@apache.org mailing list.
> Messages to you from the party mailing list seem to
> have been bouncing. I've attached a copy of the first bounce
> message I received.
> If this message bounces too, I will send you a probe. If the probe bounces,
> I will remove your address from the party mailing list,
> without further notice.
> I've kept a list of which messages from the party mailing list have
> bounced from your address.
> Here are the message numbers:
>   1713
>   1712
>   1711
> --- Enclosed is a copy of the bounce message I received.
> -----------------------------------------------------
> The reason for this is this:
> --- cut ---
> Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
>        by mail.hometree.net (8.13.8/8.13.8) with SMTP id n3NGcdEK009091
>        for <hps@intermeta.de>; Thu, 23 Apr 2009 18:39:11 +0200
> Received: (qmail 40481 invoked by uid 500); 23 Apr 2009 16:35:59 -0000
> Mailing-List: contact party-help@apache.org; run by ezmlm
> Reply-To: party@apache.org
> Precedence: bulk
> list-help: <mailto:party-help@apache.org>
> list-unsubscribe: <mailto:party-unsubscribe@apache.org>
> List-Post: <mailto:party@apache.org>
> List-Id: <party.apache.org>
> Delivered-To: mailing list party@apache.org
> Received: (qmail 39870 invoked by uid 99); 23 Apr 2009 16:33:26 -0000
> Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
> --- cut ---
> However, the MX records for "intermeta.de" point to 
> intermeta.de.           14400   IN      MX      30 ASPMX2.GOOGLEMAIL.COM.
> intermeta.de.           14400   IN      MX      30 ASPMX3.GOOGLEMAIL.COM.
> intermeta.de.           14400   IN      MX      30 ASPMX4.GOOGLEMAIL.COM.
> intermeta.de.           14400   IN      MX      30 ASPMX5.GOOGLEMAIL.COM.
> intermeta.de.           14400   IN      MX      10 ASPMX.L.GOOGLE.COM.
> intermeta.de.           14400   IN      MX      20 ALT1.ASPMX.L.GOOGLE.COM.
> intermeta.de.           14400   IN      MX      20 ALT2.ASPMX.L.GOOGLE.COM.
> and the SOA record has been updated a while ago:
> intermeta.de.           3600    IN      SOA     nsb.hometree.net. hostmaster.hometree.net.
2009042503 86400 7200 3600000 172800
> So why does hermes insist to deliver this mail to a server that used to be an MX host
for intermeta.de up until about two weeks ago. Are these entries cached somewhere and don't
time out? 
> Please verify the reason and fix it. I'd like to have my daily party mail fix. ;-) 

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


Mime
View raw message