You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Joseph Mocker (JIRA)" <ji...@apache.org> on 2008/11/10 18:45:44 UTC
[jira] Created: (INFRA-1788) Mailing lists not sending to
fakebelieve.org domain
Mailing lists not sending to fakebelieve.org domain
---------------------------------------------------
Key: INFRA-1788
URL: https://issues.apache.org/jira/browse/INFRA-1788
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: Mailing Lists
Reporter: Joseph Mocker
For the last several weeks I have only intermittently been receiving mail from the Apache mailing list jspwiki-users.
I received a mail (below) last week from the Apache ezmlm which mentioned mails were bouncing and showed a transcript of one of the attempts. The transcript mentions attempting to contact the SMTP server at 64.202.166.12 which happens to be owned by my DNS registrar (Godaddy).
I verified that my MX records are correctly pointing to my SMTP server. And have contacted Godaddy support to have them verify things on their end. Everything looks good, and yet I am still not receiving messages.
So I am wondering if the ezmlm or related processes are caching MX entries somehow? Do you know if this could be the case? Is there anything you can check on your end?
I am at a loss, its been over a week. I've even made changes to my DNS MX entries and still I am not receiving mails.
I would appreciate anything you could do to help.
--- ezmlm message ---
Hi! This is the ezmlm program. I'm managing the
jspwiki-user@incubator dot apache dot org mailing list.
I'm working for my owner, who can be reached
at jspwiki-user-owner@incubator dot apache dot org.
Messages to you from the jspwiki-user 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 jspwiki-user mailing list,
without further notice.
I've kept a list of which messages from the jspwiki-user mailing list have
bounced from your address.
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 35203 invoked for bounce); 27 Oct 2008 19:06:14 -0000
Date: 27 Oct 2008 19:06:14 -0000
From: MAILER-DAEMON@apache dot org
To: jspwiki-user-return-1484-@incubator dot apache dot org
Subject: failure notice
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<mock+jspwiki at fakebelieve dot org>:
64.202.166.12 does not like recipient.
Remote host said: 550 sorry, mail to that recipient is not accepted (#5.7.1)
Giving up on 64.202.166.12.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-1788) Mailing lists not sending to
fakebelieve.org domain
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-1788.
-------------------------------
Resolution: Fixed
I don't see any evidence of delivery failures
in the last week of logfiles, so I'm guessing
that this was a temporary problem that is
now resolved.
> Mailing lists not sending to fakebelieve.org domain
> ---------------------------------------------------
>
> Key: INFRA-1788
> URL: https://issues.apache.org/jira/browse/INFRA-1788
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Mailing Lists
> Reporter: Joseph Mocker
>
> For the last several weeks I have only intermittently been receiving mail from the Apache mailing list jspwiki-users.
> I received a mail (below) last week from the Apache ezmlm which mentioned mails were bouncing and showed a transcript of one of the attempts. The transcript mentions attempting to contact the SMTP server at 64.202.166.12 which happens to be owned by my DNS registrar (Godaddy).
> I verified that my MX records are correctly pointing to my SMTP server. And have contacted Godaddy support to have them verify things on their end. Everything looks good, and yet I am still not receiving messages.
> So I am wondering if the ezmlm or related processes are caching MX entries somehow? Do you know if this could be the case? Is there anything you can check on your end?
> I am at a loss, its been over a week. I've even made changes to my DNS MX entries and still I am not receiving mails.
> I would appreciate anything you could do to help.
> --- ezmlm message ---
> Hi! This is the ezmlm program. I'm managing the
> jspwiki-user@incubator dot apache dot org mailing list.
> I'm working for my owner, who can be reached
> at jspwiki-user-owner@incubator dot apache dot org.
> Messages to you from the jspwiki-user 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 jspwiki-user mailing list,
> without further notice.
> I've kept a list of which messages from the jspwiki-user mailing list have
> bounced from your address.
> --- Enclosed is a copy of the bounce message I received.
> Return-Path: <>
> Received: (qmail 35203 invoked for bounce); 27 Oct 2008 19:06:14 -0000
> Date: 27 Oct 2008 19:06:14 -0000
> From: MAILER-DAEMON@apache dot org
> To: jspwiki-user-return-1484-@incubator dot apache dot org
> Subject: failure notice
> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
> <mock+jspwiki at fakebelieve dot org>:
> 64.202.166.12 does not like recipient.
> Remote host said: 550 sorry, mail to that recipient is not accepted (#5.7.1)
> Giving up on 64.202.166.12.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.