Bonnetot Jean-Daniel wrote:
Assuming I would take the needed time to develop that functionality.
Would you be willing to code the management interface in the DSPAM
web UI?
I will look if it is possible for me but as I said, I'm not developer
and the only languages I know is Ruby and Bash.
If someone have knowledge to do ...
What about the way the email address is saved? Would just simple
email address be enough or would you like the whole stuff to support
regexp? Some storage engines support regexp in SQL. That's the reason
I ask.
For my needs, just simple email address or domain only is sufficient.
Maybe someone need something else ?
How would you like the function to work? Should it offer a per user
storage for white lists or should it offer a layered level of
whitelisting (aka: search user based whitelist, then search global
based whitelist)?
"search user based whitelist, then search global based whitelist" this
is a good idea.
Should those whitelist entries expire? I mean should a given entry be
deleted after a certain time if not used?
For me, I see this whitelist fully managed by users, so no automatic
actions.
etc, etc, etc.... A lot of questions where I think the DSPAM
community should bring all their needs on the table and together we
choose what to implement and how to implement. I have a whitelisting
functionality in my setup but not inside DSPAM. I have implemented it
outside of DSPAM. So I have a certain viewpoint but probably my
viewpoint is not valid for everyone. I for example add automatically
every recipient from an outbound message (but only if the sender is
authenticated with SMTP AUTH) to a whitelist for +/- 90 days. If the
email address does not send in the specified time range a mail to the
original sender, then the whitelist entry get's deleted. And so on...
To all the people on the ML wanting that manual whitelisting
functionality: let's hear about your needs.
Yes, this functionality would have to cover maximum of needs concerning
whitelist.
You can just add your needs below :
- simple email address matching
- domain matching
- fully managed by user
- user whitelist concatenated with global whitelist
- managed with dspam binary
- ...
- Full email address matching ( IE "Joe Schmoe" <[EMAIL PROTECTED]> )
- Option to match on from address and/or "Reply-to:" address.
- Administratively managed per user whitelist
- No user managed whitelist.
- No global whitelist.
- dspam gui displays whitelisted emails.
-Troy
!DSPAM:1011,48761342150921110373214!