Re: [Declude.JunkMail] New and old locations of Q files while being processed

[Matt]

Sorry.  The "Q" reference was just a generic reference to the file that contains the extra information from the SMTP session.  This is just the IMail in me speaking. Matt Gary Steiner wrote: I'm confused by the SmarterMail reference. I thought the Q naming convention was unique to IMail. I'm using SmarterMail 2.6, and the only names I've seen have been *.EML and *.HDR files. Did an older version of SmarterMail use Q files? The only renaming I've seen is a switch between uppercase and lowercase (EML to eml) and then an "X" prefix added to the file name when Declude is done processing it. -------- Original Message -------- From: Matt <[EMAIL PROTECTED]> Sent: Monday, October 03, 2005 10:02 PM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] New and old locations of Q files while being processed I have a question for the folks at Declude concerning the locations, naming conventions and locks if any that are used for the Q files while being processed. I understand that in Declude 2.x and lower Declude will rename the Q file by replacing the leading "Q" with an underscore, and the extension has it's first letter replaced with a tilde. Am I correct in assuming that when 2.x and below moves a Q file into Overflow, that it repeats this same behavior in that directory? Then for 3.x versions, it seems to have been reported that the Q files are moved no matter what. I was wondering if the renaming conventions are still the same, or what they would be if they are different. I was also wondering what directory the Q file is located in when it is being scanned. I also have a request for Declude. Please bear in mind that the Q file is the only reliable way for an external application to get sender and recipient information, and consistency across versions, even platforms (SmarterMail and IMail), including renaming conventions and directory structure, is important for those of us that wish to program external applications that make use of this information. While there is a variable for %MAILFROM% and %ALLRECIPS% that can be passed to external applications, command line applications don't allow the < and > characters (the environment will exit with an immediate error unless quoted, and Declude doesn't support that) and there are character limitations that %ALLRECIPS% can run into. So please consider the need to standardize and keep consistency when choosing locations and conventions such as these. Thanks, Matt --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.