[Declude.JunkMail] manual install of 4x
Is there a way to do this without the wizard? Thanks for any info -Nick --- 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.
RE: [Declude.JunkMail] Manual
As I can remember the latest "release" was from 07/23/2003. (yes 6 months ago) Normaly we've downloaded only releas versions because the time between beta-tests and releases was relative short.But after the date above there was only betas and"interims". In the meantime there was a lot of news, discussions, changes and new spam fighting tecniques in this communitiybut none of them found the way to a release or the manual. On the other side spammers hasn't stopped to improve their sending tecniques, and has also begun to actively fight antispam sources (IP blacklists...) Some weeks ago I paid the Declude SA fee, in the hope that soon will going on something. In the last six months I've posted a lot of suggestions, that in part was repeated from other subscribers later. For example: Check ifMAILFROM, EHLO, COUNTRY,... are nearly the same (I'm not sure if already existant tests like HEURISTICS, take care of this) ConfigurableHOLD action to move hold messages into different file system folders. New COPYSMD action to look what's happen nearly under the own hold threeshold, without breaking the delivery of legit messages. This should help us to improve filter settings and avoid FP's Dynamically disabling of ressource intensive tests (like decoding, external tests, large filter files, ...) based on the average cpu usage. This not to run great part only with the half tests. Such a feature will allow us to use much larger and complexer tests (like reg.expressions) then now without having any problem durring peaks. Holding messages between 100 and 120% of the hold weight and re-test them 15 or 30 minutes later on IP blacklists. If positive HOLD, if negative REQUEUE Extra points for certain combinations of positive test results. Optional time-based basic weight: So Mailservers with a clear defined business/free timecan add a slight basic weight between 24 and 06 o clock. At the moment we usethe latestbeta but I stopped going to interims because I fear that then shortly we will have "beta-interims" and so on. SKIPIFWEIGHT, SPF and Co. are interesting new tecniques and I hope they will be shortly available in a release version. I personaly prefer 1+1+1+1+1.+1 then 1+1+1... +5. +7...+2 Paying a SA it's ok. But waiting for a new release for over 6 months it's not so good. Ok it's not so bad as paying the IMail SA and receiving a v8 with nearly no noticeable new functionality. At the moment the only thing that will bring me to v8 is the need of declude's SMTPAUTH whitelisting. Markus From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin BilbeeSent: Friday, January 23, 2004 11:31 PMTo: [EMAIL PROTECTED]Subject: RE: [Declude.JunkMail] Manual I think this is the best idea. This also give the admin that wants to or needs to use the new features/bug fixes can and they understand their functionality. This also gives the admin the ability to decide wether using the beta is worth the hassle of possible bugs in features they are not currently ready to use. but they can understand the new features that are in the beta with out spending valuable time trolling the archives for possible outdate information on the beta features. Scott how does this suggestion sound? A seperate manpage just for the beta features Who cares if it does not look pretty Kevin Bilbee -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of paulSent: Friday, January 23, 2004 1:20 PMTo: [EMAIL PROTECTED]Subject: Re: [Declude.JunkMail] Manual I'll add my .02 worth to this discussion: What I feel would be the best as a user: 1: Maybe instead of 1.76 betato 1.77 beta, it should've been 1.76 Release, with an update to the manual about the new features of 1.76. 2: Betas should have a page devoted to the new features with a disclaimer "These may not be in the next release - use at your own risk" That way, those that don't use the betas and wait for an actual release get what they want, and beta users get what they want as well. Paul
RE: [Declude.JunkMail] Manual
Markus, Good ideas you have there. If I may comment briefly: Dynamic disabling of resource-intensive tests would be an absolute godsend. Since I have enabled filtering I went from a server that had gobs of extra overhead to one that is taxed and often redlines both processors. A load-smart system would be wonderful. Holding and retesting and possibly requeueing: Same thing. Great idea. No clue whether either is reasonably feasible. Matt Robertson [EMAIL PROTECTED] MSB Designs, Inc. http://mysecretbase.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Seems that there is a lot of chatter on the mailing list right now with tests etc that are not in the manual. I am curious will a new manual be released, or does anyone have any good explanations of some of these tests on their sites? The general rule of thumb is that the manual is updated to include new tests (and other features) whenever a released version comes out. For betas (and interim releases), the features are discussed on the list. Scott, for what it's worth, our Declude maintenance is up for renewal, and one of the questions I got asked was when there would be an updated printed manual that our less-experienced admins could understand. Don't worry, the maintenance will definitely get paid, but now one of my tasks in my free time is to write an admin manual for our staff for Declude's products. Food for thought as some/many of the features of Declude are becoming more regularly available from competitors and even Ipswitch. Jeff --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Scott, for what it's worth, our Declude maintenance is up for renewal, and one of the questions I got asked was when there would be an updated printed manual that our less-experienced admins could understand. Don't worry, the maintenance will definitely get paid, but now one of my tasks in my free time is to write an admin manual for our staff for Declude's products. Thanks for pointing this out. A major overhaul to the manual by a technical writer is something that has been on the to do list for some time. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
RE: [Declude.JunkMail] Manual
I agree that a manual is greatly needed. the value of all the new tests is greatly diminished if there is not adequate documentation. Searching through the archives and reading the discussions my be a good thing to do if you are having trouble understanding the manual but to search the archives to learn the features in the first place is prohibitive for anyone who is performing multiple functions. Once you release your next version I would suggest taking the time to create a comprehensive manual. that will be more value to your customers than new features. If they do not know how to implement the current features then new features are not going to be of any value either. For the people that can spend the time and monitor the group full time and experiment with new features when they are in beta I commend you. But not all of us have the time to do that. WE NEED A MANUAL TO QUICKLY AND EFFICITENTLY IMPLEMENT DECLUDES FEATURES. If you document the usage of the new features while you are creating them you would save yourself and your customers a lot of time. Make the documentation part of your development cycle If you hire a technical writer they are going to require it, so start it now, make the usage notes available, it will save us all time and aggravation. Kevin Bilbee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of R. Scott Perry Sent: Friday, January 23, 2004 7:07 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Manual Scott, for what it's worth, our Declude maintenance is up for renewal, and one of the questions I got asked was when there would be an updated printed manual that our less-experienced admins could understand. Don't worry, the maintenance will definitely get paid, but now one of my tasks in my free time is to write an admin manual for our staff for Declude's products. Thanks for pointing this out. A major overhaul to the manual by a technical writer is something that has been on the to do list for some time. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
I agreebetter documentation...please! - Original Message - From: Kevin Bilbee [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 23, 2004 11:06 AM Subject: RE: [Declude.JunkMail] Manual I agree that a manual is greatly needed. the value of all the new tests is greatly diminished if there is not adequate documentation. Searching through the archives and reading the discussions my be a good thing to do if you are having trouble understanding the manual but to search the archives to learn the features in the first place is prohibitive for anyone who is performing multiple functions. Once you release your next version I would suggest taking the time to create a comprehensive manual. that will be more value to your customers than new features. If they do not know how to implement the current features then new features are not going to be of any value either. For the people that can spend the time and monitor the group full time and experiment with new features when they are in beta I commend you. But not all of us have the time to do that. WE NEED A MANUAL TO QUICKLY AND EFFICITENTLY IMPLEMENT DECLUDES FEATURES. If you document the usage of the new features while you are creating them you would save yourself and your customers a lot of time. Make the documentation part of your development cycle If you hire a technical writer they are going to require it, so start it now, make the usage notes available, it will save us all time and aggravation. Kevin Bilbee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of R. Scott Perry Sent: Friday, January 23, 2004 7:07 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Manual Scott, for what it's worth, our Declude maintenance is up for renewal, and one of the questions I got asked was when there would be an updated printed manual that our less-experienced admins could understand. Don't worry, the maintenance will definitely get paid, but now one of my tasks in my free time is to write an admin manual for our staff for Declude's products. Thanks for pointing this out. A major overhaul to the manual by a technical writer is something that has been on the to do list for some time. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by The Calsoft Anti-Virus Scanner] --- [This E-mail was scanned for viruses by The Calsoft Anti-Virus Scanner] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
I have not renewed my Junkmail SA due to the lack of an updated manual. If Scott would spend the same amount of time updating the manul as he does explaining to the list how features work, the manual would be current. Monitoring and researching list archives is fine for free or diy software but for a paid product with stable features it's unacceptable. Mike --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
I have not renewed my Junkmail SA due to the lack of an updated manual. If Scott would spend the same amount of time updating the manul as he does explaining to the list how features work, the manual would be current. Monitoring and researching list archives is fine for free or diy software but for a paid product with stable features it's unacceptable. There seem to be two main issues with the manual. [1] It needs an overhaul by a technical writer. [2] It does not include all the features that are available in the latest beta, and #1 is something that has been an issue for some time. We actually did look for a technical writer a while back, but there was a snag that prevented it from being completed. We are definitely planning on addressing this. As far as #2 goes, unfortunately, if we add beta features to the manual, there are several problems. First, customers are going to get frustrated that they cannot use features shown in the manual (which would cost us more for support, too). Second, we would have to make many changes to the manual as beta features are altered. Third, I'm sure that if we were to add beta features to the manual, a lot of people would then expect them for interim releases. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Keep it up guys and you'll be forced to wait for a full release to get some of these new features that add such extreme functionality to this product. If you don't like the way Scott does this, only use the latest full release with features covered in the manual. My $.02.N. Mathews[EMAIL PROTECTED] wrote: -To: [EMAIL PROTECTED]From: "Mike K" [EMAIL PROTECTED]Sent by: [EMAIL PROTECTED]Date: 01/23/2004 02:50PMSubject: Re: [Declude.JunkMail] ManualI have not renewed my Junkmail SA due to the lack of an updated manual.If Scott would spend the same amount of time updating the manul as he doesexplaining to the list how features work, the manual would be current.Monitoring and researching list archives is fine for free or diy softwarebut for a paid product with stable features it's unacceptable.Mike---[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]---This E-mail came from the Declude.JunkMail mailing list. Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail". The archives can be foundat http://www.mail-archive.com.--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Scott: Your abilities as a writer are fine. I have seem many of your explanations on use of features and for most I think they would suffice. They just need to be put in the online manual at the same time you post a message to the list. I agree that beta features should not be in the main manual but could be listed in a separate change.log file or in a beta/interim release file. Mike - Original Message - From: R. Scott Perry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 23, 2004 3:02 PM Subject: Re: [Declude.JunkMail] Manual I have not renewed my Junkmail SA due to the lack of an updated manual. If Scott would spend the same amount of time updating the manul as he does explaining to the list how features work, the manual would be current. Monitoring and researching list archives is fine for free or diy software but for a paid product with stable features it's unacceptable. There seem to be two main issues with the manual. [1] It needs an overhaul by a technical writer. [2] It does not include all the features that are available in the latest beta, and #1 is something that has been an issue for some time. We actually did look for a technical writer a while back, but there was a snag that prevented it from being completed. We are definitely planning on addressing this. As far as #2 goes, unfortunately, if we add beta features to the manual, there are several problems. First, customers are going to get frustrated that they cannot use features shown in the manual (which would cost us more for support, too). Second, we would have to make many changes to the manual as beta features are altered. Third, I'm sure that if we were to add beta features to the manual, a lot of people would then expect them for interim releases. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
DITTO! The manual is completely updated right now, unless you have volunteered yourself for the beta program. :-) -- --- Matt Robertson, [EMAIL PROTECTED] MSB Designs, Inc. http://mysecretbase.com --- -- --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
At 03:36 PM 1/23/2004, Mike K wrote: Scott: Your abilities as a writer are fine. I have seem many of your explanations on use of features and for most I think they would suffice. They just need to be put in the online manual at the same time you post a message to the list. I agree that beta features should not be in the main manual but could be listed in a separate change.log file or in a beta/interim release file. I agree with this completely. Just a simple change.log file that has the skeleton for the added test, and maybe just a brief definition, would be more than sufficient. I would imagine that Scott and his boys (and possibly girls.. :) probably keep some type of log like this anyways. But definitely keep this stuff out of the main manual. My .02. -Russ --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
I think the beta/interim features debate has been done recently, however there are two different things that this effects, first, more info about what these things do, and eventually converging these things into the manual (they're not all there in final release format). Second, and more importantly, bug fixes need to be announced. I've spent time researching things, trying to document them appropriately in order to not waste anyone's time, only to find that the issue was fixed in a more recent interim release. For those that have issues with crashes and other serious matters, the announcement of such things is critical and should be done proactively. I will side with Scott about not announcing new interim functionality outside of this list until it is in final release format because such things always cause a lot of questions and that's a bit counterproductive, but after they hit Beta, they should be documented somewhere, and after a release, they should make it to the manual, even the little things that you can only find in the release notes with one line of text. But bug fixes of any sort should be announced, maybe to an announcement list for those of us that want to sign up. Since I monitor this list closely, I'm very much ahead of the curve, though not completely, and for those that don't read every message here, they lose out on a lot of things. Matt Mike K wrote: Scott: Your abilities as a writer are fine. I have seem many of your explanations on use of features and for most I think they would suffice. They just need to be put in the online manual at the same time you post a message to the list. I agree that beta features should not be in the main manual but could be listed in a separate change.log file or in a beta/interim release file. Mike - Original Message - From: "R. Scott Perry" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 23, 2004 3:02 PM Subject: Re: [Declude.JunkMail] Manual I have not renewed my Junkmail SA due to the lack of an updated manual. If Scott would spend the same amount of time updating the manul as he does explaining to the list how features work, the manual would be current. Monitoring and researching list archives is fine for free or diy software but for a paid product with stable features it's unacceptable. There seem to be two main issues with the manual. [1] It needs an overhaul by a technical writer. [2] It does not include all the features that are available in the latest beta, and #1 is something that has been an issue for some time. We actually did look for a technical writer a while back, but there was a snag that prevented it from being completed. We are definitely planning on addressing this. As far as #2 goes, unfortunately, if we add beta features to the manual, there are several problems. First, customers are going to get frustrated that they cannot use features shown in the manual (which would cost us more for support, too). Second, we would have to make many changes to the manual as beta features are altered. Third, I'm sure that if we were to add beta features to the manual, a lot of people would then expect them for interim releases. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. -- = MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =
Re: [Declude.JunkMail] Manual
Scott, A better manual would be nice. I grumble when I see you changed it and cannot find where *BUT* if creating a new one takes away from your literal instant tech support, advice on OT subjects, I can live with the system. From my perspective isn't fair for folks that want new features daily like me to also ask for a spiffy manual. I feel it has to be one or the other and for that reason no complaints at all on my end. Great job! -Nick Hayer Subject:Re: [Declude.JunkMail] Manual From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Keep it up guys and you'll be forced to wait for a full release to get some of these new features that add such extreme functionality to this product. If you don't like the way Scott does this, only use the latest full release with features covered in the manual. My $.02. N. Mathews [EMAIL PROTECTED] wrote: - To: [EMAIL PROTECTED] From: Mike K [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] Date: 01/23/2004 02:50PM Subject: Re: [Declude.JunkMail] Manual I have not renewed my Junkmail SA due to the lack of an updated manual. If Scott would spend the same amount of time updating the manul as he does explaining to the list how features work, the manual would be current. Monitoring and researching list archives is fine for free or diy software but for a paid product with stable features it's unacceptable. Mike --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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 was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Maybe beta's should be by invitation/request only, and distributed only to that group like a normal beta program? At the same time, bug fixes can be applied to the last release, as well as the most recent beta, or only to the beta's if that's all that is affected? It's a bit more work to maintain two different sets of code in this way, but it keeps the bugs relating to full releases from requiring you to upgrade to a beta interim release. This would also cut down dramatically on the overhead of releasing betas to the general public and having to deal with the potential pitfalls of this (i.e. too much discussion). Matt paul wrote: I'll add my .02 worth to this discussion: What I feel would be the best as a user: 1: Maybe instead of 1.76 betato 1.77 beta, it should've been 1.76 Release, with an update to the manual about the new features of 1.76. 2: Betas should have a page devoted to the new features with a disclaimer "These may not be in the next release - use at your own risk" That way, those that don't use the betas and wait for an actual release get what they want, and beta users get what they want as well. Paul -- = MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =
RE: [Declude.JunkMail] Manual
Title: Message I'm all in favour of the manual being sync'ed with the releases. That's a no-brainer. Beta support handling is a bone of contention, and I'd rather that support maintenance of those featuresnot interfere with the stellar support we already get from Declude. Therefore, I suggest that: 1) Create a new mailing list for Declude.JunkMail.Beta that those who live on the bleeding edge can join. Cross-posting to Declude.JunkMail and Declude.Virus is discouraged. Announcements of features would be done there. 2) As suggested already, simple documentation of new features under testing beprovided, e.g. sample usage and obvious gotchas, rather than the support/beta list getting clogged with people discovering a beta feature and asking how to use it. 3) Tracking what's in the Release and what's in the Beta then makes it irrelevant what's ina given Interim. Declude could then e-mail out a "new release announcement" to the customer base (that'd be us). A lot of traffic in this support list is based on administrators who are quite far behind but are seeing "new" tests discussed and want to get up to speed. 4) Perhaps: prefix the Beta feature names with BETA, e.g. BETAHIDETESTS, BETASPFPASS; the onus is then on we the mail administrators to do search and replace when we implement the Release version...? Valuable or pointless? Strict or customer-abusive?Judgingbythediscussion today,somewould prefer the clarity... but then, I only deal with one global.cfg and one $default$.junkmail so my judgement is limited. Andrew. -Original Message-From: Matt [mailto:[EMAIL PROTECTED] Sent: Friday, January 23, 2004 1:34 PMTo: [EMAIL PROTECTED]Subject: Re: [Declude.JunkMail] ManualMaybe beta's should be by invitation/request only, and distributed only to that group like a normal beta program? At the same time, bug fixes can be applied to the last release, as well as the most recent beta, or only to the beta's if that's all that is affected? It's a bit more work to maintain two different sets of code in this way, but it keeps the bugs relating to full releases from requiring you to upgrade to a beta interim release. This would also cut down dramatically on the overhead of releasing betas to the general public and having to deal with the potential pitfalls of this (i.e. too much discussion).Mattpaul wrote: I'll add my .02 worth to this discussion: What I feel would be the best as a user: 1: Maybe instead of 1.76 betato 1.77 beta, it should've been 1.76 Release, with an update to the manual about the new features of 1.76. 2: Betas should have a page devoted to the new features with a disclaimer "These may not be in the next release - use at your own risk" That way, those that don't use the betas and wait for an actual release get what they want, and beta users get what they want as well. Paul-- = MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =
RE: [Declude.JunkMail] Manual
I think this is the best idea. This also give the admin that wants to or needs to use the new features/bug fixes can and they understand their functionality. This also gives the admin the ability to decide wether using the beta is worth the hassle of possible bugs in features they are not currently ready to use. but they can understand the new features that are in the beta with out spending valuable time trolling the archives for possible outdate information on the beta features. Scott how does this suggestion sound? A seperate manpage just for the beta features Who cares if it does not look pretty Kevin Bilbee -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of paulSent: Friday, January 23, 2004 1:20 PMTo: [EMAIL PROTECTED]Subject: Re: [Declude.JunkMail] Manual I'll add my .02 worth to this discussion: What I feel would be the best as a user: 1: Maybe instead of 1.76 betato 1.77 beta, it should've been 1.76 Release, with an update to the manual about the new features of 1.76. 2: Betas should have a page devoted to the new features with a disclaimer "These may not be in the next release - use at your own risk" That way, those that don't use the betas and wait for an actual release get what they want, and beta users get what they want as well. Paul
RE: [Declude.JunkMail] Manual
Title: Message I agree with this approach. It would separate the BETA users from the curious RELEASE users (who probably should wait for the release). Todd Holt Xidix Technologies, Inc Las Vegas, NV USA www.xidix.com 702.319.4349 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Colbeck, Andrew Sent: Friday, January 23, 2004 2:16 PM To: '[EMAIL PROTECTED]' Subject: RE: [Declude.JunkMail] Manual I'm all in favour of the manual being sync'ed with the releases. That's a no-brainer. Beta support handling is a bone of contention, and I'd rather that support maintenance of those featuresnot interfere with the stellar support we already get from Declude. Therefore, I suggest that: 1) Create a new mailing list for Declude.JunkMail.Beta that those who live on the bleeding edge can join. Cross-posting to Declude.JunkMail and Declude.Virus is discouraged. Announcements of features would be done there. 2) As suggested already, simple documentation of new features under testing beprovided, e.g. sample usage and obvious gotchas, rather than the support/beta list getting clogged with people discovering a beta feature and asking how to use it. 3) Tracking what's in the Release and what's in the Beta then makes it irrelevant what's ina given Interim. Declude could then e-mail out a new release announcement to the customer base (that'd be us). A lot of traffic in this support list is based on administrators who are quite far behind but are seeing new tests discussed and want to get up to speed. 4) Perhaps: prefix the Beta feature names with BETA, e.g. BETAHIDETESTS, BETASPFPASS; the onus is then on we the mail administrators to do search and replace when we implement the Release version...? Valuable or pointless? Strict or customer-abusive?Judgingbythediscussion today,somewould prefer the clarity... but then, I only deal with one global.cfg and one $default$.junkmail so my judgement is limited. Andrew. -Original Message- From: Matt [mailto:[EMAIL PROTECTED] Sent: Friday, January 23, 2004 1:34 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Manual Maybe beta's should be by invitation/request only, and distributed only to that group like a normal beta program? At the same time, bug fixes can be applied to the last release, as well as the most recent beta, or only to the beta's if that's all that is affected? It's a bit more work to maintain two different sets of code in this way, but it keeps the bugs relating to full releases from requiring you to upgrade to a beta interim release. This would also cut down dramatically on the overhead of releasing betas to the general public and having to deal with the potential pitfalls of this (i.e. too much discussion). Matt paul wrote: I'll add my .02 worth to this discussion: What I feel would be the best as a user: 1: Maybe instead of 1.76 betato 1.77 beta, it should've been 1.76 Release, with an update to the manual about the new features of 1.76. 2: Betas should have a page devoted to the new features with a disclaimer These may not be in the next release - use at your own risk That way, those that don't use the betas and wait for an actual release get what they want, and beta users get what they want as well. Paul -- =MailPure custom filters for Declude JunkMail Pro.http://www.mailpure.com/software/=
Re: [Declude.JunkMail] Manual
Scott- I'll cast my vote for this approach. Just a simple beta-only html page on your website. Contents: What's in each interim release, a one-line explanation, and a .config file and/or .junkmail file example would be fine with me. Once we know what's in the release, we can search this list for details. That would have the added benefit of getting the users hooked into earlier-adopters' experiences with each test before they try it on their own. Even niftier, a huge convenience, and no big deal to execute: A link from the test's name to the list archive search page. -d - Original Message - From: Mike K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 23, 2004 3:36 PM Subject: Re: [Declude.JunkMail] Manual Scott: Your abilities as a writer are fine. I have seem many of your explanations on use of features and for most I think they would suffice. They just need to be put in the online manual at the same time you post a message to the list. I agree that beta features should not be in the main manual but could be listed in a separate change.log file or in a beta/interim release file. Mike --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
[Declude.JunkMail] Manual
Scott, I have been away for some time and have been trying to get caught up on the declude list (its the most active list I have). Seems that there is a lot of chatter on the mailing list right now with tests etc that are not in the manual. I am curious will a new manual be released, or does anyone have any good explanations of some of these tests on their sites? Hope someone can help. Darryl Koster --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
Re: [Declude.JunkMail] Manual
Seems that there is a lot of chatter on the mailing list right now with tests etc that are not in the manual. I am curious will a new manual be released, or does anyone have any good explanations of some of these tests on their sites? The general rule of thumb is that the manual is updated to include new tests (and other features) whenever a released version comes out. For betas (and interim releases), the features are discussed on the list. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
RE: [Declude.JunkMail] Manual
How about a new Manual page. The last released version was in early December and there have been a ton of new things added. It is getting harder and harder to search through the archives to find clarification on a feature. That is because there is no new release version yet. As Scott has stated, the manual only gets updated with release versions, as some items in betas never make it or are changed before release. John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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.
RE: [Declude.JunkMail] Manual
www.declude.com/junkmail/manual.htm Todd -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Douglas Hardison Sent: Monday, April 01, 2002 11:14 AM To: [EMAIL PROTECTED] Subject: [Declude.JunkMail] Manual Where might I find a copy of the JunkMail manual. I'm interested in reading more about the weighting system. Thanks Douglas Hardison Bits, Bytes and Pieces Internet Service 3332A-3 Airport Boulevard Wilson, NC 27896 Voice: 252-234-7040 Fax: 252-291-2119 [EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Manual
Where might I find a copy of the JunkMail manual. I'm interested in reading more about the weighting system. You can find it at http://www.declude.com/junkmail/manual.htm . If you have any questions about it, please let me know. Thanks. -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
[Declude.JunkMail] Manual
Scott Just noticed that the manual.htm for junkmail shows simply rename the \IMail\Declude\junkmail.cfg file to junkmail.bak. in the Emergency Uninstall section. David Stavert Netraprise Systems, Inc. 79 13th Ave NE, Suite 112 Minneapolis, MN 55413 612.317.9065 612.317.9062 FAX --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
Re: [Declude.JunkMail] Manual
Just noticed that the manual.htm for junkmail shows simply rename the \IMail\Declude\junkmail.cfg file to junkmail.bak. in the Emergency Uninstall section. Thanks for pointing that out, it's been fixed. [for those that didn't notice, it should be global.cfg and global.bak] -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- 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. You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
