Andrew Morgan schreef:
>
> On Thu, 30 Jun 2005, Paul van der Vlis wrote:
>
>> Igor Brezac schreef:
>>
>>>
>>> On Wed, 29 Jun 2005, Paul van der Vlis wrote:
>>>
Hello,
I want to use 2 authentication mechanisms with Saslauthd. When the
first
one gives "no", it should try th
Hi list,
i use web-cyradm in the actual cvs version and have the following problem with
cyrus and its quotas:
I use the option:
lmtp_over_quota_perm_failure: 1
in my imapd.conf to ensure that when the mailbox's quota is over, the mail is
rejected to the sender.
But it seems that cyrus acceps a
Hello,
I've added a simple script to add a mailbox to the wiki:
http://acs-wiki.andrew.cmu.edu/twiki/bin/view/Cyrus/ImapCreate2
It's based on Expect.
With regards,
Paul van der Vlis.
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/I
Christian Anton wrote:
Hi list,
i use web-cyradm in the actual cvs version and have the following problem with
cyrus and its quotas:
I use the option:
lmtp_over_quota_perm_failure: 1
in my imapd.conf to ensure that when the mailbox's quota is over, the mail is
rejected to the sender.
But
On Fri, 1 Jul 2005, Paul van der Vlis wrote:
Andrew Morgan schreef:
On Thu, 30 Jun 2005, Paul van der Vlis wrote:
Igor Brezac schreef:
On Wed, 29 Jun 2005, Paul van der Vlis wrote:
Hello,
I want to use 2 authentication mechanisms with Saslauthd. When the
first
one gives "no", it shoul
On Fri, 1 Jul 2005, Igor Brezac wrote:
Saslauthd with pam seems to be the more-stable and flexable alternative.
It is more flexible, but not more stable (see archives), performance is
suspect as well.
Is it possible in pam to use more then one module?
Yes.
Here is what my /etc/pam.d/
Hi everybody again,
As Ken helped me with my feature request for the quota behavior of cyrus-imapd
i now have one more question i don't understand.
If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to move
one message with 1 MB from one folder to another, cyrus gives me an er
Christian Anton wrote:
> Hi everybody again,
>
> As Ken helped me with my feature request for the quota behavior of
> cyrus-imapd
> i now have one more question i don't understand.
>
> If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to move
> one message with 1 MB from one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If i have a Mailbox with 5MB quota, there is 4.9MB in use and i want to
> move one message with 1 MB from one folder to another, cyrus gives me an
> error message that says i'm "over quota". Why does moving a message need
> space in the mailbox, i do
> Because IMAP doesn't provide a "move" operation for messages. Your
> client is probably first doing an append of the message to the
> destination folder (which is what's putting it over quota) then storing
> the delete flag of the original message and expunging.
I'm sure we've all had problems
Hello all,
I am setting up a new machine running Fedora Core 3 and the Cyrus
packages that came with it. I followed the instructions for using
this setup found here:
http://nakedape.cc/info/Cyrus-IMAP-HOWTO/quickstart-fedora.html
I am able to successfully log onto the IMAP server; however, I am
On Fri, 01 Jul 2005 09:37:40 -0400
Ken Murchison <[EMAIL PROTECTED]> wrote:
> Christian Anton wrote:
>
> > The problem: It is not anymore possible to delete this mail because most
> > of my users use IMAP or squirrelmail and when they "delete" a message
> > it ist moved to "Trash"-Folder. Movin
John Madden wrote:
>>Because IMAP doesn't provide a "move" operation for messages. Your
>>client is probably first doing an append of the message to the
>>destination folder (which is what's putting it over quota) then storing
>>the delete flag of the original message and expunging.
>
>
> I'm su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Is it wise to modify these clients to instead FETCH, delete/expunge, then
> STORE?
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough quota
that the STORE would
> Sounds like a recipe for lost messages should anything go wrong.. What
> happens if as you FETCH, new messages arrive and take up just enough quota
> that the STORE would put it over quota? What do you do with the message?
4th and 15. Punt.
That's certainly a tough situation. So what *is* the
>> Sounds like a recipe for lost messages should anything go wrong.. What
>> happens if as you FETCH, new messages arrive and take up just enough
>> quota
>> that the STORE would put it over quota? What do you do with the message?
>
> 4th and 15. Punt.
>
> That's certainly a tough situation. So w
Lars Kristiansen wrote:
Sounds like a recipe for lost messages should anything go wrong.. What
happens if as you FETCH, new messages arrive and take up just enough
quota
that the STORE would put it over quota? What do you do with the message?
4th and 15. Punt.
That's certainly a tough situat
I installed the lastest cyrus, compiled from the FreeBSD port.
I'm having a problem with timsieved not running as it's configured:
sieve cmd="timsieved" listen="sieve" prefork=0
>From the docs I read, this is correct. If I telnet to my local machine
(by IP, not 127.0.0.1) there's no respon
Forrest Aldrich wrote:
I installed the lastest cyrus, compiled from the FreeBSD port.
I'm having a problem with timsieved not running as it's configured:
sieve cmd="timsieved" listen="sieve" prefork=0
From the docs I read, this is correct. If I telnet to my local machine
(by IP, not 127
No it is not, but would that prevent it from running. Port 2000 is
allocated to "callback" (tcp|udp) in /etc/services.
Ken Murchison wrote:
> Forrest Aldrich wrote:
>
>> I installed the lastest cyrus, compiled from the FreeBSD port.
>>
>> I'm having a problem with timsieved not running as it's
Okay, I commented out "callback" in /etc/services and used Sieve. I
can connect with "sieveshell", but this appears to be a problem still:
# sieveshell myserver.domain.com
connecting to myserver.domain.com
Please enter your password:
Please enter your password:
perl in free(): error: junk p
21 matches
Mail list logo