Re: Case sensitve user/mailbox names
"Kevin P. Fleming" wrote: > > Patrick Welche wrote: > > % exim -bV > > Exim version 4.12 #4 built 30-Jan-2003 16:41:01 > > Copyright (c) University of Cambridge 2002 > > > > So I think Kerstin is right... > > > > Cheers, > > > > Patrick > > Hmmm. I think this may have something to do with the method being used to get > the messages from Exim to Cyrus. > > There are (at least) four ways to do that: > > 1) Exim can pipe the messages to the Cyrus "deliver" command. > > 2) The Exim LMTP transport can deliver to Cyrus' lmtpd over a Unix socket. > > 3) The Exim LMTP transport can deliver to Cyrus' "deliver" command via a pipe. > > 4) The Exim SMTP transport (in LMTP protocol mode) can deliver to Cyrus' lmtpd > over a TCP/IP socket, with or without SMTP authentication. If anyone wants to update those methods already in the Cyrus docs, or document those that aren't, I'll be happy to add it to CVS. Keep in mind that we're looking for plain vanilla configs, just enough to get mail delivered properly. Any extra bells and whistles should be left up to the reader. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: Case sensitve user/mailbox names
Am Mittwoch, 5. Februar 2003 19:18 schrieb Kevin P. Fleming: > Hmmm. I think this may have something to do with the method being used to > get the messages from Exim to Cyrus. > > There are (at least) four ways to do that: > > 1) Exim can pipe the messages to the Cyrus "deliver" command. > > 2) The Exim LMTP transport can deliver to Cyrus' lmtpd over a Unix socket. > > 3) The Exim LMTP transport can deliver to Cyrus' "deliver" command via a > pipe. > > 4) The Exim SMTP transport (in LMTP protocol mode) can deliver to Cyrus' > lmtpd over a TCP/IP socket, with or without SMTP authentication. > We use the first method, which behaves as described. Regards, Kerstin
Re: Case sensitve user/mailbox names
On Wed, Feb 05, 2003 at 11:18:50AM -0700, Kevin P. Fleming wrote: .. > Hmmm. I think this may have something to do with the method being used to > get the messages from Exim to Cyrus. > > There are (at least) four ways to do that: > > 1) Exim can pipe the messages to the Cyrus "deliver" command. > > 2) The Exim LMTP transport can deliver to Cyrus' lmtpd over a Unix socket. > > 3) The Exim LMTP transport can deliver to Cyrus' "deliver" command via a > pipe. > > 4) The Exim SMTP transport (in LMTP protocol mode) can deliver to Cyrus' > lmtpd over a TCP/IP socket, with or without SMTP authentication. > > I am currently using method 4. I don't have time to test the different > methods to see how they handle caseful local parts, and there could > certainly be a bug in Exim in the LMTP transport. When I first set up Exim > 4.x, I was using method 3 and most definitely had to lowercase local parts > before sending them to Cyrus. > Ah - I'm using cyrus_delivery: driver = lmtp command = "/usr/cyrus/bin/deliver -l" batch_max = 20 user = cyrus as per the cyrus documentation which I think counts as 3)... Cheers, Patrick
Re: Case sensitve user/mailbox names
Patrick Welche wrote: % exim -bV Exim version 4.12 #4 built 30-Jan-2003 16:41:01 Copyright (c) University of Cambridge 2002 So I think Kerstin is right... Cheers, Patrick Hmmm. I think this may have something to do with the method being used to get the messages from Exim to Cyrus. There are (at least) four ways to do that: 1) Exim can pipe the messages to the Cyrus "deliver" command. 2) The Exim LMTP transport can deliver to Cyrus' lmtpd over a Unix socket. 3) The Exim LMTP transport can deliver to Cyrus' "deliver" command via a pipe. 4) The Exim SMTP transport (in LMTP protocol mode) can deliver to Cyrus' lmtpd over a TCP/IP socket, with or without SMTP authentication. I am currently using method 4. I don't have time to test the different methods to see how they handle caseful local parts, and there could certainly be a bug in Exim in the LMTP transport. When I first set up Exim 4.x, I was using method 3 and most definitely had to lowercase local parts before sending them to Cyrus.
Re: Case sensitve user/mailbox names
On Tue, Feb 04, 2003 at 10:35:46AM -0700, Kevin P. Fleming wrote: > Kerstin Espey wrote: > > > >As long as you don't use the option "caseful_local_part" in the exim > >router, exim will send all mails to the lowercase mailbox. > > > >Regards, > >Kerstin > > > > Exim 4.x does not act this way, but Exim 3.x did. If you don't make specific > > provisions to supply Cyrus a lowercase local part using Exim 4.x, the > messages won't get delivered. I couldn't believe that and just tried it: Subject: testing case From: "Patrick Welche" <[EMAIL PROTECTED]> Date: Wed, February 5, 2003 4:38 pm To: [EMAIL PROTECTED] Priority: Normal upErCaSe? % exim -bV Exim version 4.12 #4 built 30-Jan-2003 16:41:01 Copyright (c) University of Cambridge 2002 So I think Kerstin is right... Cheers, Patrick
Re: Case sensitve user/mailbox names
Kerstin Espey wrote: As long as you don't use the option "caseful_local_part" in the exim router, exim will send all mails to the lowercase mailbox. Regards, Kerstin Exim 4.x does not act this way, but Exim 3.x did. If you don't make specific provisions to supply Cyrus a lowercase local part using Exim 4.x, the messages won't get delivered.
Re: Case sensitve user/mailbox names
Am Dienstag, 4. Februar 2003 15:45 schrieb Pål Olsen: > I've just implemented a new mail platform using Cyrus IMAPd 2.1.11 and Exim > 4.12, and I wonder... how to deal with the fact that systems don't allways > do want you expect..? > > It seem to me that exim/cyrus has problem with delivery of mail if the > mail-address are written in another case than the mailbox-name... E.g. user > fridao@mydomain can't receive mail if the sender uses mail-address > Fridao@mydomain. How should I deal with that? > As long as you don't use the option "caseful_local_part" in the exim router, exim will send all mails to the lowercase mailbox. Regards, Kerstin
Re: Case sensitve user/mailbox names
Thanks!
Pål
By the way: Do we have to set up this rule as an extra router, or can the
normal Cyrus delivery router take care of the convertion..?
- Original Message -
From: "Kevin P. Fleming" <[EMAIL PROTECTED]>
To: "Pål Olsen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 04, 2003 4:30 PM
Subject: Re: Case sensitve user/mailbox names
> Pål Olsen wrote:
> > Hi,
> >
> > I've just implemented a new mail platform using Cyrus IMAPd 2.1.11 and
Exim
> > 4.12, and I wonder... how to deal with the fact that systems don't
allways
> > do want you expect..?
> >
> > It seem to me that exim/cyrus has problem with delivery of mail if the
> > mail-address are written in another case than the mailbox-name... E.g.
user
> > fridao@mydomain can't receive mail if the sender uses mail-address
> > Fridao@mydomain. How should I deal with that?
> >
>
> I have a router like this in my Exim 4.1x setup talking to Cyrus (at the
> appropriate place in the sequence, i.e. just before your Cyrus deliver
> router):
>
> lowercase_local:
>driver = redirect
>domains = +local_domains
>redirect_router = local
>data = ${lc:${local_part}}
>
> with the Cyrus delivery router being named "local".
>
This message contains information that may be privileged or confidential and is the
property of the Cap Gemini Ernst & Young Group. It is intended only for the person to
whom it is addressed. If you are not the intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any part
thereof. If you receive this message in error, please notify the sender immediately
and delete all copies of this message.
Re: Case sensitve user/mailbox names
Pål Olsen wrote:
Hi,
I've just implemented a new mail platform using Cyrus IMAPd 2.1.11 and Exim
4.12, and I wonder... how to deal with the fact that systems don't allways
do want you expect..?
It seem to me that exim/cyrus has problem with delivery of mail if the
mail-address are written in another case than the mailbox-name... E.g. user
fridao@mydomain can't receive mail if the sender uses mail-address
Fridao@mydomain. How should I deal with that?
I have a router like this in my Exim 4.1x setup talking to Cyrus (at the
appropriate place in the sequence, i.e. just before your Cyrus deliver
router):
lowercase_local:
driver = redirect
domains = +local_domains
redirect_router = local
data = ${lc:${local_part}}
with the Cyrus delivery router being named "local".
Case sensitve user/mailbox names
Hi, I've just implemented a new mail platform using Cyrus IMAPd 2.1.11 and Exim 4.12, and I wonder... how to deal with the fact that systems don't allways do want you expect..? It seem to me that exim/cyrus has problem with delivery of mail if the mail-address are written in another case than the mailbox-name... E.g. user fridao@mydomain can't receive mail if the sender uses mail-address Fridao@mydomain. How should I deal with that? Also, this makes it, at least confusing, when dealing with imap-clients: >$ telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK imap1.mydomain Cyrus IMAP4 v2.1.11 server ready . login fridao ** . OK User logged in . select inbox * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 6 EXISTS * 0 RECENT * OK [UNSEEN 5] * OK [UIDVALIDITY 1044311451] * OK [UIDNEXT 108] . OK [READ-WRITE] Completed . logout * BYE LOGOUT received . OK Completed Connection closed by foreign host. >$ telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK imap1.mydomain Cyrus IMAP4 v2.1.11 server ready . login Fridao ** . OK User logged in . select inbox . NO Mailbox does not exist . logout * BYE LOGOUT received . OK Completed Connection closed by foreign host. Is this a bug, or what..? If not a bug, is it intended to work this way - and why..? Chers, Pål This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
