History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: HAUS-909
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Andrew Perepelytsya
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Haus Chores

Relay denied when sending to mule mailing list

Created: 07/Sep/05 07:27 AM   Updated: 06/Mar/06 03:16 PM
Component/s: Mail Lists
Affects Version/s: short-term
Fix Version/s: short-term

Time Tracking:
Not Specified


 Description  « Hide
I cannot send to dev<at>mule.codehaus.org, tried both the gmail and corporate account, the result is the same. Below is a sample delivery failure (gmail):

X-Gmail-Received: 25b939439bdb437f7d9a0152bc25759b0b2d2943
Delivered-To: aperepel@gmail.com
Received: by 10.38.24.41 with SMTP id 41cs47924rnx;
Wed, 7 Sep 2005 05:20:59 -0700 (PDT)
Received: by 10.38.90.43 with SMTP id n43mr1401182rnb;
Wed, 07 Sep 2005 05:20:59 -0700 (PDT)
From: Mail Delivery Subsystem <mailer-daemon@gmail.com>
To: aperepel@gmail.com
Subject: Delivery Status Notification (Failure)
Date: Wed, 07 Sep 2005 05:20:59 -0700 (PDT)

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

dev@mule.codehaus.org

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 10): 550 5.7.1 <dev@mule.codehaus.org>... Relaying denied

----- Original message -----

Received: by 10.38.90.43 with SMTP id n43mr1066340rnb;
Wed, 07 Sep 2005 05:20:58 -0700 (PDT)
Received: by 10.38.24.41 with HTTP; Wed, 7 Sep 2005 05:20:57 -0700 (PDT)
Message-ID: <d075621f05090705205fe1957f@mail.gmail.com>
Date: Wed, 7 Sep 2005 08:20:58 -0400
From: Andrew Perepelytsya <aperepel@gmail.com>
To: dev@mule.codehaus.org
Subject: Current component versions
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Ross,

... <message content goes here>

Thanks,
Andrew

----- End of message -----



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ben Walding - 07/Sep/05 05:09 PM
DNS was broken (tinydns had started with an old zone file rather than named which contains the new zone file)