Three questions about Cyrus::IMAP::Admin:
I am using Cyrus::IMAP::Admin for a script to archive mailboxes. It
should rename mailbox to mailbox.Archives.dateinteger.
1). How does one list mailboxes which _don't_ contain .Archives.?
It's one thing to list those that _do_:
my @mailboxes =
On Jun 26, 2004, at 1:42 PM, Aristotelis wrote:
Hello, I haven't seen the patch yet, since I'm out
of the cyrus-testing environment we have. But still
I do believe that this idea is a bad idea.
On Sat, 26 Jun 2004 [EMAIL PROTECTED] wrote:
Let me explain why I'm so hung up on this auto-create
On Jun 24, 2004, at 1:24 PM, John Wade wrote:
[EMAIL PROTECTED] wrote:
On Jun 24, 2004, at 2:01 AM, Aristotelis wrote:
On Wed, 23 Jun 2004 [EMAIL PROTECTED] wrote:
It is essential to me to create the mailboxes for which incoming
messages are intended when they don't exist. To this end, I am
On Jun 24, 2004, at 2:01 AM, Aristotelis wrote:
On Wed, 23 Jun 2004 [EMAIL PROTECTED] wrote:
It is essential to me to create the mailboxes for which incoming
messages are intended when they don't exist. To this end, I am writing
a patch.
I haven't seen the patch yet. But I want to get some more
Thank you for the suggestion, but I think autocreateinboxfolders
takes as an argument a static list of sub-mailboxes to create, upon the
auto-creation of an INBOX. So it doesn't enable the dynamic creation of
an arbitrary mailbox, based on a delivery request.
Please correct me if I'm wrong.
It is essential to me to create the mailboxes for which incoming
messages are intended when they don't exist. To this end, I am writing
a patch.
The patch is currently *very* neanderthal - but it kind of works.
Unfortunately, there are problems with the mailboxes it creates. I can
see them,
When I tried this patch a month or so ago, it would create INBOXs, but
not other mailboxes. For instance, I tried posting a message to a
nonexistent mailbox, INBOX.new-mailbox; it ended up in INBOX. Possibly
I misused the patch, and possibly it now does what it didn't before. I
would be glad
Thanks - point taken.
After consideration, however, I don't clearly understand the increased
vulnerability.
Calling mboxlist_createmailbox from lmtpd takes an auth_state,
which I presume must have authority to create the specified mailbox.
For an attacker to flood the system with new
Thank you very much for your suggestion - I've experimented with the
autocreate patch... I want to automatically create arbitrary folders
on post - when they are delivered to.
I think, however, that this patch will only create INBOXs - not
arbitrary folders as I desire.
I haven't experimented
The [cyr]deliver manpage explains that if delivery is attempted to a
mailbox, user.userid.mailbox, and ... the ACL on any such
mailbox does not grant the sender the p right ... then delivers to
the INBOX for the userid, regardless of the ACL on the INBOX.
If delivery is attempted to any
In one area I have had trouble using Cyrus IMAPd: Delivery.
After considerable effort - and help from others - I believe I've
arrived at the fundamental problem: I wish for users to be able to
filter mail using arbitrary user level programs, but I don't wish for
users to be able to deliver mail
I would like to periodically automatically rename mailboxes. The size
of some mailboxes can quickly grow out of hand. Say, once a month, I'd
like INBOX.busy-list moved to INBOX.busy-list.20040418 - for
instance.
I thought first of a cron job, calling cyradm, but this is the limit
of my
Bad indeed : /
First, I recompiled Cyrus according to instruction. I obtained an
strace: http://www.sfu.ca/~jdbates/cyrdeliver/strace; and ltrace:
http://www.sfu.ca/~jdbates/cyrdeliver/ltrace;.
From the ltrace, I gather:
---
sasl_setprop(0, 101, 0x80761a0, 0xbfffce74, 0x400083bf) = -7
---
... I dislike people who do not read docs : ) Fair enough.
I have now read _all_ /usr/share/doc/cyrus21-imapd/* and am struggling
to configure cyrus delivery using TCP sockets. cyrus.conf and
imapd.conf contain:
---
lmtp cmd=lmtpd listen=localhost:lmtp prefork=0 maxchild=20
---
lmtpsocket:
Trying to do mail filtering to cyrus imapd using procmail instead of
sieve. I'm putting | [cyr]deliver -m blah-folder into my
~/.procmailrc, instead of the global /etc/procmailrc; this fails:
couldn't connect to lmtpd: Permission denied_ procmail: Program
failure (75) of /usr/sbin/cyrdeliver )
I use a script and [cyr]deliver -m to automatically sort messages.
When it delivers a message to a nonexistent folder, I would like the
folder to be created, instead of delivering the message to INBOX. Can
[cyr]deliver create the folders to which it delivers? What techniques
have others used?
I'm attempting to connect to the Cyrus IMAPd mailbox admin on
wum.lat as the Kerberos principal [EMAIL PROTECTED], using proxy
authorization. The principal imap/wum.lat is in the realm RUZ -
cross realm authentication is working - I can connect to the mailbox
admin as [EMAIL PROTECTED].
I'm running Cyrus IMAPD 2.1.16 and INN 2.4.1 on a single server. I'm
using INN tradspool storage. Can I automatically export export
newsgroups to IMAP using Cyrus and the partition-news and newsspool
parameters?
Thanks,
Jack
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ:
I am trying to make one instance of a kerberos principal the cyrus
administrator. I've set the admins: field to username/admin. When I
try running cyradm -u username/admin servername, cyradm complains:
cyradm: cannot authenticate to server as user username/admin
Syslog contains the following
19 matches
Mail list logo
