Re: DBERROR

2005-07-13 Thread Simon Matter
> Adding the following to the original post as well. > > Directly after boot, the log looks like this. And then it will continue > to > look good with checkpointings until I restart the cyrus process... > > Jul 13 22:50:02 xanadu master[1766]: process started > Jul 13 22:50:03 xanadu ctl_cyrusdb[1

Re: Max length of domain ... ?

2005-07-13 Thread Marc G. Fournier
On Wed, 13 Jul 2005, Ken Murchison wrote: Marc G. Fournier wrote: Can someone tell me what the syntax is for logging in through a raw telnet session? So that I can determine if its a sieve daemon, or sieveshell, issue? I know IMAP and POP3, just not sieve :( Just use imtest, or one of i

Re: Max length of domain ... ?

2005-07-13 Thread Ken Murchison
Marc G. Fournier wrote: Can someone tell me what the syntax is for logging in through a raw telnet session? So that I can determine if its a sieve daemon, or sieveshell, issue? I know IMAP and POP3, just not sieve :( Just use imtest, or one of its variants (imtest, pop3test, sivtest). It

Re: Max length of domain ... ?

2005-07-13 Thread Marc G. Fournier
Can someone tell me what the syntax is for logging in through a raw telnet session? So that I can determine if its a sieve daemon, or sieveshell, issue? I know IMAP and POP3, just not sieve :( Thanks ... On Wed, 13 Jul 2005, Stefan Nitz wrote: Dear listeners, Am Mittwoch, 13. Juli 2005

Re: DBERROR

2005-07-13 Thread Per-Olov Sjöholm
Adding the following to the original post as well. Directly after boot, the log looks like this. And then it will continue to look good with checkpointings until I restart the cyrus process... Jul 13 22:50:02 xanadu master[1766]: process started Jul 13 22:50:03 xanadu ctl_cyrusdb[10342]: recove

Re: No CYRUSV2_MAILER_MAX macro?

2005-07-13 Thread Fred Bacon
On Wed, 2005-07-13 at 22:31 +0200, Per-Olov Sjöholm wrote: > > You say: > --snip-- > > I'm attempting to set a limit on the maximum size of messages handled by > > our email system. > --snip-- > Why don't you do that by adding the following to sendmail.mc > define(`confMAX_MESSAGE_SIZE', `100

Re: backslash in addresses?

2005-07-13 Thread alex
Quoting "Scott M. Likens" <[EMAIL PROTECTED]>: It seems unrealistic to me to expect a mailer to 'accept' backslashes in email address's. Let alone, sieve,etc. Well, any MUA I had in my hands will gladly accept them. Among the MTA, I know sendmail accepts backslashes *and* processes them as

Re: No CYRUSV2_MAILER_MAX macro?

2005-07-13 Thread Per-Olov Sjöholm
On Wednesday 13 July 2005 21.16, Fred Bacon wrote: > I'm attempting to set a limit on the maximum size of messages handled by > our email system. I'm using cyrus imapd 2.2.12 and sendmail 8.13.4 on a > Fedora Core 3 system. I want to set the M= equate for the cyrusv2 > mailer in my sendmail.mc fi

DBERROR

2005-07-13 Thread Per-Olov Sjöholm
Hi Does anybody know why this show up in the logs every half hour Jul 13 21:53:24 xanadu ctl_cyrusdb[4270]: checkpointing cyrus databases Jul 13 21:53:24 xanadu ctl_cyrusdb[4270]: DBERROR: error listing log files: Permission denied Jul 13 21:53:24 xanadu ctl_cyrusdb[4270]: DBERROR: archive /v

Re: Max length of domain ... ?

2005-07-13 Thread Stefan Nitz
Dear listeners, Am Mittwoch, 13. Juli 2005 20:35 schrieben Sie: > I have the virtdomain stuff setup, using cyrus 2.2.12, and just ran into > an "odd" issue ... one of the domains that we setup, sieve won't > authenticate for ... the domain is 60characters +.com: > > chiropractic-acupuncture-homeop

Re: backslash in addresses?

2005-07-13 Thread Scott M. Likens
It seems unrealistic to me to expect a mailer to 'accept' backslashes in email address's. Let alone, sieve,etc. I would ask what brought you to use backslashes in email address's, because not even Exchange uses them really. (Cept for logging in) But yes you would need to rebuild sieve to suppor

Re: backslash in addresses?

2005-07-13 Thread alex
Quoting David R Bosso <[EMAIL PROTECTED]>: It doesn't appear to be allowed by RFC2822 in local-part as it appears in "specials" and not "atext". In which case I guess there's no way to have timsived accept an address containing backslash? Other then e

No CYRUSV2_MAILER_MAX macro?

2005-07-13 Thread Fred Bacon
I'm attempting to set a limit on the maximum size of messages handled by our email system. I'm using cyrus imapd 2.2.12 and sendmail 8.13.4 on a Fedora Core 3 system. I want to set the M= equate for the cyrusv2 mailer in my sendmail.mc file with something like define(`CYRUSV2_MAILER_MAX',`200

Re: Cyrus bug? -> Strange over quota behaviour in cyrus imapd 2.2.12

2005-07-13 Thread Per-Olov Sjöholm
Good info! Now I know the status. I can live with 4Gb for now ;-) Thank you very much /Per-Olov -- GPG keyID: 4DB283CE GPG fingerprint: 45E8 3D0E DE05 B714 D549 45BC CFB4 BBE9 4DB2 83CE On Wednesday 13 July 2005 15.11, Paul Raines wrote: > Yes, the archive of this list shows a message that it i

Max length of domain ... ?

2005-07-13 Thread Marc G. Fournier
I have the virtdomain stuff setup, using cyrus 2.2.12, and just ran into an "odd" issue ... one of the domains that we setup, sieve won't authenticate for ... the domain is 60characters +.com: chiropractic-acupuncture-homeopathy-self-help-workshops-dvd.com The domain is valid, and testing IM

{Virus?} {Spam?} Account Alert

2005-07-13 Thread service
Prot: account-details.zip->account-details.doc Infection: W32/[EMAIL PROTECTED] Note to Help Desk: Look on the MailScanner in /var/spool/MailScanner/quarantine/20050713 (message j6DF65uM031321). -- Postmaster MailScanner thanks transtec Computers for their support

Re: backslash in addresses?

2005-07-13 Thread David R Bosso
--On July 13, 2005 9:49:34 AM -0500 [EMAIL PROTECTED] wrote: I haven't really checked RFCs to see if "\" is allowed charcter in an email address. It might be that it is, or that it isn't, or it might be that RFCs simply discourage its use. It doesn't appear to be allowed by RFC2822 in local-p

Re: backslash in addresses?

2005-07-13 Thread alex
Quoting Ondrej Sury <[EMAIL PROTECTED]>: Well, IMHO you are mixing .forward syntax with /usr/sbin/sendmail behaviour. Sieve reinjects forwarded mail using /usr/sbin/sendmail (or whatever you have configured in /etc/imapd.conf) and since backslashed email address is not valid, so isn't sieve sc

Re: cyrus-imap + sieve

2005-07-13 Thread Ondrej Sury
Return-path: is not reliable check (it's usually added by MDA), so most propably it's not there when sieve checks mail. You have to check for another header. > Return-Path: <[EMAIL PROTECTED]> so it should work, but it doesn't. Ondrej. -- Ondrej Sury <[EMAIL PROTECTED]> --- Cyrus Home Page: ht

Re: integer overflow at 2^32 in quota calculations

2005-07-13 Thread Ondrej Sury
> > Actually, it's an unsigned 32-bit value, so the limit is 4GB: > > > > https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2690 > > > > (Yes, we really do have users who are using more than 4GB of space.) > > The limit is still 32-bit signed. It needs to remain unsigned because > -1 is use

Re: backslash in addresses?

2005-07-13 Thread Ondrej Sury
Well, IMHO you are mixing .forward syntax with /usr/sbin/sendmail behaviour. Sieve reinjects forwarded mail using /usr/sbin/sendmail (or whatever you have configured in /etc/imapd.conf) and since backslashed email address is not valid, so isn't sieve script. So what you want to do is to learn

Re: Cyrus bug? -> Strange over quota behaviour in cyrus imapd 2.2.12

2005-07-13 Thread Paul Raines
Yes, the archive of this list shows a message that it is increased to a 64-bit max in the next major release. Some is considering backporting a patch. At the very least, IMHO, the next minor release should prevent admins from assigning quotas over 4GB. On Wed, 13 Jul 2005, Per-Olov Sjöholm w

Re: Cyrus bug? -> Strange over quota behaviour in cyrus imapd 2.2.12

2005-07-13 Thread Per-Olov Sjöholm
Paul Raines said: > Found this out myself last week and answered the same issue for > someone else yesterday. The max quota you can set is 4GB (using 400) > and anything over will result in a seemingly random quota limit > as it takes a 32-bit bit mask of what you have given over 4GB > > -- >