Re: a few suggestions / vmailmgr server wide?

Hi Olivier,

> > OK. This is not hard to implement at all. Do you want to know what is the
> > worst part in adding this to the project? Getting the translations!  I'd
> > have to create a new template and beg all those who kindly translated the
> > blacklist template to translate this new file to their native language. :)
> > But I'll look into it.
> 
> my hint: Don't worry about translation: just put the english version in
> all files, and you will magically get the translations later, for the
> next update...   I can help with french and german ASAP if you need: you
> can reach me by mail or AIM: swix3k. 

That would help. I'll add this feature to the list of things to be coded for
the next release.

> > ASK will eventually stop sending mails to a given subscriber after five or so
> > emails. This will last until a number of emails from other people come in to
> > push the "offending" addresses off a FIFO. You can play with those thresholds
> > if you like.
> 
> mmm, where is then this setting ? I don't see it in .askrc (but not
> looked very long).

I left these parameters out of the sample askrc purposedly, to prevent
unnecessary tweaking that could lead to disastrous consequences.  Whenever
ASK sends a confirmation, it stores the recipient's email address in a
FIFO. The maximum size of the FIFO (in lines) is rc_max_confirmation_list
(default = 40 lines). Once the list exceeds this size, it will be trimmed to
be the difference between rc_max_confirmation_list and rc_min_confirmation
list (default = 20 lines). A given email address is allowed to appear
rc_max_confirmations (default = 5) times in this list before ASK stops
sending confirmations to it. Note that as ASK sends new confirmations,
addresses are pushed off the list. This will eventually push the offender's
address out of the list giving him/her a chance to receive another
confirmation.

> > > Don't you think only one would be enough? For example there could be a
> > > setting: maximal frequency of confirmation request: max 1 per hour, 1
> > > per day or one per week...  (like good mailresponders works). 

I would code it this way too, but, to be honest, I did not code this
section of ASK (/me ducks and takes cover, waiting for Kurt's bomb) :)))

> Another problem: I've been away one week, and now the ASK queue has
> about 1000 mails, with 990 of the same "person" in it.  Using the remote
> commands I get a list of the 1000 mails... 
> 
> It would be _much_ nicer if it could send a list of _UNIQUE_ email
> addresses pending. If an address has got many emails, just display
> a sample set of the Subjects (for example the last 5 or 10 ones). 

This is still a workaround. The ideal situation is to dequeue everybody with
the same sender's address (which I plan to do). I don't feel this problem so
much because I use IMAP to browse my queue. It's simple (in mutt) to filter
by from and dequeue all messages at once.

> Otherwise I would have to click 990 times on the html link: that
> is not very nice... don't you think? :)  Do you see what I mean?

Ouch! :)

> regards,
> Olivier

Regards,
Paga

-- 
Marco Paganini          | UNIX / Linux / Networking
[email protected]   | PGP: http://www.paganini.net/pgp/
http://www.paganini.net | Magnus Frater te spectat...


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click