You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2005/08/05 00:55:40 UTC
[jira] Created: (INFRA-486) List mail sent to wrong server
List mail sent to wrong server
------------------------------
Key: INFRA-486
URL: http://issues.apache.org/jira/browse/INFRA-486
Project: Infrastructure
Type: Bug
Reporter: Mark Thomas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-486) List mail sent to wrong server
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-486?page=comments#action_12317759 ]
Henning Schmiedehausen commented on INFRA-486:
----------------------------------------------
Nothing out of the ordinary here:
% host -t mx laguna-industries.com
laguna-industries.com mail is handled by 20 mail.phnx.uswest.net.
laguna-industries.com mail is handled by 10 mail.laguna-industries.com.
% host mail.phnx.uswest.net.
mail.phnx.uswest.net has address 63.231.195.31
host -t ptr 31.195.231.63.in-addr.arpa.
31.195.231.63.in-addr.arpa domain name pointer mpls-pop.inet.qwest.net.
qmail chose the secondary MX (which is the mpls-pop.inet.qwest.net), probably because it could not reach the primary MX.
Nothing wrong, everything is cool.
Seems to be a faulty mailserver setup at laguna-industries.com. Unfortunately, in these days where everyone that can put a CD
the right way up in a drive is a Linux/Unix/Windows/Internet Expert, this has become pretty common. And with a network that
tolerates almost everything to get a mail somehow in the right place, it is only seldom noticed (or when it is, it is blamed on
Microsoft. :-) )
> List mail sent to wrong server
> ------------------------------
>
> Key: INFRA-486
> URL: http://issues.apache.org/jira/browse/INFRA-486
> Project: Infrastructure
> Type: Bug
> Components: Mail (qmail)
> Reporter: Mark Thomas
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-486) List mail sent to wrong server
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-486?page=all ]
Mark Thomas updated INFRA-486:
------------------------------
Component: Mail (qmail)
> List mail sent to wrong server
> ------------------------------
>
> Key: INFRA-486
> URL: http://issues.apache.org/jira/browse/INFRA-486
> Project: Infrastructure
> Type: Bug
> Components: Mail (qmail)
> Reporter: Mark Thomas
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-486) List mail sent to wrong server
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-486?page=all ]
Mark Thomas closed INFRA-486:
-----------------------------
Resolution: Invalid
Thanks for taking the time to explain this. I'll know what to look for next time someone reports something like this.
> List mail sent to wrong server
> ------------------------------
>
> Key: INFRA-486
> URL: http://issues.apache.org/jira/browse/INFRA-486
> Project: Infrastructure
> Type: Bug
> Components: Mail (qmail)
> Reporter: Mark Thomas
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-486) List mail sent to wrong server
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-486?page=comments#action_12317694 ]
Mark Thomas commented on INFRA-486:
-----------------------------------
Sorry about the sparse message - finger trouble. Full details are as follows:
<fact>
One of the tomcat-user subscribers reported receiving a ezmlm warning re bounced messages. A little research showed the the bounced mail had been sent to the wrong server.
It should have been sent to 65.123.156.4 (mail.laguna-industries.com)
It was sent to 63.231.195.31 (mpls-pop.inet.qwest.net)
There is at least one qwest.net address subscribed to the tomcat-user list
Headers from the original bounce were:
Received: (qmail 2561 invoked for bounce); 22 Jul 2005 20:07:17 -0000
Date: 22 Jul 2005 20:07:17 -0000
From: MAILER-DAEMON@apache.org
To: tomcat-user-return-130092-@jakarta.apache.org
Subject: failure notice
I tried googling but couldn't find anything to shed any light on what might be going on.
</fact>
<speculation>
Some form of threading issue associated with looking up the mail server address? I guess dnscache and qmail-remote are candidates for this.
It might be ezmlm since users from both domains are subscribed to tomcat-user but AFAIK ezmlm doesn't use DNS and this is a DNS mix up.
It could also be a genuine error in the DNS data but the odds seem rather long on this one.
</speculation>
> List mail sent to wrong server
> ------------------------------
>
> Key: INFRA-486
> URL: http://issues.apache.org/jira/browse/INFRA-486
> Project: Infrastructure
> Type: Bug
> Components: Mail (qmail)
> Reporter: Mark Thomas
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira