Re: Cyrus 2.2.10: autocreatequota?
Hello Bernd, the patch is _not_ included by default in any of the Cyrus distributions. However, you can download the patch from http://email.uoa.gr/download/cyrus/ and patch your sources or use Simon Matter's RPMs that contain the patch. Cheers, Christos Bernd Nies wrote: > > Thanks for the info. Is this patch included in Cyrus 2.2.13? Didn't find > it in the changelog. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus 2.2.10: autocreatequota?
Hello all, I would like make clear some points about the autocreate inbox patch. 1. There is a patch for Cyrus 2.2.10. 2. If you have already created the mailbox through cyradm, the patch will not be activated and thus will not set any quota on your mailbox. 3. The patch is activated when the user logs in through IMAP or POP3 and the mailbox does not exist (autocreatequota option must be > 0) or if a mail is sent to a mailbox that does not exist through LMTP (autocreatequota > 0 and createonpost = yes). For more information and detailed documentation about the patch, you can fread http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 One final note is that the patch is not contained by default in the cyrus distribution. Therefore, you will have to patch your cyrus sources (patch can be downloaded from http://email.uoa.gr/projects/cyrus/autocreate/) or download Simon Matter's RPM packages that contain the patch. I hope this mail cleared things out a bit. Cheers, Christos Bernd Nies wrote: Hi Rafael, For this quota to work, the inbox needs to have recieved email via pop or lmtp... if the user has never logged in, or if he has never gotten email, then you cannot change the quota. Thanks for your response. The messages are delivered from Postfix via LMTP socket. If I send a message and the user inbox hasn't been created with cyradm, then I get this error: /var/cyrus/imap/socket/lmtp[/var/cyrus/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command) If I create the user inbox with cyradm and send then a message, then the default quota is infinite (not listed with the quota command). Bye, Bernd Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Create on login is not working in Cyrusimap/OLDAP
Hello there, could you also change your syslog settings so that you log debug info too? If you have enabled autocreate you should see something like the following: autocreateinbox: autocreate inbox for user was called Cheers, Christos Bipindas K wrote: Simon Matter wrote: Simon Matter wrote: Hi All, I had setup a squirrelmail/oldap server with autocreate patch. The problem is when a valid user login,cyrus will not create its inbox automatically. But the createonpost is working successfully. I am pasting my imapd.conf file below. -- autocreatequota: 1 createonpost: yes Remove the line below and try again. I don't think creating "Inbox" makes sense, INBOX is a special folder and is always created, what you do is creating a subfolder Inbox, like INBOX.Inbox. autocreateinboxfolders: Inbox|Trash|Sent|Drafts -- When a valid user login the squirrelmail showing following errors The problem I know with that configuration is that, at least when using pam, openldap users are not case sensitiv. That's why I added a new module to the pam stack which makes sure the user is lowercase. And in my case I also set "lmtp_downcase_rcpt: yes" in imapd.conf to apply the same rule from the MTA side. Simon (1).The following error show on left panel --- Warning: substr_count(): Empty substring. in /usr/share/squirrelmail/functions/imap_mailbox.php on line 394 Warning: substr_count(): Empty substring. in /usr/share/squirrelmail/src/left_main.php on line 932 (2).The following error show on right panel - ERROR : Could not complete request. Query: SELECT "INBOX" Reason Given: Mailbox does not exist - Please tell me the missing thing. Kindly help BipinDas -- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Hi simon, I had triend again according to your instructions,but fails. The same error throwing. So what is created on the server when you try to login or what do the logs show? Simon Hi simon, The *syslog* says the following when the user "tina" try to login, --- Feb 19 11:34:46 cyrus cyrus/master[21711]: about to exec /usr/lib/cyrus/bin/imapd Feb 19 11:34:46 cyrus cyrus/imap[21711]: executed Feb 19 11:34:46 cyrus cyrus/imapd[21711]: accepted connection Feb 19 11:34:46 cyrus cyrus/imapd[21711]: login: [xxx.xx.xxx.xx] tina plaintext Feb 19 11:34:47 cyrus cyrus/imapd[21711]: accepted connection Feb 19 11:34:47 cyrus cyrus/imapd[21711]: login: [xxx.xx.xxx.xx] tina plaintext Feb 19 11:34:47 cyrus cyrus/imapd[21711]: accepted connection Feb 19 11:34:47 cyrus cyrus/imapd[21711]: login: [xxx.xx.xxx.xx] tina plaintext The *imapd.log* says nothing in this mysterious situation. -- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sieve autocreate
Perhaps this patch may be useful for you. http://email.uoa.gr/projects/cyrus/autosievefolder/ Cheers, Christos Marten Lehmann wrote: > Hello, > > does sieve include any form of autocreating a "fileinto"-folder? > > I know that there's an option in Cyrus, but that doesn't help me in this > case. Each user shall be able to define a name for a Junk-folder. > Usually this is "Junk" (in Thunderbird), but in other Applications it > might be called "Spam", "Unwanted" or even with Umlauts "Unerw?nschte > Nachrichten". > > I surely put this name after the "fileinto" command, but is there also a > way to create this folder automatically or check if it exists at each > delivery? > > Regards > Marten > > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Seg faults in lmtpd in Cyrus 2.3.7
Do you possibly happen to have any Cyrus log files too? Preferably
logging debug messages too.
Cheers,
Christos
Lenny wrote:
Hello,
I'm currently using Simon's rpms on a Centos 4 murder setup. For awhile
now, I've been getting (occasionally) 15-20 minutes worth of "Deferred"
messages from sendmail. I never believed it was sendmail, but I've been
having issues proving that. We managed to get the debug_command going in
Cyrus, and have now found that it's lmtpd that's seg faulting, but I'm
still confused as to why.
This happens, like I said, randomly for 15-20 minutes at a time. It will
eventually start delivering fine on it's own. As a matter of fact, any
attempt at restarting services (cyrus, sendmail, etc) or rebooting the
server has NO effect (it will just keep Deferring until it starts
randomly delivering again).
At any rate, I so far have telemetry and strace logs and will paste an
example here. I hope to recompile with debugging and have a gdb
backtrace soon as well, but was wondering if anyone had ideas.
This has been happening for awhile now. It even happened occasionally in
2.2.x tho nowhere near as bad as 2.3.x has been. This also seems to
happen after the "Rcpt to:", either before or during the DATA section.
Example telemetry log:
1154532184>220 X.net LMTP Cyrus v2.3.7-Invoca-RPM-2.3.7-2.LN1
ready
<1154532184
1154532184>250-cX.net
250-8BITMIME
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-SIZE
250-AUTH EXTERNAL
250 IGNOREQUOTA
<1154532184 SIZE=2109
1154532184>250 2.1.0 ok
<1154532184
RCPT To:<[EMAIL PROTECTED]>
DATA
(and that's the last thing in the telemetry log).
Excerpt from strace:
11:23:04.144071 send(5, "<23>Aug 2 11:23:04 lmtpunix[100"..., 73,
MSG_NOSIGNAL) = 73
11:23:04.144318 open("/var/lib/imap/log/postman/10002",
O_WRONLY|O_APPEND|O_CREAT, 0644) = 8
11:23:04.144569 time(NULL) = 1154532184
11:23:04.144788 write(8, "-- postman Wed Aug 2 11"..., 45) = 45
11:23:04.145044 select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
11:23:04.145206 time([1154532184]) = 1154532184
11:23:04.145351 write(8, ">1154532184>", 12) = 12
11:23:04.145508 write(8, "220 XXX.net LMTP Cyr"..., 72) = 72
11:23:04.145704 write(1, "220 XXX.net LMTP Cyr"..., 72) = 72
11:23:04.146082 time(NULL) = 1154532184
11:23:04.146225 select(1, [0], NULL, NULL, {360, 0}) = 1 (in [0], left
{360, 0})
11:23:04.146408 time(NULL) = 1154532184
11:23:04.146532 time(NULL) = 1154532184
11:23:04.146684 read(0, "LHLO XXX.net\r\n", 4096) = 26
11:23:04.146856 time([1154532184]) = 1154532184
11:23:04.147030 write(8, "<1154532184<", 12) = 12
11:23:04.147187 write(8, "LHLO XX.net\r\n", 26) = 26
11:23:04.147430 select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
11:23:04.147592 time([1154532184]) = 1154532184
11:23:04.147763 write(8, ">1154532184>", 12) = 12
11:23:04.147914 write(8, "250-XXX.net\r\n250-8BI"..., 126) = 126
11:23:04.148065 write(1, "250-XXX.net\r\n250-8BI"..., 126) = 126
11:23:04.149743 time(NULL) = 1154532184
11:23:04.149893 select(1, [0], NULL, NULL, {360, 0}) = 1 (in [0], left
{360, 0})
11:23:04.150075 time(NULL) = 1154532184
11:23:04.150198 time(NULL) = 1154532184
11:23:04.150317 read(0, "MAIL From:<[EMAIL PROTECTED]"..., 4096) = 48
11:23:04.150484 time([1154532184]) = 1154532184
11:23:04.150658 write(8, "<1154532184<", 12) = 12
11:23:04.150822 write(8, "MAIL From:<[EMAIL PROTECTED]"..., 48) = 48
11:23:04.151030 open("/var/lib/imap/msg/shutdown", O_RDONLY) = -1 ENOENT
(No such file or directory)
11:23:04.151314 select(1, [0], NULL, NULL, {0, 0}) = 0 (Timeout)
11:23:04.151477 time([1154532184]) = 1154532184
11:23:04.151619 write(8, ">1154532184>", 12) = 12
11:23:04.151811 write(8, "250 2.1.0 ok\r\n", 14) = 14
11:23:04.151961 write(1, "250 2.1.0 ok\r\n", 14) = 14
11:23:04.153298 time(NULL) = 1154532184
11:23:04.153442 select(1, [0], NULL, NULL, {360, 0}) = 1 (in [0], left
{360, 0})
11:23:04.153619 time(NULL) = 1154532184
11:23:04.153779 time(NULL) = 1154532184
11:23:04.153902 read(0, "RCPT To:<[EMAIL PROTECTED]>\r\n"..., 4096) = 70
11:23:04.154068 time([1154532184]) = 1154532184
11:23:04.154215 write(8, "<1154532184<", 12) = 12
11:23:04.154364 write(8, "RCPT To:<[EMAIL PROTECTED]>\r\n"..., 70) = 70
11:23:04.154539 open("/var/lib/imap/msg/shutdown", O_RDONLY) = -1 ENOENT
(No such file or directory)
11:23:04.154809 select(7, [6], NULL, NULL, {0, 0}) = 0 (Timeout)
11:23:04.155000 write(6,
"\0\0\0:\305\"K\341U\326w:u4\273hx\263\274\363\374\246\24"..., 62) = 62
11:23:04.155671 time(NULL) = 1154532184
11:23:04.155818 read(6,
"\0\0\0\246\205\3669\356\212\360\351S\260t\305\233\274@"..., 4096) = 170
11:23:04.156045 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
I'll try to post a backtrace of a crashing lmtpd process as soon as I
can, but does anyone hav
Re: the autocreate feature (Cyrus IMAPd 2.3.7 Released)
Hi all. I have seen this issue come up several times in the info-cyrus list. The answer to the question 'why isn't autocreate included in the cyrus distribution' is 'because it does not support the murder architecture'. The CMU developers do very well not to accept a patch that does not work with all possible configurations, since if they did otherwise, that would lead to a maintance nightmare. However, as mentioned before, the patch existed before murder was released, but no one knows why it was not included then. Other than murder support, the autocreate patch is perfectly compatible and well tested with unix hierarchy separator, alternate namespaces and virtual domains. I am pretty much sure that it works with cyrus replication, although it is not tested yet and I have no reports by anyone playing with autocreate and replication code. All these are documented in the README.autocreate file distributed with the patch. (It can also be found here: http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.3) So, anyone who does not deploy a murder setup can use the autocreate patch. The next question that comes to everyone is 'why don't you implement murder support for the autocreate patch?'. The answer is 'because it is not so easy to do it'. Actually, implementing such a feature for a murder environment is not simply a matter of writing some code. Serious design decisions have to be taken. For example: - If a client contacts a front end, who decides in which backend should the mailbox be created? - How should the frontend iniate a mailbox creation procedure to a specified backend? - What should happen in every different murder scenario (standard, unified, replicated)? Especially when some architectures like replicated murder are not so well tested yet. - The MUPDATE protocol (http://www.ietf.org/rfc/rfc3656.txt) may need some extentions/modifications to support the autocreate patch. Modifying an IETF RFC requires responsible decisions that can't be taken by a single developer. One may understand, that there are two approaches to solving the above issues. The 'quick and dirty hack' approach, which would have some config variables for some of the above decisions. A patch like that could be produced in a few weeks time. On the other hand, there could be a well designed, scalable solution that would have some inteligence (ie different groups of user mailboxes are created in different backends, the mupdate server performs load balancing in mailbox creation). Since we, at the University of Athens do not use a murder enviroment and it is not one of our priorities either, we would go on implementing it only if the final result would be a well designed, extensible piece of code that would lead to integrating the patch into the main distribution. In the past there were some efforts in the cyrus-devel list to start discussing an initial approach for the support of murder by the patch. However, they did not lead anywhere, as the patch was not within the priorities of the CMU developers. See threads: http://email.uoa.gr/archive/message.php?mailbox=Software.cyrus-devel&searchterm=autocreate&msg=1048 http://email.uoa.gr/archive/message.php?mailbox=Software.cyrus-devel&searchterm=autocreate&msg=1585 Ever since this issue comes up from time to time but no progress has been made. I hope this email answers some of the questions asked in this thread. However, what I want to ask is the following: What happens next? Since both the CMU and the UOA developers are too busy with their own priorities, can the cyrus community make some development work? Are there any people determined to work as a team and do some work on cyrus? And by this I mean, a true development cycle, which requires collecting all feature requests, prioritising them, presenting a decent feature roadmap, discussing design of the featues, distributing development responsibilities and finally making sure that the patches are pushed into the main distribution. Of course, that requires an active community that is supported and encouraged by CMU, but above all it requires willing with programming skills and will to help.This would make cyrus work as lots of other opensource projects and would push the delivered product quality really high. That should be a priority for all cyrus developers, users. Lastly, in the past there were some efforts to create this sort of community, starting with work in the also much discussed cyrus documentation via the cyrus wiki. However, this effort did not evolve and cyrus is still poorly documented. Cheers, Christos Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate patch wrongly created?
You are right Andreas. It seems that accidentally, the .orig files that the patch command created, were included in the patch. I will publish new patches for cyrus 2.3.3 and cyrus 2.3.5 soon. Thanks for pointing this out. Cheers, Christos Andreas Hasenack wrote: > The autocreate patch available at > http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.3/ seems to be wrong, > it's > 380Kbytes in size and adds some .orig files. > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: auto create features
I am not sure, but I guess you have already created the user inbox before posting the email to the account. However, by design autocreate patch does not function this way. In order the create on post feature of the autocreate patch be activated, no account at all must be pre-exist. If the mailbox has been already created, then the patch is not activated at all. This is probably the reason for not seeing any log messages. Below I cite the conditions required in order the create on post functionality to be activated: Create on post == This feauture provides automatic creation of a user's INBOX folder when all of the following requirements are met. i) An e-mail message addressed to the user has been received. ii) The recipient is not any of the imap_admins or admins accounts. Note that passing e-mails to admins or imap_admins accounts from the MTA to LMTP should be avoided in any case. iii) The recipient's INBOX does not exist. iv) The "autocreatequota" option in the imap configuration file has been set to a non zero value. v) The "createonpost" option in the imap configuration file has been switched on. The above text was taken from the patch's documentation at: http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 I hope this clears the situation out. Cheers, Christos Craig White wrote: On Fri, 2006-04-07 at 13:19 +0300, Christos Soulios wrote: When autocreate fails, it logs the error message to your syslog. (be sure you do not filter out warnings). The patch for cyrus-2.3.x also logs debug info to check if the patch was invoked. Unfortunately debug info are not printed for cyrus 2.2.12. Cheers, Christos Craig White wrote: I am using Simon's rpm's on a CentOS 4 system... # rpm -q cyrus-imapd cyrus-imapd-2.2.12-16 my /etc/imapd.conf includes... configdirectory: /var/lib/imap partition-default: /var/spool/imap admins: cyrus sievedir: /var/lib/imap/sieve sendmail: /usr/sbin/sendmail hashimapspool: true lmtp_downcase_rcpt: 1 createonpost: 1 autocreateinboxfolders: Sent Items|SPAMBOX|VIRUSBOX|Drafts|Deleted Items autosubscribeinboxfolders: Sent Items|SPAMBOX|VIRUSBOX|Drafts|Deleted Items autosubscribesharedfolders: public|user.ratesheets autocreatequota: 512000 autocreate_sieve_script: /var/lib/imap/autocreate/default_sieve_script autocreate_sieve_compiledscript: /var/lib/imap/autocreate/default_sieve_script.bc generate_compiled_sieve_script: 1 allowallsubscribe: 1 anysievefolder: 1 and on other systems where I have done this, the auto features (autocreateinboxfolders, autosubscribeinboxfolders, etc.) all work. The features used to work here but seemed to have stopped working and I don't know why - which is why I upgraded last night. Is there a way I can 'trace' where things are breaking down on the 'autocreate' features when I create a new mailbox and send the first email to the new mailbox? that's just it...I'm not seeing log of significant info. here is the maillog... # account created... Apr 7 10:05:41 srv1 master[15542]: about to exec /usr/lib/cyrus-imapd/imapd Apr 7 10:05:41 srv1 imap[15542]: executed # mail automatically generated... Apr 7 10:05:41 srv1 postfix/pickup[14853]: C530DF8DC0: uid=76 from= Apr 7 10:05:41 srv1 postfix/cleanup[14961]: C530DF8DC0: hold: header Received: by srv1.myhomelenders.net (Postfix, from userid 76)??id C530DF8DC0; Fri, 7 Apr 2006 10:05:41 -0700 (MST) from local; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> Apr 7 10:05:41 srv1 postfix/cleanup[14961]: C530DF8DC0: message-id=<[EMAIL PROTECTED]> Apr 7 10:05:41 srv1 MailScanner[14598]: New Batch: Scanning 1 messages, 842 bytes Apr 7 10:05:43 srv1 MailScanner[14598]: Virus and Content Scanning: Starting Apr 7 10:05:43 srv1 imap[15203]: accepted connection Apr 7 10:05:43 srv1 master[15560]: about to exec /usr/lib/cyrus-imapd/imapd Apr 7 10:05:43 srv1 master[15561]: about to exec /usr/lib/cyrus-imapd/imapd Apr 7 10:05:43 srv1 imap[15560]: executed Apr 7 10:05:43 srv1 imap[15561]: executed Apr 7 10:05:43 srv1 imap[15203]: login: localhost.localdomain [127.0.0.1] cyrus plaintext User logged in Apr 7 10:05:47 srv1 MailScanner[14598]: Requeue: C530DF8DC0.A2DE3 to 16CC0F8DB8 Apr 7 10:05:47 srv1 MailScanner[14598]: Uninfected: Delivered 1 messages Apr 7 10:05:47 srv1 postfix/qmgr[6603]: 16CC0F8DB8: from=<[EMAIL PROTECTED]>, size=848, nrcpt=1 (queue active) # autocreate_sieve_compiled_script should have been copied but didn't... Apr 7 10:05:47 srv1 lmtpunix[14976]: IOERROR: fstating sieve script /var/lib/imap/sieve/t/test2/defaultbc: No such file or directory Apr 7 10:05:47 srv1 lmtpunix[14976]: duplicate_check: <[EMAIL PROTECTED]> user.test2 0 Apr 7 10:05:47 srv1 lmtpunix[14976]: mystore: starting txn 2147486686 Apr 7 10:05:47 srv1 lmtpunix[14976]: mystore: committing txn 2147486686 Apr 7 10:05:47 srv1 lmtpunix[14976]: d
Re: auto create features
When autocreate fails, it logs the error message to your syslog. (be sure you do not filter out warnings). The patch for cyrus-2.3.x also logs debug info to check if the patch was invoked. Unfortunately debug info are not printed for cyrus 2.2.12. Cheers, Christos Craig White wrote: > I am using Simon's rpm's on a CentOS 4 system... > > # rpm -q cyrus-imapd > cyrus-imapd-2.2.12-16 > > my /etc/imapd.conf includes... > > configdirectory: /var/lib/imap > partition-default: /var/spool/imap > admins: cyrus > sievedir: /var/lib/imap/sieve > sendmail: /usr/sbin/sendmail > hashimapspool: true > lmtp_downcase_rcpt: 1 > > createonpost: 1 > autocreateinboxfolders: Sent Items|SPAMBOX|VIRUSBOX|Drafts|Deleted Items > autosubscribeinboxfolders: Sent Items|SPAMBOX|VIRUSBOX|Drafts|Deleted > Items > autosubscribesharedfolders: public|user.ratesheets > autocreatequota: 512000 > autocreate_sieve_script: /var/lib/imap/autocreate/default_sieve_script > autocreate_sieve_compiledscript: > /var/lib/imap/autocreate/default_sieve_script.bc > generate_compiled_sieve_script: 1 > allowallsubscribe: 1 > anysievefolder: 1 > > and on other systems where I have done this, the auto features > (autocreateinboxfolders, autosubscribeinboxfolders, etc.) all work. The > features used to work here but seemed to have stopped working and I > don't know why - which is why I upgraded last night. > > Is there a way I can 'trace' where things are breaking down on the > 'autocreate' features when I create a new mailbox and send the first > email to the new mailbox? > > Craig > > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus autocreate mailboxes
autocreate is not triggered when mailboxes are created by cyrus administrator. It is triggered when a user logs in or a mail is sent to the mailbox and the mailbox does not exist. Take a look at the patch documentation at http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 Cheers, Christos Mark Schwarz wrote: > Hi, > > i search for a way to autocreate "sub"mailboxes in cyrus imap 2.2.14! > My users are managed in Web-cyradm with a MySQL backend. > I have tried to patch the cyrus-ebuild on my gentoo server, that was > successful. > But with the options... > > ---zap--- > autocreateinboxfolders: sent|drafts|spam|templates > autosubscribeinboxfolders: sent|spam > ---zap--- > > nothing happened. > Only the INBOX is there if i try to add a user through web-cyradm. > Did I make an error? > > Thanks > P. Schwarz > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate inbox patch..
You have to define the autocreate_sieve_script option in you imapd.conf too. Both the binary compiled and text script are needed. Cheers, Christos Andrzej Kwiatkowski wrote: > Hello > I would like to use this patch for Cyrus 2.3.1, > but i dont want it to create folders, but only to create default > INBOX but only to automating creating sieve scripts. > I'm using autosieve folder patch too. > > Now i setup my imapd.conf in this way: > > autosievefolders: spam > autocreate_sieve_compiledscript: > /opt/cyrus/imapd-2.3.1/etc/default_sieve_script.bc > > I can create inbox automaticly, because of quota setting which is > different > for each user. > > When user is logging to cyrus, there is no sieve script inside. > > Have got any idea ? > > Thanks > AK > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.1 RPM for RedHat/Fedora Core Released
Then it is quite unlikely that it is autocreate patch's fault since: 1. The patch is disabled 2. Mailbox exists 3. lmtpd is not involved in the delivery To be on the safe side, check your logs. Cyrus logs by default in local4 facility (I am not sure if Simon has or has not changed it in his rpms). In that case you should add the following line in your syslog.conf local4.* /var/log/imapd.log Christos Mitja Sladovic wrote: > HI, > > createonpost is disabled and mailbox exists. > Hm, if I use LMTP, then mail is delivered just fine... > > How can I enable debug level? > Putting mail.* in syslog.conf doesn't show anything more... > > Mitja > > Christos Soulios pravi: >> Hi, >> I would like to check out if it is the autocreate patch's fault for >> this >> situation. >> >> So, do you have the createonpost option enabled in your imapd.conf >> Do >> you get the same error if you disable it? Does the mailbox to which you >> deliver the mail exist or is it created at that time? >> >> Could you please enable debug level in the syslog and send the relevant >> lines in your syslog? >> > > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus IMAPd 2.3.1 RPM for RedHat/Fedora Core Released
Hi, I would like to check out if it is the autocreate patch's fault for this situation. So, do you have the createonpost option enabled in your imapd.conf Do you get the same error if you disable it? Does the mailbox to which you deliver the mail exist or is it created at that time? Could you please enable debug level in the syslog and send the relevant lines in your syslog? Cheers, Christos Mitja Sladovic wrote: > Simon Matter pravi: >> I am pleased to announce the release of Cyrus IMAPd 2.3.1 as Invoca RPM >> designed for RedHat/Fedora Core based distributions. The RPM builds on >> > > Simon, thanks for your work! > I have one problem :) > > After RHEL4 box upgrade (2.2.12) to 2.3.1, deliver crashes with sig 11... > > Jan 24 10:01:21 mail postfix/pipe[25836]: 40F23C0002: to=<[EMAIL PROTECTED]>, > relay=cyrus, delay=0, status=deferred (Command died with signal 11: > "/usr/lib/cyrus-imapd/deliver") > > Somebody with the same problem? > > Mitja > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[PATCH] autocreateinbox for Cyrus IMAPd 2.3.1
Dear all, I am pleased to announce the release of the autocreate inbox patch (version 0.10-0) for Cyrus IMAPd 2.3.1 This release is mostly a port of the patch to Cyrus IMAPd 2.3.1. Moreover, a new imapd.conf option (autocreate_users) has been added to restrict the users and/or groups whose mailboxes are created. For more information please visit the patch's web page at: http://email.uoa.gr/projects/cyrus/autocreate/ The patch may be downloaded from: http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.1/cyrus-imapd-2.3.1-autocreate-0.10-0.diff For questions and comments contact information is available at: http://email.uoa.gr/contact/ Best regards, Christos Soulios -- Did you visit http://email.uoa.gr? -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[PATCH] autosievefolder for Cyrus IMAPd 2.3.1
Dear all, I am pleased to announce the release of the autosievefolder patch (version 0.6-0) for Cyrus IMAPd 2.3.1 This release is purely a port of the patch to Cyrus IMAPd 2.3.1. The patch may be downloaded from: http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.1/cyrus-imapd-2.3.1-autosievefolder-0.6-0.diff For more information please visit the patch's web page at: http://email.uoa.gr/projects/cyrus/autosievefolder/ For questions and comments contact information is available at: http://email.uoa.gr/contact/ Best regards, Christos Soulios -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: ETA on auto-* patches?
Hello, just for your information, I have finished with porting the autocreate inbox patch and I plan to release it until the end of the week. I am just doing some final tests at the moment. I am sorry for the terrible delay for releasing the patches for cyrus 2.3.1. Unfortunately no support for mupdate is included in this release either. Regards, Christos Andreas Hasenack wrote: > On Wed, Jan 11, 2006 at 10:33:35AM -0200, Andreas Hasenack wrote: >> Any ETA on the auto-* patches for cyrus-imapd-2.3.x? Days? Weeks? Months? Don't know? >> I could start hacking on them, I guess, just didn't want to duplicate work. > > Attached is some *preliminary* work. It most certainly has bugs, doesn't even try to think about cyrus murder or replication, it may have security problems, blow up your machine, etc. I just took the original patches, made them apply and fixed the most obvious api changes so that it builds. > > I tested anysievefolder and autoinbox creation so far. > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html -- Did you visit http://email.uoa.gr? -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate folder for plus addressing?
Hi, for sure the autocreate patches do not implement such a feature. The autosievefolder patch (http://email.uoa.gr/projects/cyrus/autosievefolder/) implements creation of the folders used for the "file into" command of the sieve filters, but sieve is absolutely necessary for that. Regards, Christos Scott Russell wrote: > Greets. > > With Cyrus 2.3.1 (or the auto create patches?) can folders automatically > be created for plus addressing? > > I was toying with the idea of having tagged spam being sent to > [EMAIL PROTECTED] rather than using a sieve script. Since sieve > scripts are user editable using plus addressing to sort tagged spam into > a folder seemed like a more sensible idea. > > Maybe I'm on crack? > > -- > Scott Russell <[EMAIL PROTECTED]> > IBM Linux Technology Center > > > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: 2.2 and 2.3 imapd
I fell into the same bug and from what I found using gdb was that after a
SELECT command, the function cmdloop() of imapd calls proxy_check_input().
Then the following function calls are performed :
proxy_check_input() -> prot_read() -> prot_fill() -> read()
Then read() blocks while waiting from input from the backend. This results
in blocking the whole imapd.
I am not sure what kind of input from the backend should be waited for. I
tried changing the configuration several times but no success.
Christos
Mark wrote:
> Hello,
>
> There is a 2.2-imapd (2.2.12) murder enabled environment (front ends,
> murder master, back ends) working nice, and so I set up another front
> end with the 2.3 cvs code for testing. After setting it all up, I'm
> having problems fetching mail through it. What happens is, a mail
> client (tried mutt and Thunderbird) connects to 2.3 proxy fine,
> authenticates, and then fetches INBOX and gets stuck, mail headers
> never arrive. I'm a bit out of ideas, and in fact wanted to know if
> this kind of setup should work, and if it is recommended at all. If it
> should work, and anyone has an idea where I should look, that would be
> great help. And if not, what is a good way to upgrade to 2.3?
>
> Here are cyrus logs from both 2.3 front end that gets stuck, and also a
> working one (2.2.12) just in case it helps.
>
> Lines will probably be broken..
>
> - start 2.3 that gets stuck -
>
>>1119119387>a0003 OK User logged in
> <1119119387>1119119387>* LIST (\Noselect) "/" ""
> a0004 OK Completed (0.000 secs 0 calls)
> <1119119387>1119119387>* FLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk
> $MDNSent)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk
> $MDNSent \*)
> ]
> * 831 EXISTS
> * 0 RECENT
> * OK [UNSEEN 827]
> * OK [UIDVALIDITY 1101173713]
> * OK [UIDNEXT 18056]
> a0005 OK [READ-WRITE] Completed
>
> - end of 2.3 -
>
>
>
> - start 2.2 that works ok -
>
>>1119116500>a0003 OK User logged in
> <1119116500>1119116500>* LIST (\Noselect) "/" ""
> a0004 OK Completed
> <1119116500>1119116500>* FLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk
> $MDNSent)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen Junk
> $MDNSent \*)
> ]
> * 833 EXISTS
> * 0 RECENT
> * OK [UNSEEN 827]
> * OK [UIDVALIDITY 1101173713]
> * OK [UIDNEXT 18053]
> a0005 OK [READ-WRITE] Completed
> <1119116500>1119116500>* MYRIGHTS INBOX lrswipcda
> a0006 OK Completed
> <1119116500 BODY.PEEK[HEAD
> ER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
> IN-REPLY-T
> O REPLY-TO LINES X-LABEL)])
>>1119116500>* 1 FETCH (FLAGS (\Answered \Seen) UID 8 INTERNALDATE
> "16-Dec-2004 1
> 0:14:28 -0500" RFC822.SIZE 1765 BODY[HEADER.FIELDS (DATE FROM SUBJECT
> TO CC MESS
> AGE-ID REFERENCES CONTENT-TYPE IN-REPLY-TO REPLY-TO LINES X-LABEL)]
> {268}
> Message-ID: ...
> [ and so on, it fetches it all ]
>
> - end of 2.2 log -
>
> Thanks for any help and pointers.
>
> Mark
>
>
>
>
> Yahoo! Sports
> Rekindle the Rivalries. Sign up for Fantasy Football
> http://football.fantasysports.yahoo.com
> ---
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
--
Did you visit http://email.uoa.gr?
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate inbox and cyrus-imapd for freebsd 5.4
Perhaps the following thread from the UoA email archives can help you http://email.uoa.gr/archive/message.php?mailbox=email&msg=225 http://email.uoa.gr/archive/message.php?mailbox=email&msg=245 Christos Ivan R. Sy Jr. wrote: > hi all, > > ive been battling with installing cyrus-imapd22 from ports with the > autocreate inbox patch > > http://email.uoa.gr/projects/cyrus/autocreate/ > > on a FreeBSD 5.4. > > ive contated the port maintainer, no reply so far. and im just asking here > if anyone knows how to patch the port distribution. > > i really want to use the port coz there are a lot of patches that would > fit for my system thats prebuilt in that freebsd port, ive done a binary > install, autocreate works great but i need it to work with the port > > have anyone done any patching to the cyrus-imapd22 freebsd port? > how? > > thanks > > > --- > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus Banner
>From what I can see from the source code, there is no way of removing the cyrus banner. (except patching cyrus) Christos Christian Cernuschi wrote: > Sorry for stupid question but google didn't help me. > How can i remove Cyrus Banner? > > I would like to remove Name and version. > Thank You > > Christian > > --- > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Unified mupdate status in Cyrus 2.3
Hi all, currently I am trying to setup a Cyrus 2.3 testing environment using the unified mupdate architecture. Since documentation on unified mupdate is very scarce both in cyrus lists and cyrus documentation, I would like to ask the following : - What is the status of the code for unified murder in Cyrus 2.3? (I suspect this can be best answered by the cyrus developers) - Is there anyone who managed to set it up and has some testing results regarding stability? - Are there any sample imapd.conf and cyrus.conf files or some config options that need extra attention before setting it up? Thanks in advance for your help, Christos -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate question
Paul Dorneanu wrote: > Hi. > I've setup the autocreate patch for 2.2.12 and using virtdomains > > It doesnt work properly on post... it creates the inbox > /var/spool/imap/t/user/test/ for a nondefault domain. > > but, on login it creates the proper inbox... > ./var/spool/imap/domain/n/nondefaultdomain.tld/t/user/test/ > > How can I make that it createsonpost work properly? > I just doublechecked it in my testing environment and the patch seems to work as expected. The mailbox is created under /var/spool/imap/domain/n/nondefaultdomain.tld/user/test in both cases. Is there any more information (logs, imapd.conf) you can provide in order that I can look further? > > Another question is... > when I login from squirrellmail I get this error: > *ERROR:* * ERROR : Could not complete request.* > Query: CREATE "Sent" > Reason Given: Permission denied > > I understand that it wants to create the Sent folder and it doesn't have > enough permissions. One work-around is to auto-create the sent folder on > mailbox creation. What permisions are we talking about for letting it to > create the folders in a user's box? The user always has the c permission on her own Inbox. In that case the INBOX.Sent folder may be created. What I suspect is that the INBOX folder has not yet been created and thus INBOX.Sent cannot be created. For more information on Squirrelmail INBOX creation functionality, perhaps you should refer to the squirrelmail mailing lists. On the server side the autocreate inbox patch is surely the way to do this. Christos > --- > Cyrus Home Page: http://asg.web.cmu.edu/cyrus > Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Can't create virtual domain mailboxes
The autocreate patch is fully functional when using virtual domains. Your imapd.conf seems to be ok. Nevertheless, autocreate is triggered when a user logs in and the inbox does not exist. In any case, it does not work when cyrus administrator creates the mailbox using cyradm. Christos Robin Rainton said: admins: cyrus [EMAIL PROTECTED] [EMAIL PROTECTED] autocreatequota: 10240 autocreateinboxfolders:Sent Items|Trash|Drafts autosubscribeinboxfolders:Sent Items|Trash|Drafts sasl_pwcheck_method: auxprop sasl_auxprop_plugin: sasldb virtdomains: userid unixhierarchysep: yes loginrealms: domain1.com domain2.net Additionally, the auto... options aren't working, do these not apply to virtual domains? Known bug? Again, my dumbass config? -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: DB Errors [SOLVED]
Hi again Daniel. I just saw that you use cyrus-imapd-2.2.10, packaged in YDL 4.0. And this bug has been fixed in autocreate patch for cyrus-2.2.10 for quite sometime. The autocreate patch for cyrus-imapd-2.2.10 (patch versions 0.9.0 & 0.9.1) checks userinbox variable and does not sefault. + +if(rcpt_userid == NULL) + return IMAP_MAILBOX_NONEXISTENT; + So what I can think of are the following : 1. Your distro did not include this fix in the distributed cyrus package. 2. Segfault is caused by something else. Please check your sources and let me know if I can do something to fix it. Regards, Christos Daniel Hazelbaker said: Okay, after knocking down our mail server for an hour to track this down I have a solution. I do not remember where, but somewhere when I was setting this up years ago I read that the method for delivering from postfix->procmail->spamassassin->cyrus was to have postfix deliver to procmail, and procmail instruct spamassassin to do its thing. Then to use the cyrus deliver program with "-a $LOGNAME -m user.$LOGNAME" to deliver the message. Well what was happening is this: Breakpoint 1, verify_user (user=0x0, domain=0x0, mailbox=0x100f8189 "user.kristina", quotacheck=0, authstate=0x0) at lmtpd.c:554 This combination (user = null and mailbox != null and mailbox does not exist) would cause verify_user to pass userinbox (== null) to autocreate_inbox, which would strcmp without any error checking and segfault. The solution seems to be to change the deliver line to just "-a $LOGNAME $LOGNAME" and it seems to work properly for everything. Daniel Hazelbaker On Apr 26, 2005, at 4:45 PM, Daniel Hazelbaker wrote: > I don't believe it is no symbols, I believe it is smashing the stack > somehow (those are the only two entries in the stack). Can't imagine > how strcmp is smashing the stack but I suppose anything is possible. > I'll try to attach, but I thought lmtpd forked a child process in the > same way httpd does, maybe not though. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Autocreate bug fixed (was Re: DB Errors [SOLVED])
Hi Daniel, Ok I found the problem. It is really autocreate's fault. I bet you use a 2.1.x version of cyrus, because in cyrus 2.2.12 it is already fixed. Now it is fixed in 2.1.18 too (patch version 0.9.4). Get it from http://email.uoa.gr/download/cyrus/cyrus-imapd-2.1.18/ Regards, Christos Daniel Hazelbaker said: Okay, after knocking down our mail server for an hour to track this down I have a solution. I do not remember where, but somewhere when I was setting this up years ago I read that the method for delivering from postfix->procmail->spamassassin->cyrus was to have postfix deliver to procmail, and procmail instruct spamassassin to do its thing. Then to use the cyrus deliver program with "-a $LOGNAME -m user.$LOGNAME" to deliver the message. Well what was happening is this: Breakpoint 1, verify_user (user=0x0, domain=0x0, mailbox=0x100f8189 "user.kristina", quotacheck=0, authstate=0x0) at lmtpd.c:554 This combination (user = null and mailbox != null and mailbox does not exist) would cause verify_user to pass userinbox (== null) to autocreate_inbox, which would strcmp without any error checking and segfault. The solution seems to be to change the deliver line to just "-a $LOGNAME $LOGNAME" and it seems to work properly for everything. Daniel Hazelbaker On Apr 26, 2005, at 4:45 PM, Daniel Hazelbaker wrote: > I don't believe it is no symbols, I believe it is smashing the stack > somehow (those are the only two entries in the stack). Can't imagine > how strcmp is smashing the stack but I suppose anything is possible. > I'll try to attach, but I thought lmtpd forked a child process in the > same way httpd does, maybe not though. --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: change default mailbox names
If your server is patched with the autocreate inbox patch, then you can configure the names of the INBOX subfolders in imapd.conf by the "autocreateinboxfolders" configuration option. (eg autocreateinboxfolders: Sent | Drafts | Trash) For more information on the configuration parameters of autocreate inbox patch, please see : http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.1 Regards, Christos Ken Murchison said: Nick Trenary wrote: > At 03:20 PM 4/20/2005, Derrick J Brashear wrote: > >> On Wed, 20 Apr 2005, Nick Trenary wrote: >> There answer may be "no" but unless you give an example of what you mean it's hard to know what you're really asking for. >>> >>> >>> The default mailbox names created are Inbox, Deleted Messages, >>> Drafts, and Sent Messages. I want to shorten the names to something >>> like Inbox, Trash, Drafts and Out(box) respectively if I can. >> >> >> inbox is a synonym for user.(you). >> the rest are presumably being created by the client. if you want the >> client to create something else, well, you need to pervert the client >> to do so. what client? > > > I don't think so. I created to users, I logged in initially as user1 in > Eudora and user2 in Squirrelmail. Both had the same folder names > created. That leads me to believe it is in cyrus somewhere. My > imapd.conf doesn't mention the mailbox names anywhere. Nope. As one of the maintainers of Cyrus, I'll repeat what others have told you. An unmodified Cyrus server does NOT create any mailboxes on its own. An admin has to create the INBOX (user.) and any other mailboxes are usually created by the client (either explicitly or implicitly by the user). There is an "autocreate" patch for Cyrus floating around which can be configured to create additional mailboxes when an admin creates an INBOX. You might want to see if your source/distro has been patched. -- 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 --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: auth ldap, creating folders automatically for new users
Because current patch implementation is not compatible with MURDER architecture. It is within our intentions to make the patch complete and finally have it included in the main cyrus source tree. Regards, Christos Thomas Bolioli said: This has probably been covered before but why is this still a patch and not a bona fide option in the main distribution? It seems like it is something many people would want. I know I do at least. Tom Andreas Hasenack wrote: >On Mon, Apr 25, 2005 at 01:34:05PM +0200, Sueveges Gyoergy wrote: > > >>Hi all, >> >> I use LDAP for authentication to cyrus (actually for saslauthd). I >>noticed when there is a new user on my ldap, altough I can login to >> cyrus, >>there are no folders created. I think it is the default behaviour of >>cyrus. How can I change it so that also folders (inbox, sent,..) are >>created? >> >> > >You need to apply the autocreate patch from >http://email.uoa.gr/projects/cyrus/autocreate/index.php > >--- >Cyrus Home Page: http://asg.web.cmu.edu/cyrus >Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu >List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > > -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
CVSweb problem
Hi all There seems to be a problem with cvs web, because during the last month every link to a diff from the cyrus-cvs list is broken. Could it be fixed because this feature is very useful for monitoring changes in the Cyrus souces. Regards, Christos -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: lmpt/quota behaviour
Indeed, lmtpd checks for the quota immediately on delivery. There should be no delay in updating for the quota change. Christos Ken Murchison wrote: Per olof Ljungmark wrote: Hi all, I'm running a test setup and today I tried setting the quota for a mailbox below the current size of it to see what happened. No surprise, lmpt started responding "452 4.2.2 Over quota" as it should. Then I increased the quota again so that there were plenty of room, waited for the 452 response to go away but it did not. After an hour I restarted the lmtp process and the account accepted mail again. Q: How long should it normally take for lmtp to see the changes? The change TO "Over quota" was registered instantly but the not the opposite apparently. Can this time be adjusted? I believe lmtpd should be checking the quota for each RCTP TO that it receives, but I'd have to check. It *should* see the change immediately. I know the test scheme was perhaps not a real world one but should not an account be able to accept mail more or less immideately after the quota is fixed? 2.2.10 with patches from UOA. Thanks, --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[PATCH] Autosievefolder patch
A new release (version 0.5) for the autosievefolder patch is out. The new version fixes the wrong handling of alternate namespaces. Bug reported by Erik de Zeeuw. The new version can be downloaded from : http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.10/ and http://email.uoa.gr/download/cyrus/cyrus-imapd-2.1.17/ For more information please visit the patch's homepage at http://email.uoa.gr/projects/cyrus/autosievefolder/ Finally, I would like to thank Simon Matter and Erik de Zeeuw for thoroughly testing the patch and the excellent feedback we received from them. Regards, Christos -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: automated delivery of sieve scripts for new users
Craig White wrote: I believe that you are correct on the patch level but interestingly enough, it doesn't complain if I include any of the following directives in /etc/imapd.conf autocreate_sieve_script: /etc/default_sieve_script autocreate_sieve_compiledscript: /etc/default_sieve_script.bc generate_compiled_sieve_script: 1 Cyrus would not complain neither if it supported these options, nor if it did not supported them. I don't think I've tried all of the combinations of them yet but they don't appear to work. The above configuration is correct as long as the files are valid sieve scripts and readable by cyrus. Moreover, the patch is executed only when there is no user mailbox and the user logs into the system. And not when you create the mailbox using cyradm or other administering tool. and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder there is no mention of those items. Autosieve folder patch is a different patch from autocreate inbox/sieve. It implements the creation of a folder upon file_into command from a sieve script. Perhaps you should read the README.autocreate file for more information in these options or read the following links : http://email.uoa.gr/projects/cyrus/autocreate http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2 I appreciate your offer of the packages and note that apparently fedora-3 is using some derivative of your packages since I recall seeing the name on some file they distribute. I am going to try to stick with that which is distributed by fedora package for automated updates, etc. and so that really leaves me option 2 - which isn't so terrible since I have the bytecoded script in hand and I will script new users anyway. I believe that Simon's patches are very stable and always uptodate against security and bug fixes. So I am sure, you should try them. I might put in a bugzilla entry into fedora though... Regards, Christos --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
[PATCH] New release of the autocreate inbox patch
Hello and happy new year from Athens - Greece. I am pleased to announce the new releases of the autocreate inbox patch for cyrus-imapd 2.1.17 and 2.2.10. Patches can be downloaded from their homepage : http://email.uoa.gr/projects/cyrus/autocreate Both patches contain the autosubscribe_all_sharedfolders config option and the much wanted autocreate sieve script feature. Autocreate sieve script feature enables cyrus admins to define a sieve script that will be automatically become the user's default sieve filter upon INBOX creation. Special thanks go to Simon Matter for his invaluable contribution in testing and submitting some critical bugs. For anything related to the patches please contact the developers through : http://email.uoa.gr/contact Regards, Christos -- Did you visit http://email.uoa.gr? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: virtdomains and autocreateinboxfolders not working!! -SOLVED
Matt Goebel wrote: After some further investigation I've figured out a workaround/fix for this problem. Web-cyradm uses the function createmb() to create a new user's mailbox (located in ./lib/cyradm.php). This function uses "create" to create a user INBOX which works fine. The problem with this is that it that's all it creates, and once a user has a INBOX autocreateinboxfolders doesn't work. (It's triggered my either a new email or first login to an account without an INBOX). In order autocreateinbox to function, you must have absolutely no user mailbox created in your mailbox db. From what I can understand from your email, you try to create the user using cyradm or web-cyradm and then expect that all folders are created by the autocreateinbox patch. In this case you have no success with web-cyradm/cyradm because it logs in using cyrus admin account and creates the user mailbox. Then when the user logs in with his/her imap client, INBOX already exists and no further creation takes place. Using cyradm "create" from the command line the functionality it identical. However, if you use "cm" instead from cyradm it creates the INBOX and all subfolders set by autocreateinboxfolders. I suspect that when you login from console, using cyradm, you login using the user account and not cyrus administrator account. In this case the INBOX as well as subfolders are created by the autocreateinbox patch. That is why the create mailbox command fails. To fix this I changed "create" to "cm" in the createmb() function in cyradm.php. After testing it appears that makes the create mailbox command fail (no errors!?) In effect you could also just disable the call to this function in newaccount.php and it would have the same effect. So since the INBOX doesn't now exist... and the login info does... autocreateinboxfolders works as it's supposed to. You just need to have it and "createonpost: 1" in your imapd.conf file. On Wed, 2004-12-29 at 15:11 -0500, Matt Goebel wrote: After some testing this appears to be an issue with Web-Cyradm. Using cyradm it creates the folders. Any ideas? On Wed, 2004-12-29 at 12:51 -0500, Matt Goebel wrote: There's nothing in the log files that indicates a problem. If there was I'd probably be able to figure this one one. Autocreateinboxfolders just doesn't work. Here's the maillog entry for a new user logging in via squirrelmail though: I think I see something here : Dec 29 11:57:51 mail imap[14936]: login: localhost.localdomain [127.0.0.1] test2.testdomain.com plaintext User logged in From what I can see you are not logged in using a virtual domain account. Rather you use the account test2.testdomain.com account which qualifies as a default domain account. If you logged in using an other than default domain account, you should have seen the following line in your log. imap[8035]: login: localhost [127.0.0.1] [EMAIL PROTECTED] plaintext User logged in Dec 29 11:57:51 mail imap[14956]: accepted connection Dec 29 11:57:51 mail imap[14956]: login: localhost.localdomain [127.0.0.1] test2.testdomain.com plaintext User logged in Dec 29 11:57:51 mail imap[14956]: seen_db: user test2^testdomain^com opened /var/lib/imap/user/t/test2^testdomain^com.seen Dec 29 11:57:51 mail imap[14956]: open: user test2^testdomain^com opened INBOX The user test2.domain.com INBOX has been already created by web-cyradm and thus it is not created by autocreateinbox patch. On the contrary when you send an email using postfix, then the email is delivered to user [EMAIL PROTECTED] and the INBOX is normally created in /var/spool/imap/domain/l/localdomain/t/user/testuser.testdomain.com. Everything else is normal, if you accept my speculations. Regards and wishes for a happy new year, Christos Dec 29 11:57:52 mail last message repeated 2 times Dec 29 11:57:52 mail imap[14956]: SQUAT failed to open index file Dec 29 11:57:52 mail imap[14956]: SQUAT failed Dec 29 11:57:52 mail imap[14959]: accepted connection Dec 29 11:57:52 mail imap[14959]: login: localhost.localdomain [127.0.0.1] test2.testdomain.com plaintext User logged in Dec 29 11:57:52 mail imap[14959]: seen_db: user test2^testdomain^com opened /var/lib/imap/user/t/test2^testdomain^com.seen Dec 29 11:57:52 mail imap[14959]: open: user test2^testdomain^com opened INBOX/Trash Dec 29 11:57:54 mail imap[14956]: accepted connection Dec 29 11:57:54 mail imap[14956]: login: localhost.localdomain [127.0.0.1] test2.testdomain.com plaintext User logged in Dec 29 11:57:54 mail imap[14956]: open: user test2^testdomain^com opened INBOX/Drafts By default Squirrelmail creates the folders Drafts, Sent, and Trash when you log in. That isn't logged anywhere I can see. On Wed, 2004-12-29 at 01:49 +0200, Aristotelis wrote: On Tue, 28 Dec 2004, Matt Goebel wrote: No matter what I try I can been unable to get either virtdomains or autocreateinboxfolders working. Without virtdomains set (as shown Hi, could you please also paste the relevant part of
[PATCH] Autocreate inbox new release
I am pleased to announce the newest release of the autocreate Inbox patch. The new version (0.9.0) of the patch contains minor fixes such as some changes in syslog priorities various code cleanups, as well as some new features. The new features are : - autosubscribe_all_sharedfolders option in imapd.conf. When set to yes, then the user gets subscribed to all shared folders, provided one has the apropriate permissions. - autocreate_sieve_script functionality. Automatic creation of a sieve filter for a user, upon mailbox creation. Normally, this is used for creating default anti-spam sieve filters and force them as default filters. For more information and patch download, please visit : http://email.uoa.gr/projects/cyrus/autocreate This patch is already in production in the University of Athens and seems to behave quite stably. NOTE : Currently, the patch is released for Cyrus IMAPd 2.1.17 only. A patch for Cyrus 2.2.10 will be released within the following couple of days. Best regards, Christos --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate INBOX patch....
I do not think major changes are needed for the patch to work. However, it is our policy to release a new and tested patch for every cyrus release. We will try to have it ready pretty soon. Christos Didi Rieder wrote: will there be an autocreate INBOX patch for cyrus 2.2.10, or does the 2.2.7 patch work for the new release? Thanks Didi --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: a directory named "yes" is created
That is what I thought of too. Do you use Simon's RPM packages to install cyrus. Perhaps you have set autocreateinboxfolders option in imapd.conf to yes. Christos Simon Matter said: >> sorry searching the documentation and google proved difficult with this. >> >> Why would a directory called "yes" be created in every new mailbox. > > Looks like you have misconfigured some autocreate feature in imapd.conf. > > Simon > >> >> i.e. >> [pdc /var/spool/imap/domain/d/draftmail.org/r/user/robin]# ls -la >> total 28 >> drwx--3 cyrusmail 4096 Feb 8 21:56 . >> drwx--3 cyrusmail 4096 Feb 8 21:56 .. >> -rw---1 cyrusmail 719 Feb 8 21:56 1. >> -rw---1 cyrusmail 600 Feb 8 21:56 cyrus.cache >> -rw---1 cyrusmail 189 Feb 8 21:56 cyrus.header >> -rw---1 cyrusmail 136 Feb 8 21:56 cyrus.index >> drwx--2 cyrusmail 4096 Feb 8 21:56 yes >> >> >> This "yes" directory is created in every new mailbox. What is the >> purpose >> of this ? Have I possibly misconfigured something or is it normal? >> --- >> Home Page: http://asg.web.cmu.edu/cyrus >> Wiki/FAQ: http://cyruswiki.andrew.cmu.edu >> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html >> > > > --- > Home Page: http://asg.web.cmu.edu/cyrus > Wiki/FAQ: http://cyruswiki.andrew.cmu.edu > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > -- Did you visit http://email.uoa.gr? --- Home Page: http://asg.web.cmu.edu/cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sig11 with autocreate feature
Ok, I think I found it. It was a stupid segmentation fault, because I did not check a variable for being NULL. I hope I fixed it now. You can download it at http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.3/cyrus-imapd-2.2.3-autocreate-0.8.6.diff Thank you for reporting it Simon. I am waiting to learn if it works now. Regards, Christos Simon Matter said: >> Could I have a look at your imapd.conf file? > > Christos, > > I'm sorry for not providing imapd.conf. Here it is > > configdirectory: /var/lib/imap > partition-default: /var/spool/imap > admins: cyrus > sievedir: /var/lib/imap/sieve > sendmail: /usr/sbin/sendmail > hashimapspool: true > sasl_pwcheck_method: saslauthd > sasl_mech_list: PLAIN > tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem > tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem > tls_ca_file: /usr/share/ssl/certs/ca-bundle.crt > autocreatequota: 50 > createonpost: yes > > As you can see, nothing special. It has worked perfect with 2.1.x so > expect it to be just a small detail in the upgraded patches. > > Thanks for looking into it. > Simon > >> >> I would like to see what are the following options : >> >> autocreatequota >> >> createonpost >> autocreateinboxfolders >> autosubscribesharedfolders >> >> altnamespace >> >> I'll have a look at it asap. >> Christos >> >> >> Simon Matter said: >>> I just discovered a problem with the autocreate patches from >>> http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.3/ which have been >>> discussed today on this list. Since the maintainers of the patches also >>> read the list I think it's okay to mention this here. >>> When the createonpost feature is set, then a new mailbox is created if >>> a >>> mail is delivered to a non existent mailbox via lmtp. Now I discovered >>> that whenever I send mail with postfix to such a nonexistent mailbox, >>> the >>> box is created on the fly but the mail is not delivered until the next >>> time postfix flushes the queue. I tried to figure out what's going >>> wrong >>> but was unable to find it. An strace of the dying lmtpd process can be >>> found here >>> >>> http://invoca.ch/pub/packages/cyrus-imapd/cyrus-sig11.txt >>> >>> this is from the logs: >>> Feb 3 14:03:26 imap01 postfix/pickup[16538]: 6A94711E05: uid=0 >>> from= >>> Feb 3 14:03:26 imap01 postfix/cleanup[16850]: 6A94711E05: >>> message-id=<[EMAIL PROTECTED]> >>> Feb 3 14:03:26 imap01 postfix/nqmgr[16539]: 6A94711E05: >>> from=<[EMAIL PROTECTED]>, size=329, nrcpt=1 (queue active) >>> Feb 3 14:03:26 imap01 lmtpunix[16766]: autocreateinbox: User imaptest, >>> INBOX was successfully created in partition default >>> Feb 3 14:03:26 imap01 master[16752]: process 16766 exited, signaled to >>> death by 11 >>> Feb 3 14:03:26 imap01 postfix/lmtp[16851]: 6A94711E05: >>> to=<[EMAIL PROTECTED]>, >>> orig_to=<[EMAIL PROTECTED]>, >>> relay=/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp], delay=0, >>> status=deferred (lost connection with >>> /var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp] while sending MAIL >>> FROM) >>> >>> Thanks, >>> Simon >>> >>> >> >> >> -- >> Did you visit http://email.uoa.gr? >> > > > -- Did you visit http://email.uoa.gr?
Re: CYRUS = GARBAGE
In order the patch to function, the autocreatequota option at the imapd.conf file must have a non zero value. Then, when the mailbox is created, the autocreatequota value is set as the mailbox's initial quota. If the autocreatequota option is zero, then the patch disables itself. Regards, Christos Christian Schulte said: > Am Dienstag, 3. Februar 2004 10:50 schrieb Simon Matter: >> > Am Dienstag, 3. Februar 2004 01:53 schrieb Edward Rudd: >> >> That's not correct.. You can use mysql and have accounts >> automatically >> >> created.. >> >> If you install the autocreate patches.. >> >> http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.3/ >> > >> > I think you do not need to even patch 2.2.3 for this to work! >> >> For 'createonpost' and 'createonlogin', you need the patch AFAIK. I've included them in my rpms and they work pretty well. >> >> Simon > > I just took a look at the patches and I am wondering if they could replace the > autocreatequota: option which I am using right now. Do these patches support > creation of initial quota on user inboxes ? Just curious. > > -- > Christian > > -- Did you visit http://email.uoa.gr? -- Did you visit http://email.uoa.gr?
Re: Renaming users. Does it work ?
That was it. It seems to work fine now. Thanks Ken. Christos Ken Murchison said: > Christos Soulios wrote: > >> Hi list, >> >> Reading the Cyrus-2.2.3 FAQ I was glad to see the following statement: >> "renaming users - Supported, but try to make sure that the user is not, >> and can not login when doing the rename. Otherwise user-meta may get >> corrupted and/or out of sync." >> >> However, when I tried to rename a user, I got the error "NO Operation is >> not supported on mailbox" >> Am I doing something wrong or is something else running here? > > Enable the allowusermoves option in imapd.conf > > -- > 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 > -- Did you visit http://email.uoa.gr?
Renaming users. Does it work ?
Hi list, Reading the Cyrus-2.2.3 FAQ I was glad to see the following statement: "renaming users - Supported, but try to make sure that the user is not, and can not login when doing the rename. Otherwise user-meta may get corrupted and/or out of sync." However, when I tried to rename a user, I got the error "NO Operation is not supported on mailbox" Am I doing something wrong or is something else running here? A log of my IMAP session follows: * OK Cyrus IMAP4 v2.2.3 server ready . login cyrusadmin . OK User logged in . list user.christos * * LIST (\HasChildren) "." "user.christos" * LIST (\HasNoChildren) "." "user.christos.Drafts2" * LIST (\HasNoChildren) "." "user.christos.Sent" * LIST (\HasNoChildren) "." "user.christos.Trash" . OK Completed (0.000 secs 5 calls) . rename user.christos user.christos2 . NO Operation is not supported on mailbox Christos -- Your Cyrus is too tough to administer? Cyrusmaster is the solution for you. Visit http://email.uoa.gr/cyrusmaster now
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Quoting Rob Siemborski <[EMAIL PROTECTED]>: > On Fri, 2 Jan 2004, Christos Soulios wrote: > > > Rob Siemborski wrote: > > > On Fri, 2 Jan 2004, Paul Boven wrote: > > > > > > The only argument I currently completely understand for an IP-only based > > > setup is that of sites that need to distinguish ANONYMOUS users between > > > domains (and prehaps that is good enough). > > > > What about being able to determine the virtual domain based on the ip > > address and presenting different ssl certificate for each domain? Even > > presenting different host name, one that is in accordance to the ssl > > certificate. All this happens long before authentication. Right? This > > would be really nice to implement. > > You can do that in a model that still allows users to add an @ sign and a > domain to their userid. > I cannot figure out how this can be achieved. And to make it clear, I will give an example. I have two domains domain1.com and domain2.com which are hosted by the hosts imap.domain1.com and imap.domain2.com respectively. These two servers must have two different certificates with cn=imap.domain1.com and cn=imap.domain2.com When the user connects to the imap.domain1.com and long before the user authentication takes place, the cyrus must be able to present the correct certificate. Because most mail clients will not accept to connect to the imap host imap.domain1.com and be presented a certificate with cn=imap.otherdomain.com But how can cyrus be able to know which is the correct certificate to present? Of course, not by retrieving the domain by the userid suffix. Then it is too late. The authentication has already taken place. In my opinion this must have taken place by the time the user connects. And then the only way for cyrus to determine the correct virtual domain is _only_ using the ip address of the server interface. Am I right or am I missing something here? Christos > The only way to get a win out of a model that disallows that feature is to > come up with something where it actively causes problems. And the SASL > ANONYMOUS mechanism is about all I can currently see. > > -Rob > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 > Research Systems Programmer * /usr/contributed Gatekeeper >
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Rob Siemborski wrote: On Fri, 2 Jan 2004, Paul Boven wrote: The only argument I currently completely understand for an IP-only based setup is that of sites that need to distinguish ANONYMOUS users between domains (and prehaps that is good enough). What about being able to determine the virtual domain based on the ip address and presenting different ssl certificate for each domain? Even presenting different host name, one that is in accordance to the ssl certificate. All this happens long before authentication. Right? This would be really nice to implement. Christos -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Paul Boven wrote: Hi Christos, everyone, Security is a very important thing. And security to me means encryption, not only of the authentication phase but of the whole session. Now with HTTPS I know you loose the ability to support virtual domains, because the TLS session must be setup before the requested URL is transferred. This means you can only have one hostname per IP-adres as soon as you use SSL. Wouldn't you run into the same problem when enabling virtual domain support on cyrus? Well, I do not want to have a flame on this matter. Besides, it is beyond this thread what security is. To me your proposal is not about security, it is about content encryption. Encryption is just one aspect of security. I've deployed several single domain cyrus servers, but am working on my first multidomain one, with Squirrelmail via SSL on top. So the way things look now is that the machine will have only one hostname, imap.example.com, and that everyone logs in with their complete email-address as the fully qualified username, either with imaps or via https and squirrelmail. In short: I think we should keep the ability to allow users to provide fully qualified usernames. I totally agree with you. The ability to append the domain to the user id is already implemented. What I suggest is just another option, which suits my needs and I think that there will be others which will find it useful in the future. Regards, Paul Boven. -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Ken Murchison wrote: Christos Soulios wrote: If the domain passed in the fully qualified userid matches the domain selected from the ipaddress, then cyrus, proceeds to authenticate user using sasl. If it is different, then authentication fails without even making a query to the authentication mechanism. Can you explain why this matters. Are you limited certain domains to a particular interface for security reasons? I assumed that byaddr is just a convenience for the users. Security is one thing. More than this, my opinion is that in order cyrus to be deployed in a true multi domain environment, and thus actually be used by ISPs, admins must be able to distribute the virtual domains according to the name of the server, users are connecting to. In such a multi domain environment, users have no abillity to choose their domain by appending a @domain to their userid. However, now they can. Of course, one may argue that the same thing may be done using the correct authentication policy through sasl. This is true, but this sollution leaves part of the domain determination procedure to sasl. My opinion is that for the shake of complicity cyrus should handle this. Besides nobody needs the overhead of a sasl call, when cyrus can do the same thing. Moreover, being able to determine the virtual domain solely by the ip address the user was connected to, gives you - the cyrus developers - the option to know the domain before the user passes an authentication command to cyrus. I will give a short example which shows how useful this is. If my imap server hosts two virtual domains. And I happen to permit anonymous logins to only one of them. Having determined the domain before the user passes an authentication command, gives me the option to allow or deny an anonymous login. Of course, this is not something it can be implemented now. But I would like to see that too in some future release of cyrus. Trying to see a little bit further, dictates me that byaddr is not merely a convenience for users. It is a key feature to implement full virtual domains support in cyrus. How do you propose to handle admins, especially the global admin? Jure's proposal seems to make the most sense to me at this point (admins use fully qualified userids) Jure's proposal sounds fine to me too. With a small change. Which is that domain admins do not need to pass a @domain when they authenticate. In stead of this, the domain is determined upon connection - using the interface they connected to - and if the user is an admin of the virtual domain, is determined in same good old way it was determined in cyrus-2.1.x In the config file, of course the notation may be in the form of : admins: cyrus [EMAIL PROTECTED] [EMAIL PROTECTED] A different, cleaner (IMHO) implementation would be to have two config options. Something like: globaladmins: cyrus domainadmins: [EMAIL PROTECTED] [EMAIL PROTECTED] Regards, Christos -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Quoting Ken Murchison <[EMAIL PROTECTED]>: > > But authentication should fail in this case, unless the user's in two > different domains have the same userid and password. > Actually, I think that it is more efficient if cyrus-imap did all the virtual domains handling, without the assistance of any authentication mechanism. > Don't know. Rob and I wondered what would be the reasonable thing to do > if byipaddess was configured and a user used a fully qualified userid to > log in. If the domain passed in the fully qualified userid matches the domain selected from the ipaddress, then cyrus, proceeds to authenticate user using sasl. If it is different, then authentication fails without even making a query to the authentication mechanism. > Its not a problem to implement it. I'd like to get some more discussion > on how the two methods can/should interact. These methods are totally different and there is no reason/need for interacting. One method uses _only_ the userid to find out the user's virtual domain, the other one uses _only_ the host's ip address. Christos
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
This means that there is no choice for an administrator who might want to distribute users to the domains _only_ according to the IP address of the server that users connect to? I would not like my users to have the ability to choose a domain only by appending a @domain to their userid. Are there any negatives consequences for implementing a byipaddress only option too? I would like to see it implemented in cyrus, if this is not a problem. Regards, Christos Ken Murchison wrote: I just committed some code to CVS which changes the virtdomains option from a SWITCH to an ENUM having 3 options: off/no/0/false/f(disabled) userid(fully qualified userids only) on/yes/1/true/t(current behavior) What this means (hopefully) is that existing installations of 2.2 code (whether virtdomains is enabled or not) should be unaffected. Those that don't want the reverse IP address lookup can use the "userid" option. -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: [POLL] Cyrus 2.2 virtdomains behavior (Was: global admin without defaultdomain?)
Hi list. It would be very helpful if I could choose _only_ one from these options. You see, with current code for virtual domains, I faced the following frustrating situation. Provided that I have set up two domains foo.com and bar.com in my dns server and that I have given 2 IP addresses to my Cyrus. Then a user may connect to the server foo.com and login with the username [EMAIL PROTECTED] Well, this is a pretty uncomfortable situtation, since users may login to different domains from the ones they got connected, which seems a little bit weird to me. My opinion is that cyrus should provide an option on how to find out the domain. Also, I understand that current situation is helpful for some admins. For this reason I would suggest having 4 options, which would be something like : none, byuserid, byipaddress, both. I think this would be a fair sollution for everyone. Christos Ken Murchison wrote: This has to do with the fact that the virtdomains code handles domains by login id and ip address simultaneously. If you don't have a fully qualified user id, the code will do a reverse lookup on the ip address of the local NIC and add that domain. The only way to prevent the appending of the domain is by setting a default domain. I could probably fix this by changing the code to only do virtdomains by one mechanism at a time, NOT both. Since the 2.2 code recently added the ability to have enumerated config options, I could change the virtdomains option to be a tri-state variable, something like [ off, byuserid, byipaddress ]. As long as nobody is depending on the current behavior, I have no problem changing this. Of course, if people do need the current bevavior, I could add a fourth state to handle this. I'd like to get some feedback from those of you that have been using the virtdomains code before I go and make any changes. Happy Holidays, Ken -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: Cannot compile cyrus-2.2.2-BETA with Sun compiler (lib/imapopts.c)
Quoting Paul Boven <[EMAIL PROTECTED]>: This is caused because of the fact that Sun compiler is stricter on C standards. Ansi C forbids the type casting to a union. However, it is implemented as an extension by gcc. In my opinion this is wrong, because it violates some C standards. In this case you may compile cyrus 2.2.2-BETA if you remove the '(union config_value)' from all the lines of imapopts.c Then the compilation will continue throwing only some warnings until it breaks later in file lib/libcyr_cfg.c where there is another union type cast. ( (union cyrus_config_value)) You must remove this too and the compilation will end normally. For the time being removing these union castings is harmless for the binaries and cyrus function, but there are cases when this may break things down. And I am afraid that this will happen in some future release. I think that the cyrus developers should deal with this problem, other than gcc compilers are excluded. Regards, Christos > L.S., > > Build system is a Solaris 9 with SunOne aka Forte 7 compiler collection. > Both compiler and OS patches were updated before I began this project. > > While trying to build cyrus-imapd-2.2.2-BETA I run into the following > problem: > > cc -c -I.. -I/usr/local/BerkeleyDB.4.1//include -I/usr/local/include > -I./../et -I/usr/local/include -DHAVE_CONFIG_H -I. -I. -g \ > imapopts.c > "imapopts.c", line 35: invalid cast expression > "imapopts.c", line 35: initialization type mismatch > "imapopts.c", line 36: invalid cast expression > "imapopts.c", line 36: initialization type mismatch > "imapopts.c", line 37: invalid cast expression > "imapopts.c", line 37: initialization type mismatch > ... > "imapopts.c", line 141: invalid cast expression > "imapopts.c", line 141: initialization type mismatch > "imapopts.c", line 142: invalid cast expression > "imapopts.c", line 142: initialization type mismatch > cc: acomp failed for imapopts.c > make[1]: *** [imapopts.o] Error 2 > > Every line of 'struct imapopts' causes the compiler to fail. Compiling > cyrus with GCC does work, but would cause a performance penalty. I > assume the (union config_value)((const char *) entries are to blame. > This is a bit beyond my level of C expertise, could someone suggest a > less compiler-dependent version of this construction? > > Regards, Paul Boven. > -- /** * Christos Soulios * University of Athens * e-mail : soulbros(AT)noc.uoa.gr */
Re: [PATCH] autocreate inbox for cyrus 2.2.1-BETA
At the moment I am trying to figure out how it would best work in a murder environment. With your cooperation and some discussion on some really internal cyrus points, I think I can make it work with murder. What else apart from murder should the patch support, in order to make it into cyrus official distribution? Christos Rob Siemborski wrote: On Sat, 26 Jul 2003, Simon Matter wrote: Feedback concerning the rpm is always welcome. USE THE BETA RPM AT YOUR OWN RISK! BTW, is there any good reason why this patch should not be included into the main distribution? Yes, (as Wil noted) it doesn't support all configurations of cyrus (namely, it won't work in Murder enviornments). -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
[PATCH] autocreate inbox for cyrus 2.2.1-BETA
Version 0.8.1 of the autocreate inbox for cyrus 2.2.1-BETA is ready. Among other features, it supports Virtual Domains and autosubscribe shared folders. Yoy may downloaded it from http://email.uoa.gr/download/cyrus/cyrus-imapd-2.2.1-BETA/ For more information visit http://email.uoa.gr/autocreate Regards, Christos -- Christos Soulios (soulbros_at_noc.uoa.gr) Microsoft is not the answer. Microsoft is the question. No is the answer.
Re: cyrus-imapd 2.2.1 beta - auth problem
Just for your information.
I had the same problems with cyrus-imapd-2.2.1 and cyrus-sasl-2.1.14.
Specifically I ran cyrus in debug mode and I found that in imapd.c, line 1609,
where sasl_getpass() is executed, it returned normally without errors, returning
SASL_OK.
After that, when line 1634 was executed, the sasl_getprop(imapd_saslconn,
SASL_USERNAME, (const void **) &canon_user) returned the error SASL_NOTDONE
("can't request info until later in exchange").
The problem was magically solved when I upgraded to cyrus-sasl-2.1.15.
Regards,
Christos
Quoting Simon Matter <[EMAIL PROTECTED]>:
> >>
> >>
> >>
> >> This error is coming from SASL. Could you please post the relevent
> >> contents of imapd.log and auth.log?
> >
> > Ken,
> >
> > I have now straced the pid's on 2.1.14 and 2.2.1-BETA. I have also tested
> > the 2.2.1-BETA with pwcheck using /etc/sasldb2 and it works well. Looks
> to
> > me like there is something broken when using saslauthd. FYI, the
> > 2.2.1-BETA test is against cyrus-sasl 2.1.10.
>
> Hmm, I just tested against cyrus-sasl 2.1.15 and it works. Reinstalled
> 2.1.10 and it didn't work again.
>
> Is 2.2.1-BETA supposed not to work with cyrus-sasl 2.1.10?
>
> >
> > Simon
--
/**
* Christos Soulios
* Department of Informatics
* University of Athens
* e-mail : [EMAIL PROTECTED]
*/
virtual domains & per domain configuration
Hi all, I have installed cyrus-imapd-2.2.1-BETA with virtual domains enabled and I would like to know if there is any way of setting different configuration settings for each virtual domain. For example if I have two different domains and I want to set one or more options to different values between my two domains, is there any provision for such kinds of configurations? What about if I have more than one virtual domains. The same is valid for authentication and sasl. ie can I authenticate one of my domains with kerberos, one wild ldap and one with sasldb? If there is not any kind of such feature, are there any plans that it will be implemented in some future version? Feedback on this subject would be greatly appreciated. Regards, Christos -- /** * Christos Soulios * Department of Informatics * University of Athens * e-mail : [EMAIL PROTECTED] */
Re: Tru64 and 2.2 problems
I also compiled cyrus-imapd-2.2.1-BETA on a Solaris 9 box with Forte C compiler.
I had some of the same problems, which come from the fact that cyrus is mostly
gcc compiler oriented.
> 2) So, I get past the above, and run right smack into another problem,
> this time with lib/imapopts.c. I get over a 100 lines of errors along
> the lines of the following:
>
> {IMAPOPT_ADMINS,"admins",0,(union config_value)((const char
> *)""),OPT_STRING},
> ---^
> {IMAPOPT_ALLOWALLSUBSCRIBE,"allowallsubscribe",0,(union
> config_value)((int)0),OPT_SWITCH},
> -^
> {IMAPOPT_ALLOWNEWNEWS,"allownewnews",0,(union
> config_value)((int)0),OPT_SWITCH},
> ---^
>
> Basically, ever line in that table generates an error on the union
> construct. I don't understand the error message, been even more so, I
> don't understand why the union is even there at all. It appears that
> this file is automatically generated by the following command:
>
> ../tools/config2header imapopts.c imapopts.h < imapoptions
>
> The config2header script talks about playing an interesting game to get
> the union to initialize itself in a syntacticly valid manner, namely to
> initialize the union itself and not the members of the union, as well
> as
> to ensure that the union is initialized to something of a type that is
> in that union. What do I say about that? Very bizarre, and it doesn't
> work in Tru64.
>
> Doing a mass delete of all the '(union config_value)' stuff in the file
> gets the code to compile, but I don't know what kind of problems that
> is
> going to cause me if it has to do with initializing things.
>
> Any thoughts on how to handle this problem?
>
> I get similar errors when compiling libcyr_cfg.c as well, but in a
> slightly different context, and doing the same deletion gets it to at
> least compile.
>
This is because there is a cast to a union. Union casts are not ansi C
compliant, but a gcc extension.
Please see :
http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html
and
http://groups.google.com/groups?q=union+cast+group:comp.lang.c.*&hl=en&lr=&ie=UTF-8&group=comp.lang.c.*&selm=21259%40mimsy.umd.edu&rnum=3
What I did is to remove the cast to a union type. This makes the syntax ansi c
compliant.
By default the compiler sets the rvalue to the first member of the union.
And because the union is
union config_value {
const char *s;
int i;
int b;
};
the compiler assigns the value to the char *s member of the union. For this
reason every assignment to a string gets perfectly compiled.
However, I had some warnings for the assignments of integers to a char *. In my
case (Sun with Solaris 9) this creates no further problems, because the char *s
and the integer members of the union share the same memory. But I am not sure
what happens with different architectures that although the union members share
the same memory, the byte alignment between the string and the integer may differ.
> 3) After that, it compiles for awhile and then stops on imap/protocol.c
> with the following error:
>
> cc: Error: ./../lib/prot.h, line 209: Missing ";". (nosemi)
> __attribute__ ((format (printf, 2, 3)));
>
> Looking in lib/prot.h, I see the following:
>
> extern int prot_printf(struct protstream *, const char *, ...)
> __attribute__ ((format (printf, 2, 3)));
>
> What is that supposed to do? I simply deleted the line that has the
> __attribute__ on it and put a semicolon on the previous line and it
> compiles. What problems will I see by doing that?
>
__atribute__ keyword handling is done at the configure script and for compilers
that do not support this extension there is a #define statement. However, a
'#include ' statement is missing from the lib/prot.h file and for this
reason it does not build with other than gcc compilers. If you add it, then it
is ok.
Regards,
Christos
--
/**
* Christos Soulios
* Department of Informatics
* University of Athens
* e-mail : [EMAIL PROTECTED]
*/
[PATCH] autocreate inbox for cyrus-imapd-2.1.14
Hi all, I have ported the patch to the latest version (2.1.14) of cyrus imapd. *** New feature *** I also implemented an automatic subscription to shared folders procedure. The administrator may declare in the imapd.conf file some shared folders to which the user gets automatically subscribed when his/her mailbox is created, provided that the shared folder exists and the user has all the necessary permissions. *** Download *** The patch is at http://email.uoa.gr/download/cyrus/cyrus-imapd-2.1.14/ and the patch homepage is at http://email.uoa.gr/autocreate For comments, bug reports, feature requests do not hesitate to contact me. Regards, Christos -- /** * Christos Soulios * Department of Informatics * University of Athens * e-mail : [EMAIL PROTECTED] */
Re: Question about Autocreate patch.
Quoting Rob Siemborski <[EMAIL PROTECTED]>: > On Mon, 23 Jun 2003, Drew Weaver wrote: > > > Howdy, I got the autocreate patch working and its very nice, the only > > thing im trying to figure out is this. If I userdel a user, why does > > sendmail still deliver mail as if the user still exists? Shouldnt > > sendmail say, hey uh this user doesnt exist, and return the message? > > If you're using the autocreate patch, your MTA is responsible for > determining if a user doesn't exist (and needs to be configured as such, > specifically for your enviornment). The whole point of the patch is for > cyrus to NOT detect that a user doesn't exist. > > -Rob > Exactly. In this case you have 2 options : 1. Turn the option createonpost to off. In this case the lmtpd will never create any mailbox and always return a message of "user unknown" to sendmail. The mailbox will be created only upon user's login. 2. Have sendmail do the check against a user database if the user exists and delete the user from the user db along with the mailbox. However, this is risky in case the user db is used by other services too. Christos -- /** * Christos Soulios * Department of Informatics * University of Athens * e-mail : [EMAIL PROTECTED] */
Re: question about cyrus
Quoting Rob Siemborski <[EMAIL PROTECTED]>: > On Thu, 19 Jun 2003, Wil Cooley wrote: > > > http://haus.nakedape.cc/~wcooley/xfer/cyrus-imapd-2.1.13-3.src/ > > > > The patch in question is > > 'cyrus-imapd-2.1.13-autocreate-0.7.1.patch.txt'. I see no indication in > > the patch of whence it comes. > The autocreate inbox patch has been created by the University Of Athens. There is a homepage created for it too. Please see http://email.uoa.gr/autocreate . It has all the necessary information for the patch as well as frequent updates. This patch is the one used in Simon Matter's rpm distribution of cyrus imapd. Here at the UoA we are interested in integrating the patch into the Cyrus source code and willing to implement everything needed for it to be done. > If someone does the following, I think we'll be able to accept it in 2.2: > > 1. Conversion for 2.2 (mostly the configuration options) Already done in a cvs version cyrus 2.2 (specifically the CVS snapshot was at 19.5.2003) > 2. MURDER support It is in our plans to implement this. However, there are a lot of things to be considered first. Co-operation with the CMU developers would be very helpful. > 3. Virtual Domain Support This is currently being implemented. I hope it will be ready quite soon. > > (I realize the last two are on the todo list, but they're really necessary > to have a consistant behavior throughout the system). I totally agree. > > -Rob Christos -- /** * Christos Soulios * Department of Informatics * University of Athens * e-mail : [EMAIL PROTECTED] */
* U5 VirusKill * Re: autocreatequota - does it really work?
U5 VirusKill 2.3 has modified this mail as it contained a PC-executable attachment. ~ ~ ~ ~ ~ You should probably simply ignore this mail. If you really expected somebody to send you an executable attachment please mail back to this person and ask him/her to zip the file first. Below is given the first 60 lines of the mail that was sent to you with an executable file attached. As more than 99.999% of executable attachments are viruses, U5 VirusKill 2.3 has deactivated the attachment and truncated the mail. If you haven't done it yet please read http://www.u5.com/gen/ser/u5vk.htm Best regards U5com Co Ltd. Security Division ~ ~ ~ ~ ~ >Return-Path: <[EMAIL PROTECTED]> >Received: from lists2.andrew.cmu.edu (LISTS2.andrew.cmu.edu [128.2.10.216]) > by pb10.pair.com (Postfix) with ESMTP id 866DDA3034 > for <[EMAIL PROTECTED]>; Tue, 19 Nov 2002 03:36:39 -0500 (EST) >Received: (from postman@localhost) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) id gAJ89YQR010611 > for info-cyrus-list; Tue, 19 Nov 2002 03:09:34 -0500 (EST) >Received: from jlonline.com (pip15.ptt.js.cn [61.155.13.245]) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) with SMTP id >gAJ89IRw010601 > for <[EMAIL PROTECTED]>; Tue, 19 Nov 2002 03:09:23 -0500 (EST) >Received: from jlonline.com([10.1.0.13]) by js.cn(AIMC 2.9.5.2) > with SMTP id jm43dda079b; Tue, 19 Nov 2002 16:02:15 +0800 >Received: from lists2.andrew.cmu.edu([128.2.10.216]) by js.cn(AIMC 2.9.5.2) > with SMTP id jm43dd50a4b; Fri, 15 Nov 2002 22:13:28 +0800 >Received: (from postman@localhost) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) id gAFDYVOE011734 > for info-cyrus-list; Fri, 15 Nov 2002 08:34:31 -0500 (EST) >Received: from olympus.noc.uoa.gr (olympus.noc.uoa.gr [195.134.100.100]) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) with ESMTP id >gAFDYRRw011730 > for <[EMAIL PROTECTED]>; Fri, 15 Nov 2002 08:34:28 -0500 (EST) >Received: from olympus.noc.uoa.gr (localhost [127.0.0.1]) > by olympus.noc.uoa.gr (8.12.6/8.12.6) with ESMTP id gAFDYROT026178; > Fri, 15 Nov 2002 15:34:27 +0200 (EET) >Received: (from ierax@localhost) > by olympus.noc.uoa.gr (8.12.6/8.12.6/Submit) id gAFDYRZS026177; > Fri, 15 Nov 2002 13:34:27 GMT >X-Authentication-Warning: olympus.noc.uoa.gr: ierax set sender to [EMAIL PROTECTED] >using -f >Received: from 195.134.65.216 ( [195.134.65.216]) > as user [EMAIL PROTECTED] by webmail.uoa.gr with HTTP; > Fri, 15 Nov 2002 13:34:26 + >Message-ID: <[EMAIL PROTECTED]> >Date: Fri, 15 Nov 2002 13:34:26 + >From: Christos Soulios <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: Re: autocreatequota - does it really work? >MIME-Version: 1.0 >Content-Type: multipart/mixed; >boundary="-MOQ1037367266a37e8a668a0ad1fd3e90b9baa851c1cf" >User-Agent: Internet Messaging Program (IMP) 3.1 >Sender: [EMAIL PROTECTED] >Precedence: bulk > >This message is in MIME format. > >---MOQ1037367266a37e8a668a0ad1fd3e90b9baa851c1cf >Content-Type: text/plain; charset=ISO-8859-7 >Content-Transfer-Encoding: 8bit > >In my opinion features such as autocreate must not be implemented by clients, >but by the imap server. This way a lot of problems due to incompatibilities of >the various MUAs on the naming of the INBOX subfolders and the policies on the >inbox creation are avoided. > >Below I attach you some patches for the autocreate function. We patched the >autocreate function in order to have some extra features. In short, the extra >features implemented in this autocreate function are : > >1. Cyrus **creates** the inbox as well as other submailboxes. The user is >subscribed automatically to some or all of them. The administrator can >explicitly define in imapd.conf which submailboxes may be created and to which
* U5 VirusKill * Re: autocreatequota - does it really work?
U5 VirusKill 2.3 has modified this mail as it contained a PC-executable attachment. ~ ~ ~ ~ ~ You should probably simply ignore this mail. If you really expected somebody to send you an executable attachment please mail back to this person and ask him/her to zip the file first. Below is given the first 60 lines of the mail that was sent to you with an executable file attached. As more than 99.999% of executable attachments are viruses, U5 VirusKill 2.3 has deactivated the attachment and truncated the mail. If you haven't done it yet please read http://www.u5.com/gen/ser/u5vk.htm Best regards U5com Co Ltd. Security Division ~ ~ ~ ~ ~ >Return-Path: <[EMAIL PROTECTED]> >Received: from lists2.andrew.cmu.edu (LISTS2.andrew.cmu.edu [128.2.10.216]) > by pb10.pair.com (Postfix) with ESMTP id B9B47A301D > for <[EMAIL PROTECTED]>; Fri, 15 Nov 2002 09:14:19 -0500 (EST) >Received: (from postman@localhost) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) id gAFDYVOE011734 > for info-cyrus-list; Fri, 15 Nov 2002 08:34:31 -0500 (EST) >Received: from olympus.noc.uoa.gr (olympus.noc.uoa.gr [195.134.100.100]) > by lists2.andrew.cmu.edu (8.12.3.Beta2/8.12.0.Beta16) with ESMTP id >gAFDYRRw011730 > for <[EMAIL PROTECTED]>; Fri, 15 Nov 2002 08:34:28 -0500 (EST) >Received: from olympus.noc.uoa.gr (localhost [127.0.0.1]) > by olympus.noc.uoa.gr (8.12.6/8.12.6) with ESMTP id gAFDYROT026178; > Fri, 15 Nov 2002 15:34:27 +0200 (EET) >Received: (from ierax@localhost) > by olympus.noc.uoa.gr (8.12.6/8.12.6/Submit) id gAFDYRZS026177; > Fri, 15 Nov 2002 13:34:27 GMT >X-Authentication-Warning: olympus.noc.uoa.gr: ierax set sender to [EMAIL PROTECTED] >using -f >Received: from 195.134.65.216 ( [195.134.65.216]) > as user [EMAIL PROTECTED] by webmail.uoa.gr with HTTP; > Fri, 15 Nov 2002 13:34:26 +0000 >Message-ID: <[EMAIL PROTECTED]> >Date: Fri, 15 Nov 2002 13:34:26 + >From: Christos Soulios <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: Re: autocreatequota - does it really work? >MIME-Version: 1.0 >Content-Type: multipart/mixed; >boundary="-MOQ1037367266a37e8a668a0ad1fd3e90b9baa851c1cf" >User-Agent: Internet Messaging Program (IMP) 3.1 >Sender: [EMAIL PROTECTED] >Precedence: bulk > >This message is in MIME format. > >---MOQ1037367266a37e8a668a0ad1fd3e90b9baa851c1cf >Content-Type: text/plain; charset=ISO-8859-7 >Content-Transfer-Encoding: 8bit > >In my opinion features such as autocreate must not be implemented by clients, >but by the imap server. This way a lot of problems due to incompatibilities of >the various MUAs on the naming of the INBOX subfolders and the policies on the >inbox creation are avoided. > >Below I attach you some patches for the autocreate function. We patched the >autocreate function in order to have some extra features. In short, the extra >features implemented in this autocreate function are : > >1. Cyrus **creates** the inbox as well as other submailboxes. The user is >subscribed automatically to some or all of them. The administrator can >explicitly define in imapd.conf which submailboxes may be created and to which >the user is subscribed. > >2. Create on post is also implemented. Which means, that a mailbox may also be >created when a mail arrives at the user's mailbox, while the user has not >already logged in the system. Of course, this configurable too. > >3. On login the user may also be subscribed to bulleting board folders, provided >that he has been granted the priviliges to subscribe to this folder. This is >very useful with public folders (allowed to anonymous or anyone). Of course, >this is also configurable in imapd.conf.
Re: autocreatequota - does it really work?
In my opinion features such as autocreate must not be implemented by clients, but by the imap server. This way a lot of problems due to incompatibilities of the various MUAs on the naming of the INBOX subfolders and the policies on the inbox creation are avoided. Below I attach you some patches for the autocreate function. We patched the autocreate function in order to have some extra features. In short, the extra features implemented in this autocreate function are : 1. Cyrus **creates** the inbox as well as other submailboxes. The user is subscribed automatically to some or all of them. The administrator can explicitly define in imapd.conf which submailboxes may be created and to which the user is subscribed. 2. Create on post is also implemented. Which means, that a mailbox may also be created when a mail arrives at the user's mailbox, while the user has not already logged in the system. Of course, this configurable too. 3. On login the user may also be subscribed to bulleting board folders, provided that he has been granted the priviliges to subscribe to this folder. This is very useful with public folders (allowed to anonymous or anyone). Of course, this is also configurable in imapd.conf. A snippet of my imapd.conf, relative to the autocreate feature is following : - #createonpost: no #If nonzero new mailboxes will be created on if #autocreatequota is also set. createonpost: yes autocreatefolders: SUB: Sent |SUB: Drafts |SUB: Trash | Templates - NOTICE : If cyrus admin ever tries to log in the system and is authorised as a user that has never logged in before, special care is taken and the mailbox is never created. This behaviour may also be implemented as configurable. -- /** * Christos Soulios * EDUnet Team * University of Athens * e-mail : soulbros_AT_noc.uoa.gr */ edunet-autocreate Description: Binary data
