OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: heads-up: greylist support

From: Roman Neuhauser (neuhauserbellavista.cz)
Date: Sat Aug 02 2003 - 10:41:41 CDT


# hellsopninehells.com / 2003-07-16 18:28:37 -0500:
> On Wed, Jul 16, 2003 at 12:28:42PM +0200, Roman Neuhauser wrote:
> > # wietseporcupine.org / 2003-07-13 11:53:44 -0400:
> > > PROTOCOL DESCRIPTION
> > > ====================
> > >
> > > When the same attribute is sent more than once, the server may keep
> > > the first or the last instance.
> >
> > Why don't you mandate either behavior?
>
> Because then there's the opportunity for someone to write it wrong and
> screw up the protocol. If it's left "This may be either" then the
> other end MUST account for either behaviour instead of being lazy.

    Or, as I see it: it would eliminate interoperability issues.
    If it's left "This may be either" then we'll have implementations
    that are correct but incompatible as in: don't work together (very
    well).

--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html