public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Petre Rodan <petre.rodan@ravantivirus.com>
To: gentoo-dev@gentoo.org
Cc: "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: [gentoo-dev] qmail testing again
Date: Wed, 3 Sep 2003 09:55:36 +0300	[thread overview]
Message-ID: <20030903065536.GA27869@peter.rav.local> (raw)
In-Reply-To: <20030903003249.GB31229@curie-int.orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 2571 bytes --]


I'm sorry to disturb you, but I couldn't help noticing that currently there are 15 patches to qmail, and this number has the tendency to rise with every ebuild.

I feel that DJ Bernstein did a great job creating the world's safest MTA. This is one of the main reasons sysadmins use it. My point is that even if there are reasons for upgrading the product (to add new features and such) the issues with not doing it are considerable and will likely out-weigh them. The commotion generated by smtp-auth patch is an example.

Now please don't get me wrong, I appreciate your work, I simply fell in love with Gentoo but I think that those who would like to emerge qmail should have the choice of selecting the exact features that can make them happy. Simply masking versions doesn't sound to good, maybe some USE switches would ease the way. I'm wondering maybe qmail-1.03-x.ebuild can be made to inherit some patch related switches from a file that is system-specific.

What are your thoughts on this?

Best regards,
Petre Rodan


On Tue, Sep 02, 2003 at 05:32:49PM -0700, Robin H. Johnson wrote:
> Previously I asked for testers for qmail, and I would now like another
> round of testing. 
> 
> If you tested qmail before, please definetly do upgrade to this latest
> version as it fixes a major bug in my other testing version that could
> cause major mail delays and a remote possiblity of mail loss.
> 
> Sync up to the latest tree, then re-emerge -r12 of qmail (it's currently
> hardmasked).
> 
> STARTTLS and SMTP AUTH (both directions) should now work, but please
> test them. Likewise with the ESMTP SIZE addon, and the other patches
> involved.
> 
> I've got a few more patches to add in, then write some documentation in
> the install files as to how to use the new stuff.
> 
> -- 
> Robin Hugh Johnson
> E-Mail     : robbat2@orbis-terrarum.net
> Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
> ICQ#       : 30269588 or 41961639
> GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85



-- 

Petre Rodan
Senior Network Engineer
GeCAD Software - RAV Division

----------------------------------------------------------------------
Tel/Fax: +40-21-321-7803
Hotline:  +40-21-321-7859

This message is confidential. It may also be privileged or otherwise 
protected by work product immunity or other legal rules. 
If you have received it by mistake please let us know by reply and then 
delete it from your system; you should not copy the message or disclose 
its contents to anyone.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-03  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  0:32 [gentoo-dev] qmail testing again Robin H. Johnson
2003-09-03  6:55 ` Petre Rodan [this message]
2003-09-03  9:29   ` Robin H. Johnson
2003-09-04 11:49 ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030903065536.GA27869@peter.rav.local \
    --to=petre.rodan@ravantivirus.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=robbat2@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox