[NOTE: Your mail server [208.247.235.30] is missing a reverse DNS entry. All Internet hosts are required to have a reverse DNS entry. The missing reverse DNS entry will cause your mail to be treated as spam on some servers, such as AOL.]
BRAVO!!!! That is what I am talking about. Tony, we are doing the same with the .asp app. perhaps we should compare notes. rusty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Gray - Network Administrator Sent: Monday, April 01, 2002 2:41 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] Blacklist/Whitelist ### My submission to the suggestion box :-) ### I just recently heard about how AOL users can blacklist all but specified recipients. I happened to learn about it by sending an email to my uncle (who uses it and forgot to add me to the list - at least he says he forgot) I (and a small sampling of our users that I've run it by) think that's a GREAT idea. I've been working on an .asp app to allow users to modify their own per/user junkmail/virus settings, it would be very easy to add this feature if Declude supported it (i.e. self administration by the end user would be a must) It would allow those who utilized it to cut out 99.9% of spam, unless someone was lucky enough to spoof an address they had in their 'allowed senders' list. What kind of spam detection can claim that type of percent? Along with this feature should be it's own special 'bounce' email (i.e. we're sorry, but the recipient has chosen not to receive email from %SENDER%, if you think this is in error contact postmaster@, etc. etc.) As for an easy way to manage it, possibly a subfolder (\imail\declude\allowed_senders), a seperate file for each user (user_domain_com.allowed), if a file doesn't exist for a user, then mail is allowed normally via global junkmail/virus/hijack rules. If file exists, the email addresses contained in the file are the ONLY allowed senders, anything else is bounced back to sender (or quietly deleted based on per user settings). The only negative I could imagine, is that the contents of the ..\allowed_senders folder would probably get pretty huge after people adopted the cool, new feature, and declude parsing this folder all the time could cause a decent performance hit(?) Thanks for listening, Tony Gray Intouch Communications, Inc. >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry >Sent: Monday, April 01, 2002 2:08 PM >To: [EMAIL PROTECTED] >Subject: Re: [Declude.JunkMail] Blacklist/Whitelist > > > >>Is it possible to create a sender blacklist that blocks >everything? As well >>as a sender whitelist that allows exceptions to the blacklist. > >I believe the sender blacklists require a minimum of 2 characters >per line, >but you try something like this: > > @a > @b > ... > @z > @0 > ... > @9 > >Having all 26 characters and 10 digits should block all E-mail. The >WHITELIST entries would then override the blacklist. > >>So I guess I am looking for a WHITELIST file (looks like we are currently >>limited to 200 entries in the global.cfg), and an "*" in the >BLACKLIST file. >>This would move it to a per user/domain check instead of a global as well. > >And that is where it would be difficult with the current release. The >WHITELIST entries are global (and the blacklist entries are effectively >global, too), so it wouldn't be possible for individual users to >have their >own whitelist entries. > >>I really feel that this would be the biggest step we could take to stop >>spammers cold. AOL offers "trusted" accounts (where only mail that you >>specify makes it to your mailbox), this would give all of us that >>capability. > >We are looking into a "confirmation" action that would require the sender >of the E-mail to confirm that they sent the E-mail, which would also cut >down significantly on spam (probably 99% or so), while being slightly less >inconvenient. That won't definitely be added, but if enough people think >it would be useful, we may. > -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 . --- [This E-mail was scanned for viruses by http://www.intouchmi.com] --- [This E-mail was scanned for viruses by http://www.intouchmi.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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
