Custom Query (21 matches)


Show under each result:

Results (7 - 9 of 21)

1 2 3 4 5 6 7
Ticket Resolution Summary Owner Reporter
#27 fixed Ror-farm: define MAILTO for 'ror' user crontab Lucas Bonnet Vincent Caron

Ror-farm templates currently use nullmailer in the vserver context to synchronously transfer the mail to the root server MTA (it's local, hence as fast as possible).

Nullmailer defaults to a single adress for 'root' or undefined users, which has obviously been mapped to Bearstech's own root email collector.

OTOH, the user crontab should send mail to the user. But MAILTO is undefined in the default crontab, and the root collector receives various stuff about user's applications and custom scripts.

Fix proposal:

  • Define a MAILTO=null@… in the template crontab for the 'ror' user; apply on existing instances if MAILTO is undefined
  • Find a way to automatically grab the user's email adress (from the Redmine account) and use it in the crontab's MAILTO
#4 fixed ITP: phptop 0.1 zecrazytux Vincent Caron

Goal: provides a arch:all (no binary) package for PhpTop with relaxed dependencies on PHP and Perl in order to work with Etch, Lenny, Squeeze and Sid (they all have PHP >=5.2 anyway).

It depends on perl (I believe no post-5.6 features are used so we're cool with 5.8 and 5.10) and libwww-perl (no specific version required).

It may suggest or recommend php5-cgi|libapache2-mod-php5|libapache2-mod-php5filter (without a server-side SAPI phptop is not really exciting).

It might install itself by creating a file such as /etc/php5/conf.d/phptop.ini with this content:


And should run 'apache2ctl reload' if relevant, maybe check the policy and code in php5-gd postinst for instance.

phptop itself is a classic /usr/bin userland program.

To be published on - and later pushed to Debian.

#5 fixed BearMail::Web::Login error handling zecrazytux Vincent Caron

We need some error and feedback handling in bearmail login: Add some div in source:/bearmail/template/login.html. I'd suggest a <p class="error"> before the submit button, and only present if an error occurs. I'm not fan on errors "on top" which shift the whole form layout down.

And of course add proper logic in source:/bearmail/lib/BearMail/Web/ - see if CGI::App has some "standard way" to handle error/flash messages.

I'd like meaningful errors (instead of a single message "Login failed"):

  • "Echec: le mot de passe est incorrect, essayez à nouveau."
  • "Echec: cette adresse email est inconnue."

I know it's supposed to be a privacy issue since a brute force attack can guess the list of hosted domains and addresses, but it's also so convenient for end users who must know if they mispelled their address or password in the first place.

(BTW all public strings are French, let's keep it that way until we add i18n)

1 2 3 4 5 6 7
Note: See TracQuery for help on using queries.