|
Group: netwin.surgemail
Subject: RE: [SurgeMail List] Re: Surgemail stopped sending daily logs (Update)
Date: Wed, 27 Jan 2010 01:26:33 -0500
> In addition, another neat feature has been added > to Surgemail 41d in Sep 2009 that acts like a > temporary RBL. If a spammer sends an email to a > SpamTrap address, the spammer's IP address is > immediately blocked for X minutes. (configurable). > This prevents spammers from delivering to multiple > accounts... and DRASTICALLY reduces the spam load > of other accounts. > > I will provide more details in a separate email - > if anyone is interested. Yes please. Cheers, -Slim -- Jeroen C. "Slim" van Gelderen ________________________________________ From: Webmaster@1usa.com [mailto:Webmaster@1usa.com] Sent: Tuesday, January 26, 2010 22:45 To: surgemail-list@netwinsite.com Subject: Re: [SurgeMail List] Re: Surgemail stopped sending daily logs (Update) Welcome to Surgemail Version 4q+ You are probably upgrading from Surgemail version 3-something, right? Please review the Surgemail Change History at http://netwinsite.com/surgeweb/help/updates.htm to see all that has changed since Version 3. Although I cannot speak on Netwin's behalf, I can provide these details: /surgemail/status.eml was worked on in Aug-Sept 2006, and revisited in Jun 2007. /surgemail/status-html was created in surgemail version 4q between May and June 2009, then became part of the mainstream code around Aug 2009. The purpose of the coding is to allow POP3 and IMAP customers to manage their Friends-Pending emails as well as their In-Box from Client software -- without having to log into Webmail. With a few tweaks, even the most 'computer-challenged' customer can understand and manage their mailbox protections... namely the Friends system. If a user chooses to receive spam along with good emails in their In-Box, the best Friends setting is "Apply friends list but don't block anything or request confirmation." For tighter control, "Request confirmation from unknown addresses." Surgemail will build the list of Authorized Senders in the background, which can become a Backup Address Book for the customer should the customer's computer crash and not recover their .adb file Rules in Mfilter.Rul still apply to all accounts on the server... and Admins can still redirect-reject based on these server-wide rules. In my opinion, the Challenge message should be sent out to ALL new senders. The purpose is to verify that the sender's address exists. The pending email is deleted if the sender's address was a fake... which further reduces the number of spams in the customer's account. Our Friends-Pending message says "Did you send me an email? If you did, click here ||link||" and the Confirm_by-Webpage is turned on, which requires the first-time sender to type in 4 numbers on the web page. On the other hand, if the customer sends an email to joe@Yayhoo first, then joe's email address is also added to the list of Friends, and if joe replies, joe's reply goes directly to the In-box. To implement the Friends system on accounts that have been live for awhile, the best setting is "Request confirmation if smite score is:" 40 or some number fairly high. This will begin to accumulate the email addresses based on outgoing emails without interfering too much with incoming emails. After the customer has been around for a few months, then the setting can be change to "Request confirmation from unknown addresses." -- which will keep the spams from all the 'free' email services out of the In-Box. At this point, the customer will see only legit emails in their In-Box. Our customers here get NO spams in their In-Boxes. If you would like to see the coding & verbage changes we've done on the status-html.eml, please email off-list. Testimonial: We have an insurance company as a client who were receiving 300 spams per day in each account with their old ISP. When setting up the accounts here, the same email addresses were used - because all of their business contacts had the email addresses. They saw an immediate improvement. They had a few questions in the first 60 days about the Friends system, and have loved getting no spams in their mailboxes since. We have since changed the account names from john@ to johnP@... and added the old email address as an Alias. Thus, their outbound emails update the other person's Address Book with the new email address over time. After 2 years, the alias to the old email address will be removed, which will reduce the spam load. ==== In addition, another neat feature has been added to Surgemail 41d in Sep 2009 that acts like a temporary RBL. If a spammer sends an email to a SpamTrap address, the spammer's IP address is immediately blocked for X minutes. (configurable). This prevents spammers from delivering to multiple accounts... and DRASTICALLY reduces the spam load of other accounts. I will provide more details in a separate email - if anyone is interested. BarryZ 1USA.Com ----- Original Message ----- From: "Surgemail Support (Marijn)" <surgemail-support@netwinsite.com> To: <surgemail-list@netwinsite.com> Sent: Tuesday, January 26, 2010 3:16 PM Subject: Re: [SurgeMail List] Re: Surgemail stopped sending daily logs (Update) > > Hi > > I gather some of you have been struggling with the "improvements" to > the spam reporting / daily status log reporting email... > > For starters I want to apologise for possible annoyance and > inconvenience. It was not intended as a "major change of behaviour", > but as significantly improved functionality from "a status email" > whose usefulness was dubious due to its lack of organisation and > formatting, to a very useful feature for handling spam from your inbox > in your mail client without needing to login to any of surgemail's web > interfaces. > > By having surgemail start to use this automatically everyone was > intended to start receiving the benefits of this even if the admin did > not explicitly go and enable settings for html status emails... for > some of you it has not worked that way. > > I agree that the complete non sending of the status email if only the > spam held folder is in use is not the ideal behaviour and could have > been better managed on our part. Originally this was identified as not > affecting a significant number of users which is why it has not > received more attention sooner. > > Anyway, this page should explain most of the situation, offers several > remedies, and shows you the features of the html status email. > http://netwinsite.com/surgeweb/help/spam_config.htm > > I'll also go and have a look at the source code to see what I can do > to improve the "non sending" issue if you are using the "Spam held" > folder only. > > Let me know if you have further input and suggestions. > > > Marijn