This is a discussion on [AMaViS-user] SQL lookups : Which amavisd-new version to use additional fields within the Amavis User forums, part of the Anti-Spam and Anti-Virus Related Forums category; Hello, I'm building a mail server with antispam and antivirus capabilities=20 and one of the requirements is that ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hello,
I'm building a mail server with antispam and antivirus capabilities=20 and one of the requirements is that each user should be able to choose=20 if he/she wants to enable spam and/or virus checking as well as his/her=20 antispam settings. We have people in-house which is going to develop a=20 nice end-user interface which would allow the users to choose what they=20 want easily, that's not a problem. However, I need to provide a way to let the end-user interface to=20 store values on a database representing user's choices. I have already=20 did something like this before using amavisd-new and SQL lookups, but=20 now I need to provide users (through the end-user interface) the ability=20 to set more fields in the database than I provided before. I have been searching and I found some new supported (optional)=20 fields given as examples in the README.lookups file in the=20 amavisd-new-2.2.1 source tree. That's exactly what I want, but I'm=20 currently using amavisd-new-20030616p10 in my test server and, for=20 various (non-technical) reasons I would like to stick with this older=20 version. I'm most interested in having the possibility to store per-user=20 settings for the following amavisd-new settings in a SQL (MySQL)=20 database : spam_quarantine_to, virus_lover, spam_lover and=20 banned_files_lover. These ones "seems" (but I'm not sure yet) to be=20 supported by my current amavisd-new version (20030616p10). There are some additional amavisd-new settings which I would like to=20 store also in a SQL database, but I found a comment into the=20 README.lookups to be somewhat discouraging : "--Here are some additional (more recent) optional fields, --not accounted for in the INSERT INTO examples further down. --Add them to you schema (into table 'policy') if you need them:" This "more recent" is what I din't understood. Does this means that=20 in order to have amavisd-new look up the database for these "more=20 recent" settings I shold be using a "more recent" amavisd-new version ?=20 If so, which one specifically ? Is there a way I could check (in the amavisd-new sources, probably)=20 if a lookup for a given amavisd-new parameter is supported ? Regards, -- Andr=E9 Lu=EDs Lopes ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/...fo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/ |
![]() |
| Thread Tools | |
| Display Modes | |
|
|