Virus in Ihrer Nachricht / Virus in your mail
V I R E N A L A R M In Ihrer Nachricht an: - [EMAIL PROTECTED] ist ein Virenbefall entdeckt worden. Dabei handelt es sich um: 'W32/Sobig-F' Die Nachricht wurde nicht zugestellt. Bitte beachten Sie, daß Viren bei der Verbreitung häufig den Absender fälschen, so daß die Nachricht nicht von Ihrem Rechner stammen muß. Den wahren Urheber der Nachricht erkennen Sie an dem beigefügten Header (http://www.fernuni-hagen.de/URZ/Wenzel/Mail-FAQ.html#Header). Auch wenn diese Nachricht häufig nicht den tatsächlichen Absender erreicht, ist die Information an die Absenderadresse aus rechtlichen Gründen erforderlich. Wenn die Nachricht nicht von Ihrem Rechner stammt, ist diese Nachricht gegenstandslos; anderenfalls untersuchen Sie bitte Ihren Rechner auf Virenbefall oder wenden Sie sich an Ihren Administrator. Zu Ihrer Information fügen wir den Briefkopf Ihrer Nachricht bei: --- Anfang des Briefkopfes -- Received: from pd9e58467.dip.t-dialin.net ([217.229.132.103] helo=AP4) by oak.FernUni-Hagen.de with esmtp (Exim 4.04) id 19wMlO-0005AZ-00 for [EMAIL PROTECTED]; Mon, 08 Sep 2003 16:13:07 +0200 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Your details Date: Mon, 8 Sep 2003 16:16:03 +0200 X-MailScanner: Found to be clean Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=_NextPart_000_01D95D79 Message-Id: [EMAIL PROTECTED] X-Virus-Scanned: by AMaViS (http://amavis.org/) Ende des Briefkopfes --- V I R U S A L E R T Our viruschecker found the 'W32/Sobig-F' virus(es) in your email to the following recipient(s): - [EMAIL PROTECTED] Please check your system for viruses, or ask your system administrator to do so. For your reference, here are the headers from your email: - BEGIN HEADERS - Received: from pd9e58467.dip.t-dialin.net ([217.229.132.103] helo=AP4) by oak.FernUni-Hagen.de with esmtp (Exim 4.04) id 19wMlO-0005AZ-00 for [EMAIL PROTECTED]; Mon, 08 Sep 2003 16:13:07 +0200 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Your details Date: Mon, 8 Sep 2003 16:16:03 +0200 X-MailScanner: Found to be clean Importance: Normal X-Mailer: Microsoft Outlook Express 6.00.2600. X-MSMail-Priority: Normal X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=_NextPart_000_01D95D79 Message-Id: [EMAIL PROTECTED] X-Virus-Scanned: by AMaViS (http://amavis.org/) -- END HEADERS -- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Patching?
On Sun, Sep 07, 2003 at 03:34:32PM -0700, jw schultz wrote: I'm thinking the protocol version MIN would be good to add, it might not help for this cycle but would in future. This also ties in with something i suggested earlier for the sake of testing, a --protocol option to explicitly force a downgrade. I agree with both ideas, and have worked up a patch (though the new option is, as yet, undocumented): http://www.blorf.net/rsync-protocol.patch I'll go ahead and check this in soon, since I can't see any downside to doing this. Note that this change should help out with this cycle, since this change allows someone to just bump down the PROTOCOL_VERSION in rsync.h and the code will properly skip all the new-protocol extensions. It will also give us a work-around for talking to a pre-release server that someone might have left lying around, unsupported. E.g., if the remote system says it supports protocol 27, but it's a CVS version that doesn't really support all of 27, you can use the new --protocol=26 option to force the two to talk using an earlier protocol version. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: doing an md5sum rsync?
On 7 Sep 2003 Marc MERLIN [EMAIL PROTECTED] wrote: I don't know if this has been requested before, but I would really like for rsync to compute an md5sum for each file at the source and destination (with a flag turned off by default of course), and it would realize that I renamed files at the source by noticing a matching md5sum between different filenames It would then rename the destination instead of deleting it and resending the entire source, just because the filename changed. This would also take care of me moving files between directory trees, and again do a mv instead of a delete/resend (if I rsync the root of all that of course) Or is this possible already? This is not possible yet. It is on my wishlist for a future program. Of course remotely detecting files that have moved between directories might mean having the server hash every file on the filesystem. So it might be quite expensive... -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Add a feature : disk and partition cloning
On 2 Sep 2003 francis.mit [EMAIL PROTECTED] wrote: Bonjour, Today, I use rsync for updating some 40 Debian/Linux box, rsync is great. So, now, I'll need to update a whole disk or partition (NTFS) with an image or an other disk or part. (case multiboot system), can'I hope rsync do this task in some day ? I agree that it would be a cool feature. It's unlikely that the existing codebase would be extended for it, but something like rdiff might support it eventually. In the meantime, just dd across ssh. rsync algorithm would be great for this task, isn't-it ? Not directly; the basic rsync algorithm cannot update in place. You might adapt it to do so though. I'don't mind how amount of works this feature need, but some folks are interresting in ? You don't mind how much work other people do for you? How gracious. Or were you volunteering to write it? If so, adding in-place updates to rdiff would be a good place to start. -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
