But you get the emails sent to the list (I can see you are subscribed
to it)? How odd - wonder if it's temporary or something wrong at the
codehaus mail settings? Cc:ing tynamo users just to see if it goes
through.

Kalle


On Wed, Aug 3, 2011 at 2:37 PM, Lenny Primak <lpri...@hope.nyc.ny.us> wrote:
> Fwd: Returned mail: see transcript for details
>
>
>
> Begin forwarded message:
>
>> From: Mail Delivery Subsystem <mailer-dae...@aceinnovative.com>
>> Date: August 3, 2011 1:12:15 PM CDT
>> To: <lpri...@hope.nyc.ny.us>
>> Subject: Returned mail: see transcript for details
>>
>
>> The original message was received at Fri, 29 Jul 2011 12:14:39 -0400
>> from user-0cdfs5f.cable.mindspring.com [24.215.240.175]
>>
>>   ----- The following addresses had permanent fatal errors -----
>> <u...@tynamo.codehaus.org>
>>    (reason: 451 IP 66.114.74.12 is UCEPROTECT-Level 1 listed. See 
>> http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12)
>>
>>   ----- Transcript of session follows -----
>> ... while talking to mail.codehaus.org.:
>>>>> RCPT To:<u...@tynamo.codehaus.org>
>> <<< 451 IP 66.114.74.12 is UCEPROTECT-Level 1 listed. See 
>> http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12
>> <u...@tynamo.codehaus.org>... Deferred: 451 IP 66.114.74.12 is 
>> UCEPROTECT-Level 1 listed. See 
>> http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12
>> Message could not be delivered for 5 days
>> Message will be deleted from queue
>> Reporting-MTA: dns; mail1.aceinnovative.com Arrival-Date: Fri, 29 Jul 2011 
>> 12:14:39 -0400 Original-Recipient: rfc822;u...@tynamo.codehaus.org 
>> Final-Recipient: RFC822; u...@tynamo.codehaus.org Action: failed Status: 
>> 4.4.7 Remote-MTA: DNS; mail.codehaus.org Diagnostic-Code: SMTP; 451 IP 
>> 66.114.74.12 is UCEPROTECT-Level 1 listed. See 
>> http://www.uceprotect.net/rblcheck.php?ipr=66.114.74.12 Last-Attempt-Date: 
>> Wed, 3 Aug 2011 14:12:15 -0400
>> I get this error message, just to clarify, it looks like a slightly 
>> different message that Taha is getting:
>> WARNING: Unable to add 'SecurityConfiguration' as a dependency of 
>> 'StoreIntoGlobals', as that forms a dependency cycle ('StoreIntoGlobals' 
>> depends on itself via 'SecurityConfiguration'). The dependency has been 
>> ignored.
>>
>> Taha, maybe you are using 0.3.0 by mistake?
>>
>> On Jul 29, 2011, at 1:16 AM, Kalle Korhonen wrote:
>>
>>> Oh yes, the warning's still there, only it's called
>>> SecurityConfiguration as I said.
>>>
>>> Kalle
>>>
>>>
>>> On Thu, Jul 28, 2011 at 9:33 PM, Taha Hafeez <tawus.tapes...@gmail.com> 
>>> wrote:
>>>> Yes, we are also using 0.4.0 and the warning is still there
>>>>
>>>> regards
>>>> Taha
>>>>
>>>> On Fri, Jul 29, 2011 at 10:01 AM, Lenny Primak <lpri...@hope.nyc.ny.us> 
>>>> wrote:
>>>>> I can definitely confirm that the warning appears in 0.4.0.
>>>>> I think there is something wrong with the 0.4.0 in the maven central repo,
>>>>> perhaps it's 0.3.0 masquerading as 0.4.0.  Perhaps the checksum errors
>>>>> are indicative of a deeper problem...
>>>>>
>>>>>
>>>>> On Jul 28, 2011, at 11:52 PM, Kalle Korhonen wrote:
>>>>>
>>>>>> On Tue, Jul 26, 2011 at 4:26 PM, Taha Hafeez <tawus.tapes...@gmail.com> 
>>>>>> wrote:
>>>>>>> Tapestry5 : 5.25
>>>>>>> tapestry-security : 0.4.0
>>>>>>> and at startup we have this warning
>>>>>>> [WARN] TapestryModule?.HttpServletRequestHandler? Unable to add
>>>>>>> 'StoreIntoGlobals?' as a dependency of 'SecurityRequestFilter?', as
>>>>>>> that forms a dependency cycle ('SecurityRequestFilter?' depends on
>>>>>>> itself via 'StoreIntoGlobals?'). The dependency has been ignored.
>>>>>>> I think it is because of the service ApplicationGlobals being injected
>>>>>>> into SecurityRequestFilter. Is it a concern ? and if so what is the
>>>>>>> solution ?
>>>>>>
>>>>>> You must be using 0.3.x since SecurityRequestFilter was refactored
>>>>>> into SecurityConfiguration in 0.4.0. Anyway, it's just a warning you
>>>>>> can ignore. We only use ApplicationGlobals to get the ServletContext.
>>>>>>
>>>>>> Kalle
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe from this list, please visit:
>>>>>>
>>>>>>   http://xircles.codehaus.org/manage_email
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe from this list, please visit:
>>>>>
>>>>>   http://xircles.codehaus.org/manage_email
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this list, please visit:
>>>>
>>>>   http://xircles.codehaus.org/manage_email
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>   http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to