Thank you for replying to my email.
Connect was probably the wrong word. Here is the situation. I work on
operational project that uses qmail to receive incoming mail on Digital
Alpha servers. We have found that all user accounts created in the
/etc/passwd file of this server must be made in lower case, because it is
our experience that qmail seems to convert incoming mailbox names (To:) to
lower case.
Question 1: > Is qmail RFC compliant to the best of your
knowledge. Especially with regards to case sensitivity, mailbox user names
and any address conversions that take place?
Question 2: If qmail does convert any of the addresses to lower
case, can you shed any light on why?>
Question 3: I have been told that qmail is RFC compliant, in that
it is case insensitive, but it does alter the case of a mailbox user name.
Do you agree with this statement? Why or why not?
Question 4: What are qmail-getpw, qmail-pw2u, qmail-users? What do
they do? How if at all could they be used to handle mixed-case user names.
Question 5: How do you get qmail to accept and deliver mail to a
user with mixed case user name on a Unix system? For example the Unix
account name is: "GregGum123"
Thanks in advance for your help.
----------
From: Adam D . McKenna
Sent: Monday, August 16, 1999 11:06 AM
To: Gum, Greg
Cc: '[EMAIL PROTECTED]'
Subject: Re: Qmail case sensitivity
adam@spotted:~$ echo to:[EMAIL PROTECTED] | qmail-inject
==> /var/log/qmail/@00000934589497 <==
934815785.584174 new msg 14146
934815785.584186 info msg 14146: bytes 217 from <[EMAIL PROTECTED]>
qp 16516 uid 1000
934815785.623605 starting delivery 26638: msg 14146 to local
[EMAIL PROTECTED]
934815785.623626 status: local 1/10 remote 0/20
934815785.678035 delivery 26638: success: did_0+0+2/
934815785.678051 status: local 0/10 remote 0/20
934815785.678063 end msg 14146
adam@spotted:~$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 flounder.net ESMTP
mail from:<[EMAIL PROTECTED]>
250 ok
rcpt to:<[EMAIL PROTECTED]>
250 ok
data
354 go ahead
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]
hello
.
250 ok 934815918 qp 16539
==> /var/log/qmail/@00000934589497 <==
934815918.595499 new msg 14146
934815918.595510 info msg 14146: bytes 235 from <[EMAIL PROTECTED]>
qp 16539 uid 71
934815918.634793 starting delivery 26640: msg 14146 to local
[EMAIL PROTECTED]
934815918.634813 status: local 1/10 remote 0/20
934815918.685727 delivery 26640: success: did_0+0+2/
934815918.685743 status: local 0/10 remote 0/20
934815918.685754 end msg 14146
What's the problem?
--Adam
On Mon, Aug 16, 1999 at 10:46:22AM -0400, Gum, Greg wrote:
>
>
> I am using Qmail on a Unix system (Digital Unix) and recently had
a
> complaint from my customer that a new email user was unable to
connect to
> the system using Qmail. Evidently the user name needed to be
upper and
> lower case in their system and possibly in our server also.
>
> Is Qmail RFC compliant with case sensitivity using mailbox user
names? The
> reason I ask is Qmail seems to take all user names to lower case.
I have
> heard through my peers that the RFC states that the mailbox user
names need
> to be accepted as either upper case or lower case and not be
converted to
> lower case. Is this true? If not would you say that Qmail is RFC
> compliant? What is your thoughts with Qmail case sensitivity?
Is there a
> fix to the lower case conversion if I need to change our Qmail.
>
> Bottom line is if it is not RFC compliant and there is not a fix
to the case
> sensitivity issue, then I might need to come up with a good
argument not to
> replace Qmail in our system.
>
> Thank You
> Greg Gum
> Lockheed Martin
>
