[Fwd: Delivery Status Notification (Failure)]

[El Gato Feo]

YES
             yes I see get this quite often I thought it was me.
Monitor plz look into this.
Thanks 
DAve

Jeff Vian <jvian10 at charter.net> wrote:
Is anybody else getting this?
It is happening every time I send a message to this list.
Annoying at the least, and filtering it will not stop it, only hide it.


-------- Forwarded Message --------
> From: postmaster at iwwd.ae
> To: jvian10 at charter.net
> Subject: Delivery Status Notification (Failure)
> Date: Sat, 5 Nov 2005 03:15:10 +0400
> 
> This is an automatically generated Delivery Status Notification.
> 
> Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
> 
> akbarvv at iwwd.ae
> 
> 
> 
> email message attachment
> -------- Forwarded Message --------
> > From: Jeff Vian 
> > Reply-To: For users of Fedora Core releases 
> > To: For users of Fedora Core releases 
> > Subject: Re: still struggling with ndiswrapper
> > Date: Fri, 04 Nov 2005 17:01:02 -0600 
> > 
> > On Fri, 2005-11-04 at 10:00 -0800, Rick Stevens wrote:
> > > On Fri, 2005-11-04 at 10:28 -0500, James Pifer wrote:
> > > > > The key entry in keys-wlan0 should be like
> > > > > KEY='the_entire_key_here'
> > > > > 
> > > > > the key must be exactly as displayed in the AP with no abcd-efgh- type
> > > > > structure. It is case sensitive and must be the exact number of
> > > > > characters (yes, the - is a character). I use copy/paste with my web
> > > > > browser interface to the AP to capture it and put it into the
> > > > > configuration file for the adapter.
> > > > > 
> > > > 
> > > > At this point I don't know what to say. I know I'm doing this
> > > > correctly. 
> > > > -My key in my AP's configuration has 26 characters.
> > > 
> > > Then you're using a hex key, not an ASCII one.
> > > 
> > > > -It will only allow me to use upper case.
> > > 
> > > Again, it's hex, not ASCII.
> > > 
> > > > -I've directly copied and pasted the key.
> > > > -FC4's network applet will also only use upper case.
> > > > -entered with 0x in front
> > > > -FC4's network applet correctly updates keys-wlan0.
> > > > -file has KEY=[the key] WITHOUT the 0x
> > > 
> > > That won't work. If you're using a hex key, you MUST have "0x" in
> > > front of it in your keys.
> > > 
> > 
> > If you have the references to tell us where the requirement to use the
> > 0x notation is documented I would appreciate it.
> > 
> > At no time in my experience have I ever needed that notation and James
> > experience that he has listed here at least twice reinforces that. 
> > 
> > Neither iwconfig nor the keys-wlan0 file will work with the 0x notation.
> > 
> > > > -My router id a DLink DI624
> > > > 
> > > > Is there any type of ndiswrapper debugging that can be turned on? 
> > > > I know the key works since I have a windows machine connected using the
> > > > same key. I've also tried changing the key to something else.
> > > > 
> > > > It's works great without encryption, and even though wep kind of sucks,
> > > > it's at least not wide open. Sorry to those of you that are helping but
> > > > getting frustrated. I'm right there with you. 
> > > 
> > > I don't have any issues. A 26-character key is hex. If you want to
> > > use ASCII, you have to tell your DI624 that, and the key will be 13
> > > ASCII characters (and you can use mixed case). Your key on the system
> > > must match (no leading "0x" for ASCII). Oh, and when you change the
> > > key on the DI624, you must reboot it.
> > > 
> > > If you're using hex, then it's 26 HEX characters. The clickbox on the
> > > DI624 for hex keys MUST be set on, and you must restart the DI624. On
> > > the system, and you MUST have the "0x" in front of the key in your key
> > > file.
> > > 
> > > ----------------------------------------------------------------------
> > > - Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
> > > - VitalStream, Inc. http://www.vitalstream.com -
> > > - -
> > > - Brain: The organ with which we think that we think. -
> > > ----------------------------------------------------------------------
> > > 
> > 
-- 
fedora-list mailing list
fedora-list at redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20051107/40017b29/attachment-0001.htm>