OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Duke Ionescu (dukemastre.com)
Date: Mon Oct 01 2001 - 16:00:45 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Sep 25, 2001 16:11 postfixxtremedev.com wrote:
    > I'm running into a problem with user case sensitivity in emails.

    On Sep 28, 08:00 Rod... Whitworth <listenerwitworx.com> replied:
    >>>
    Read RFC2821:
    Verbs and argument values (e.g., "TO:" or "to:" in the RCPT command
    and extension name keywords) are not case sensitive, with the sole
    exception in this specification of a mailbox local-part
                                         ^^^^^^^^^^^^^^^^^^^
    So why should Postfix break that?

    It was the same IIRC in RFC821 so anything that lcases your localpart
    is broken. Fix the sender.
    <<<

    To answer your question, I will quote Wietse's excellent reasoning:
    On Nov 17, 2000 Wietse Venema <wietseporcupine.org> wrote:
    >>>
    Reason for the case insensitivity: even though RFCs say that the
    left-hand side case should be preserved, it is not reasonable to
    expect that remote senders will remember the "right" CaPiTaLiZaTiOn
    of an email address. It just is not practical.
    <<<

    So, that makes sense. BUT, looking thru the RELEASE_NOTES, one can
    see that this behavior has changed since snapshot-20010808, where we
    get this tasty morsel:

    > The Postfix pipe delivery agent no longer automatically case-folds
    > the expansion of $user, $extension or $mailbox command-line macros.
    > Specify the 'u' flag to get the old behavior.

    I ran into this problem myself today when I upgraded from
    20010228-pl03, and had to fix it. So, in the interest of the greater
    good, I present the solution:
    As the above hints, you have to add the `uŽ flag to the pipe delivery
    agent. If you are running Cyrus (as I am), you will replace the line
    in master.cf which reads (lines might get mangled a bit by PGP):

    cyrus unix - n n - - pipe
        flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m ${extension}
    ${user}

    with one that reads:

    cyrus unix - n n - - pipe
        flags=Ru user=cyrus argv=/usr/cyrus/bin/deliver -e -m
    ${extension} ${user}

    That it, the whole big enchilada!
    The default operation of the current Postfix snapshot, in this
    regard, is per RFC and you must use the option above in order to have
    what some people would call `brokenŽ functionality. In this regard
    I, for one, disagree with the RFC because from a usability point of
    view it's hell for the mindless corporate users ("What's this, a
    cupholder?" ;)

    P.S. If you are running something other than Cyrus, it's the same,
    because the flags are for the `pipeŽ program, which are part of
    Postfix (`man pipeŽ).

    -----BEGIN PGP SIGNATURE-----
    Version: PGP 6.5.8

    iQA/AwUBO7jZfMWLnVTiCTx7EQLp2ACg7lDXQ5qIf411pFUvjsJeP19lEmIAoLFs
    39dHCN+92QsCXX2dJvDjNu/E
    =jddP
    -----END PGP SIGNATURE-----

    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users