After remove from SOURCE/imap/message.c & lmtpengine.c ,problem is fixed.
Thanks a lot Dmitry.
David Chang
¤Þ¥Î Dmitry Novosjolov <[EMAIL PROTECTED]>:
> Hello,
>
> I think I had the same issue with subjects,
> here is what I did:
>
> I removed from cyrus-imapd sources a line which changes subje
[EMAIL PROTECTED] wrote:
> I have read man page about imapd.conf,but there is only one item about 8-bit
> setting - reject8bit .But that seems not working for my situiation.
>
> I was used wu-iampd before,and everything looks fine.So I guess wu-imapd must
> support 8-bit mail's header,am i right
Hello,
I think I had the same issue with subjects,
here is what I did:
I removed from cyrus-imapd sources a line which changes subject if the
subject consists non 7 bit chars. You can easily find where it is in source
code by greping the line: reject8bit. I cannot tell more specifically at the
mo
I have read man page about imapd.conf,but there is only one item about 8-bit
setting - reject8bit .But that seems not working for my situiation.
I was used wu-iampd before,and everything looks fine.So I guess wu-imapd must
support 8-bit mail's header,am i right ?
David Chang
¤Þ¥Î "Scott M. Li
The reason why it's doing this is because cyrus or your MTA is stripping
the 8th bit. It's a very simple option in imapd.conf to set, if you
need to either man it, or read the docs you'll find the exact option to
stop that.
Thanks and goodbye
-Original Message-
From: [EMAIL PROTECTED]
[m
[EMAIL PROTECTED] wrote:
> Hi all:
> I am a Chinese user in cyrus.
> There are a strange problem in email Subject's display problem.
>
> If i send a mail with Chinese words in subject field from outlook express to
> myself.When i received this mail from cyrus-imap i found,that the Subject looks
Blah... Right, the Subject not the To field. Never mind my last post.
Cove
On Thursday, February 20, 2003, at 06:40 PM, David Chang wrote:
Hi all:
I am a Chinese user in cyrus.
There are a strange problem in email Subject's display problem.
If i send a mail with Chinese words in subject field
Hi David,
Do you mean something like this?
To:
If so, I've also noticed this on occasion, though I figured it was due
to Microsoft Entourage
From: <[EMAIL PROTECTED]>
Date: Fri Jan 3, 2003 2:55:02 PM US/Pacific
To:
Subject: FW: Newly price list from james.
Return-Path: <[EMAIL PRO
Hi all,
I'm trying to install cyrus-imap 2.1.12 on a machine running freeBSD4.7.
I've sucessfully installed cyrus-sasl 2.1.12. But no luck to get
cyrus-imap compile. The following are copy-and-paste. Anyone's help will
be greatly appreciated. Thank you in advance.
[root /usr/src/cyrus-ima
Hi all:
I am a Chinese user in cyrus.
There are a strange problem in email Subject's display problem.
If i send a mail with Chinese words in subject field from outlook express to
myself.When i received this mail from cyrus-imap i found,that the Subject looks
like "XXX?" .Anybody can tell me
One thing you can try is to log what procmail does with a directive like
this:
LOGFILE=/var/log/mail/procmail.log
which might give you some useful information. You could also try
delivering the mail to a standard mbox file and examining it to see if
theres any other bogus headers that might be
Thank you for the suggestion. I added the formail line to the .procmailrc,
but I still am not getting an of the messages delivered to the mailbox. I'm
not even seeing procmail even calling /usr/cyrus/deliver in my mail logs (we
use procmail for alot of other things -- mainly spam checking). I'm s
>> The missing symbols in the sasl lib were being caused by a prehistoric
>> gdb build. A new build of gdb got three "fatal" internal errors while
>> starting, but gave me enough information to suspect the API had changed.
>
>There shouldn't have been an API change from 2.1.7 to 2.1.12, what
>funct
Quoting James Miller <[EMAIL PROTECTED]>:
> Thank you all for your advice. mkimap was the hint I needed. It would
> seem
> that all of the directories under /var/imap/user/(a-z) were all lower case
> instead of being upper case (A-Z).
>
> But I'm still confused why the directories were created
Hi all,
I'm having trouble using /usr/cyrus/deliver for delivering mail to
mailstore.And am hoping someone else has run into this problem before.
I'm sure it's something stupid on my part. While testing, I'm using
procmail to deliver new messages. Here's the .procmailrc receipt I'm using:
--
Thank you all for your advice. mkimap was the hint I needed. It would seem
that all of the directories under /var/imap/user/(a-z) were all lower case
instead of being upper case (A-Z).
But I'm still confused why the directories were created all lower case
instead of upper case (per the tools/mki
On Wed, Feb 19, 2003 at 07:16:53PM -0600, David Masover wrote:
> Using cyrus 1.5.19 on debian-testing. Trying to deliver mail to Cyrus
> from exim. cyrdeliver fails with errorcode 75, every time, no matter
> what the options, except if I specify '-l' for LMTP. I don't think exim
> knows LMTP,
On Thu, 20 Feb 2003, Rob Siemborski wrote:
> On Thu, 20 Feb 2003, John C. Amodeo wrote:
> > We've run into this problem on Linux and it was determined glibc was most
> > likely the problem. John Wade wrote a file locking patch for 2.0.16 that has
>
> Of course, the real answer is "find the bug in
Don't know how much it will help you, but when we were dealing with some
locking issues in cyrus I grabbed a tool called "lslk" that's similar to
lsof but reports tons of locking information. I don't remember where I
got it, but google should be your friend.
Thanks,
Dave
--
Dave McMurtrie, Syste
* a generic lock debugging strategy...
The first question is what OS are you running on? If this is Linux,
applying the poll-style locking will probably mask whatever the
problem is. If it's something else:
. processes get stuck waiting for a lock (truss shows stuck process in
fcntl)
. the pro
Pong
On Thu, 20 Feb 2003, John C. Amodeo wrote:
> We've run into this problem on Linux and it was determined glibc was most
> likely the problem. John Wade wrote a file locking patch for 2.0.16 that has
> worked for us flawlessly for about a year now. Its really saved us from a
> situation where we h
On Thu, 20 Feb 2003, Jay Levitt wrote:
> Thanks.. for my education, are there cases (legitimate or just bugs) where
> FILE could be null but errno == 0? I haven't done a whole lot of UNIX
> programming yet.
No, but I have seen cases where errno won't be reset on success (errno !=
0 and file != N
Test
Rob & Scott,
We've run into this problem on Linux and it was determined glibc was most
likely the problem. John Wade wrote a file locking patch for 2.0.16 that has
worked for us flawlessly for about a year now. Its really saved us from a
situation where we had to restart the Cyrus server every n
On Thu, 20 Feb 2003, Scott Adkins wrote:
> whole university, so the less we do to it, the better. We will upgrade
> to the latest greatest version when summer gets here, which seems to
> get here pretty quick anyways...
By this I hope you mean 2.1.12, since 2.0 is really done except
for security
On Thu, 20 Feb 2003, Christian Schulte wrote:
> Igor Brezac wrote:
>
> >On Wed, 19 Feb 2003, Ilya wrote:
> >
> >
> >
> >>Ken, do you have any plans for global admins without default domain setting?
> >>
> >>
> >
> >I got this working by accident, but this would be a nice feature. Admin
> >needs
On Thu, 20 Feb 2003, Andrew McNamara wrote:
> The missing symbols in the sasl lib were being caused by a prehistoric
> gdb build. A new build of gdb got three "fatal" internal errors while
> starting, but gave me enough information to suspect the API had changed.
There shouldn't have been an API
On Thu, 20 Feb 2003, Wolfgang Hottgenroth wrote:
> If you're wondering why there is a proxy_authname in the imapd.conf of
> the backend: I found that backend-to-backend moving of mailboxes seems
> to require this. Is this intentionally?
Sort of. It could probably be documented clearer. (Since w
Igor Brezac wrote:
>
> On Wed, 19 Feb 2003, Ilya wrote:
>
> > Ken, do you have any plans for global admins without default domain setting?
>
> I got this working by accident, but this would be a nice feature. Admin
> needs to be unqualified and the imap server ip address should not resolve
>
We are running into issues on our system where IMAP and LMTP processes
become stuck and start to stack up and never go away. The IMAP processes
aren't so bad, but LMTP definitely is... Investigating the problem with
truss and lsof shows that all of the *stuck* processes (the ones that
seem to be o
Hi,
on my cyrus 2.1.4 I get several error messages like
Feb 20 16:37:27 golem imapd[4353]: DBERROR db3: 82f9/894:6902192
Feb 20 16:37:45 golem imapd[4353]: DBERROR db3: 82fa/894:
82f9 6902336
Feb 20 16:49:57 golem lmtpd[5162]: DBERROR db3: 2 lockers
Feb 20 16:50:16 golem lmtpd[51
I've committed this, with the small modification that it checks to see if
the FILE * returned is NULL, instead of errno != 0.
-Rob
On Thu, 20 Feb 2003, Jay Levitt wrote:
> Right now, lmtpd assumes that if fopen() fails on the sieve script, it must
> be because the file isn't there, which is a va
Igor Brezac wrote:
On Wed, 19 Feb 2003, Ilya wrote:
Ken, do you have any plans for global admins without default domain setting?
I got this working by accident, but this would be a nice feature. Admin
needs to be unqualified and the imap server ip address should not resolve
to a FQDN.
Right now, lmtpd assumes that if fopen() fails on the sieve script, it must
be because the file isn't there, which is a valid condition, so no error is
logged. Since two people this week had permissions problems, seems like
something that ought to be logged. This simple patch does it.
Jay Levitt
Okay, I got it. _mechs is required if KERBEROS_V4 is not
supported ...
Sorry for distrubing you.
Wolfgang
On Thu, 20 Feb 2003, Wolfgang Hottgenroth wrote:
> Hi,
>
>
>
> is there a problem with proxying POP3 connection from a frontend to a
> backend in v2.1.12?
>
> I've a test setup with two f
RJ45 wrote:
Hello I haev lately this error mesage always the same time of day once a
day:
imaplog:Feb 7 04:00:00 venus ctl_deliver[429]: [ID 866726 local6.warning]
DBERROR db4: 6 lockers
This is (almost) completely normal. If the number of lockers keeps
rising constantly, that is not. It may ve
Hi,
is there a problem with proxying POP3 connection from a frontend to a
backend in v2.1.12?
I've a test setup with two frontends, two backends and a mupdate
master.
While proxying of IMAP connection works fine and while I can connect
to a backend using POP3 without problems any attempt to con
>I upgraded a previously working postfix from cyrus-sasl-2.1.7 to
>cyrus-sasl-2.1.12, and while SASL works fine for smtpd, the lmtp process
>dumps core within the SASL libraries. The resulting core isn't really
>useful because I'm not getting any symbols resolved from the sasl lib..
Sigh - SASL wa
Ah sorry, I just pasted the first filter in - the script tests out fine
using the sieve 'test' binary.
Daryl
--On 20 February 2003 18:55 +0900 Mark Keasling <[EMAIL PROTECTED]> wrote:
Hi,
Is the '}' missing in your script or did you just miss it when cutting and
pasting?
On Thu, 20 Feb 2003 0
Hi,
Is the '}' missing in your script or did you just miss it when cutting and
pasting?
On Thu, 20 Feb 2003 09:39:12 +, Daryl <[EMAIL PROTECTED]> wrote...
>
>
> --On 19 February 2003 15:10 -0500 Ken Murchison <[EMAIL PROTECTED]> wrote:
>
> > Did you check the permissions on the entire path
--On 19 February 2003 15:10 -0500 Ken Murchison <[EMAIL PROTECTED]> wrote:
Did you check the permissions on the entire path to your script? Do you
have 'sieveusehomedir' enabled? DO you have any messages in imapd.log
like: "lmtpd: unable to init duplicate delivery database"?
User Cyrus can
I upgraded a previously working postfix from cyrus-sasl-2.1.7 to
cyrus-sasl-2.1.12, and while SASL works fine for smtpd, the lmtp process
dumps core within the SASL libraries. The resulting core isn't really
useful because I'm not getting any symbols resolved from the sasl lib
(dynamlic linking?):
43 matches
Mail list logo