Hello Roberto,

I see in the thread about the new features about the upcoming version  http://www.logsat.com/spamfilter/forums/forum_posts.asp?TID= /5788&PN=1

so here are some (lots) of my requests.

1. LDAP lookup for allowed Email addresses. Currently I have to create this file on the central server in different formats and push to several servers. Since you already have the LDAP code in, I guess this might be easy to implement.

2. Destination routing per domain or per email address.
Again this can be done via LDAP query or a database.
Currently I have the SF-incoming->Postfix (for LDAP lookup and Mail routing to internal mailbox server) -> SF-outgoing -> Outgoing server.
If I can do the mail routing on the SF box, I can get rid of the mail server in between and put more nodes running SF.
Example mail routing. (a mix of the two docs should do it.)
http://ispman.sourceforge.net/mail-routing.php
http://ispman.sourceforge.net/mail-multiplexing.php


3. Ability to assign some rules for the SMTP Auth'ed users.
Your design for the SMTP auth assumes the role of outgoing server and white-list everything coming from a authenticated user.
In an Enterprise that may be the case but at the ISPs, the authenticated users can be as bad as the un-authenticated connections.
Example: Worm on your computer using your outlook settings to send spam as u, using your credentials via your ISP.

This makes more work for our Outgoing SF (3rd in the row) to get rid of this SPAM.

4. This one should make you __MAD__.
  A scripting engine? or a plugin possibility where the administrators can add / change some functionality? For example if you provide a hook to the logging feature, I am sure someone will write a plugin to log to syslog. Example: see qpsmtpd (smtpd.develooper.com)

5. Ability to run as a helper application to other mail server.
   For example (postfix and amavisd-new). Ok, I take this one back.

6. Transport over LMTP to internal mail servers. Ok.. this one is too much too.

I will bug you with more feature requests as I get more ideas.

Hi Atif,

#1 has been added to the wishlist. It won't quite make it right away in the next release, but it will be considered later.

For #2, that can already be done! Please see this section in the readme.html file:


Local Domains - SpamFilter will only deliver email to the domains listed here. Wildcards (* and ?, same rules as DOS wildcards) are allowed. You can also use Regular Expressions (RegEx). If the domain in the  RCPT TO email address is listed as a local domain, then the recipient is accepted. This is done to prevent spammers to use SpamFilter to relay email to third party email addresses/servers. It is very important to add your own domains to the local domain list. If not, you will not be able to receive email. If you need to have any domain listed here forward its destination email to a different server than the default destination server, you can specify so here. You can override the default destination server by appending the forwarding mail server and port to any domain in this list. The syntax should be as follows:

DomainName:DestinationServer:DestinationPort - ex. logsat.com:mail.netwide.net:25


For #3, can you be more specific on what kind of options you'd like to see?

#4, 5, and 6 instead are pretty unlikely to be implemented any time soon, sorry!

Could also use this one !

 

###

for example
sales@logsat.com should go to roberto_franceschetti@192.168.100.29
info@logsat.com should go to some_other_mailbox@192.168.100.30
*@logsat.com should to some_other_mailbox@192.168.100.30
###

 

/Web123