| ArGoStuff User to User Support Forums |
Spam & Virus Control - DNSBLs or Mail Filters Last Post 23 Nov 2009 01:31 PM by Steve Topilnycky. 3 Replies. | Sort: |
|  Prev Next | You are not authorized to post a reply. | |
H2o
New Member
Posts:16
 | | 20 Nov 2009 03:50 PM |
| What metheds are users finding most effective for Spam & Virus Control and why? DNSBLs , Mail Filters, IP filtering I understand they all handle certain aspects a little differently,. but what are some of the more obvious defaults tools a .NET server admin or user should utilize? Which ones seem not worth the effort or cause more problems than good? | | |
|
|
Steve Topilnycky
Forum Administrator
Veteran Member
Posts:1278
| | 20 Nov 2009 06:35 PM |
| It all boils down to an admins preference. I use eWall as a front end. From within eWall, I used SPF, reject invalid sender domains, reject invalid recipients, SURBL, DNSBL, reject messages that attempt to relay through my server, Reverse DNS check (A user must have reverse DNS to send mail to my server), Paranoid for rating spam probability, and AVG Anti virus to scan all messages for viruses. A snapshot from last year of my system stats are available at http://www.topcatcomputing.com/Arti...tsv1.aspx. The .NET server does have some of what I mentioned above, however the eWall option gives me much more flexibility on doing just simple filtering. Again it boils down to the admins preference and needs. I am sure other have a totally different approach to this. | | - - - - - - -
Regards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com/ | |
| H2o
New Member
Posts:16
| | 23 Nov 2009 12:03 PM |
| Thanks for the info. I will check into e-wall to see what it offers. Although we have been running Pro for 6+years with 30+ domains, with 200 total e-mail addresses, for spam, we have been using only what pro offered. The settings we used over the years changed and morphed as spam increased, DNSBLs, reverse DNS Lookup, etc,.. it seemed that for one reason or another one or more of the tools we used,.. would cause issues with one or more clients/users and or other ISPs. Basically too tight of settings and e-mails don't get through,.. and too loose and too much spam. A fine balance. Seems we have been constantly tightening and loosening settings. It has never seemed as the right approach to jump when a client complains and change settings. I like tight settings,.. but users also like getting their e-mails with no spam. Funny how that works. Clients help pay the bills. We were looking for guidance more experienced than ourselves as to what is the recommended good starting point and good practice. Perhaps a discussion as to what tools are preferred and why and which are not preferred and why. Basically who is using what. Your info and screenshot were helpful. | | | |
| Steve Topilnycky
Forum Administrator
Veteran Member
Posts:1278
| | 23 Nov 2009 01:31 PM |
| I have tried various approaches with mixed results. Essentially, SPF, reject invalid sender domains, reject invalid recipients, SURBL, DNSBL, reject messages that attempt to relay through my server, Reverse DNS check all get rejected. Everything else gets tagged with a spam probability and I let the end user decide. I am also a very small shop with 6 domains and a handful of users. I also utilize POP3 instead of IMAP, so I can't just put messages into a spam folder. The end user needs to either set up a rule on their client or manually sift through the tagged messages (The subject is appended with a Spam Probability Message). | | - - - - - - -
Regards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com/ | |
|
| You are not authorized to post a reply. |
|
|
|  | | Mail Server v1.0.8.3 |
- Added support of STARTTLS (STLS) command for SMTP, POP3, IMAP, and SMTP relay and delivery, which will
allow secure, fully encrypted connections, when possible;
| | 11/6/2011 1:10:34 PM |
| Mail Server v1.0.8.2 |
- Optimized delivery speed. In earlier versions each "tick" which was checking whether messages were
in the outbox queue, was picking up only one message at a time. Now it will attempt to pick MaximumAllowedThreads-ActiveDelivery threads
messages, which should considerably increase deliver speed;
- Optimized SEARCH and STATUS IMAP commands. They appear to be used very extensively by Android, and (not that extensively, but still) by
iPhone. Now users who use mobile phones to access their IMAP accounts will see considerable improvement;
- Optimized STORE IMAP command. Before storing of IMAP flags was occuring one message at a time, which seemed to be fine
with SQL server, but proved to be slow for SQLite... Now it happens with single SQL call.
| | 10/8/2011 7:59:35 PM |
| ArGoSoft Mail Server v1.0.8.1 | -
Fixed a bug: when using IMAP via Firefox with "When I delete a message, move it
to Trash folder" option, marking messages in the trash folder was causing high CPU usage,
and was taking some time, making the server pretty much non-responsive. The problem was
happening only when using SQLite.
| | 6/6/2011 9:33:36 PM |
| ArGoSoft Mail Server v1.0.8.0 |
- Fixed a problem with web interface - was showing only first page of messages, and would not
switch to other pages; In order to fix the web interface, mail server itself has to be updated;
- When installint initially, was still using SQLite, even when SQL was requested;
- There was a problem with switching from SQLite database engine to SQL server database engine:
the SQL database was not being created;
| | 5/23/2011 5:53:55 PM |
| ArGoSoft Mail Server .NET v1.0.7.9 |
- The server no longer requires Microsoft SQL Server. If SQL server is not found, it will use
SQLite engine, which does not require separate installation. If SQL server is found, then user will be
prompted whether he wants to use it;
- Made other improvements, such as, now mailbox rebuild indexes orphaned records, rather then deleting them,
also added an opotion to increment UIDL validity of folder (both on the Mailbox viewer box);
- Made minor improvements on web interface;
| | 4/26/2011 9:47:25 PM |
| |
|  |  | |  |
|