CSAV for Exchange - Virus Alert

2005-10-20 Thread Mail Administrator
The message "Returned mail: see transcript for details" you sent to ""[EMAIL PROTECTED]" <[EMAIL PROTECTED]>" had the file attachment "file.pif" which was infected with the "Infection: W32/[EMAIL PROTECTED] (exact)" virus. The file attachment was deleted from the message. -- To UNSUBSCRIBE,

Re: ifenslave hacks and policy, plus: Re: Needing explanations about BTS usage for wishlist

2005-10-20 Thread Justin Pryzby
Hello DevRef team, Could you make it more clear what the canonical, best-practice procedure should be for suspected MIA developers? -- Clear skies, Justin On Thu, Oct 20, 2005 at 04:22:34PM +0100, Adam D. Barratt wrote: > On Wednesday, October 19, 2005 7:22 PM, Justin Pryzby > <[EMAIL PROTECTE

Re: ifenslave hacks and policy, plus: Re: Needing explanations about BTS usage for wishlist

2005-10-20 Thread Adam D. Barratt
On Wednesday, October 19, 2005 7:22 PM, Justin Pryzby <[EMAIL PROTECTED]> wrote: [...] > You might contact the maintainer, and if you don't receive a response, > email [EMAIL PROTECTED] and ask "is this person mia" (and Cc: them > in that message). The recommended method is to mail [EMAIL PROTECTE

Re: ifupdown-bonding package

2005-10-20 Thread Jerome Martin
Hmmm. How about filing wishlist bug report to ifupdown and provide your script as a patch which falls into one of the example in /usr/share/doc/examples/ . Or create a patch to ifupdown itself to support bondX.Y notation in interfaces and file bug report. This may be enen better. What I'll