deleting ALL mailboxes from cyrus
For some reason the default mailbox creations on my cyrus install have become all screwed up. I would like to know what I should do to delete ALL of the boxes currently on the system. I created an account for myself(this first and only account) shell>cm user.cwiles But when I do a listmailboxes shell>lm I get this: Drafts (\HasNoChildren) user.cwiles (\HasChildren) Sent (\HasNoChildren) user.cwiles.Sent (\HasNoChildren) Trash (\HasNoChildren) user.cwiles.Trash (\HasNoChildren) What created the "Drafts, Sent, and Trash" folders? shell>lam * Drafts: cwiles d anyone lrs Sent: cwiles d anyone lrs Trash: cwiles d anyone lrs user.cwiles: cwiles lrswipcda user.cwiles.Sent: cwiles lrswipcda user.cwiles.Trash: cwiles lrswipcda When I logged into my account from my mail client my mailbox listing is Inbox -Sent -Trash Drafts Sent Trash I tried to delete the Inbox.Trash and Inbox.Sent box, but when I log back into my email it is created againuggg. I want to just start fresh and create all the boxes from scratch...suggestions? Thanks so much, Cory --- 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: weird sieve issues
Derrick J Brashear wrote: > On Wed, 16 Mar 2005, Cory D. Wiles wrote: > >> Programs Installed: >> Cyrus IMAPd 2.2.12 >> Cyrus SASL 2.1.20 >> >> I have been trying to get sieve running all day, but to no avail. If I >> run the following command: >> >> shell>$sieveshell --user=cwiles -a cyrus localhost >> >> I get the following error: >> >> connecting to localhost >> Bad protocol from MANAGESIEVE server: EOL2 >> >> When I looked at my imadp.log I noticed that I was getting the following >> error: >> IOERROR: not a sieve bytecode file /usr/local/sieve/c/cwiles/defaultbc > > > Said file gets created when you enable a script as default. Don't > precreate it unless you're putting in a script for all your users in > advance, and if so put the script there also. > >> When I removed the defaultbc file I now get: >> IOERROR: fstating sieve script /usr/local/sieve/c/cwiles/defaultbc: No >> such file or directory > > > find /usr/local/sieve -print|xargs chown cyrus Still received the connecting to localhost Bad protocol from MANAGESIEVE server: EOL2 error message. Nothing was found in /var/log/imapd.log However...in /var/log/messages the following error message was recorded: timsieved: could not getenv(CYRUS_SERVICE); exiting > > and see if that fixes it? I can't look at source right this second but > I'm guessing the ownership is wrong... > >> >> >> If anyone has any insight as to what I am missing then i would really >> appreciate it. I have been googling all day long and I am out of ideas. >> >> Thanks, >> Cory >> --- >> 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
weird sieve issues
Programs Installed:
Cyrus IMAPd 2.2.12
Cyrus SASL 2.1.20
I have been trying to get sieve running all day, but to no avail. If I
run the following command:
shell>$sieveshell --user=cwiles -a cyrus localhost
I get the following error:
connecting to localhost
Bad protocol from MANAGESIEVE server: EOL2
When I looked at my imadp.log I noticed that I was getting the following
error:
IOERROR: not a sieve bytecode file /usr/local/sieve/c/cwiles/defaultbc
::NOTE::
I had to create the "c/cwiles/defaultbc" directories/files manually...I
am not sure if that is correct or not.
When I removed the defaultbc file I now get:
IOERROR: fstating sieve script /usr/local/sieve/c/cwiles/defaultbc: No
such file or directory
When I checked to make sure that the port(2000) was even open I was
shocked to see that the mimedefang.sock was listening to it and I have
no idea why:
shell>$netstat -na | grep LISTEN
tcp0 0 0.0.0.0:32768 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:993 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:995 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:33060.0.0.0:* LISTEN
tcp0 0 0.0.0.0:110 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:143 0.0.0.0:* LISTEN
tcp0 0 127.0.0.1:783 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:20000.0.0.0:* LISTEN
tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp0 0 127.0.0.1:32825 0.0.0.0:* LISTEN
tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN
unix 2 [ ACC ] STREAM LISTENING 1977
/var/spool/MIMEDefang/mimedefang-multiplexor.sock
unix 2 [ ACC ] STREAM LISTENING 2000
/var/spool/MIMEDefang/mimedefang.sock
unix 2 [ ACC ] STREAM LISTENING 2271 /tmp/mysql.sock
unix 2 [ ACC ] STREAM LISTENING 2276
/tmp/.font-unix/fs7100
unix 2 [ ACC ] STREAM LISTENING 8825
/var/imap/socket/lmtp
unix 2 [ ACC ] STREAM LISTENING 2825
/var/run/dbus/system_bus_socket
I did have to create a new xinetd file:
service sieve
{
socket_type = stream
protocol= tcp
wait= no
user= cyrus
port= 2000
passenv = PATH
server = /usr/cyrus/bin/timsieved
}
::IMAPD.CONF::
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cwiles, cyrus
sasl_pwcheck_method: saslauthd
sievedir: /usr/local/sieve
sieveusehomedir: no
hashimapspool: true
altnamespace: yes
sendmail: /usr/sbin/sendmail
timeout: 90
allowplaintext: yes
::CYRUS.CONF::
# standard standalone server implementation
START {
# do not delete this entry!
recover cmd="ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
idled cmd="idled"
}
# UNIX sockets start with a slash and are put into /var/imap/socket
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=0
imaps cmd="imapd -s" listen="imaps" prefork=0
pop3 cmd="pop3d" listen="pop3" prefork=0
pop3s cmd="pop3d -s" listen="pop3s" prefork=0
sieve cmd="timsieved" listen="sieve" prefork=0
# these are only necessary if receiving/exporting usenet via NNTP
# nntp cmd="nntpd" listen="nntp" prefork=0
# nntpscmd="nntpd -s" listen="nntps" prefork=0
# at least one LMTP is required for delivery
# lmtp cmd="lmtpd" listen="lmtp" prefork=0
lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
# this is only necessary if using notifications
# notify cmd="notifyd" listen="/var/imap/socket/notify"
proto="udp" prefork=1
}
EVENTS {
# this is required
checkpointcmd="ctl_cyrusdb -c" period=30
# this is only necessary if using duplicate delivery suppression,
# Sieve or NNTP
delprune cmd="cyr_expire -E 3" at=0400
# this is only necessary if caching TLS sessions
tlsprune cmd="tls_prune" at=0400
}
If anyone has any insight as to what I am missing then i would really
appreciate it. I have been googling all day long and I am out of ideas.
Thanks,
Cory
---
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: RE: Newbie Cyrus IMAP on Fedora Core 2
I spent ALOT of time getting Cyrus IMAP to work on my Fedora Core 2 and it works great now. I documented the steps that one would need to go through to get it to work. I credited those individuals from this mailing list who assisted. If for some reason I did miss someone then just let me know and I'll give you the credit you greatly deserve. ---cut here Cyrus IMAP Mail Server Install 2.2.8 Written Primarily by: Michael Sims <[EMAIL PROTECTED]> Contributions by: Cory Wiles <[EMAIL PROTECTED]> Andreas <[EMAIL PROTECTED]> Cyrus Mailinglist <[EMAIL PROTECTED]> Install and configure Cyrus IMAP Installing Cyrus is a two step process. First we must install the Cyrus SASL libraries, which Cyrus IMAP uses for authentication. Go to the source directory for Cyrus SASL and do the following: Shell>./configure --disable-krb4 --disable-gssapi --disable-cram --disable-digest\ --enableĀplain >From the Cyrus source directory: ./configure --with-auth=unix --with-perl=/usr/bin/perl\ --with-comm_err=/usr/include/et/com_err.h --with-idle=idled\ --with-mboxlist-db=skiplist --with-seen-db=skiplist --with-duplicate-db=skiplist\ --with-sasl=/usr/lib/sasl2 Shell>make Shell>su Shell>make install Shell>ln -s /usr/local/lib/sasl2 /usr/lib/sasl2 This last step is necessary because the sasl libraries look for plugins under /usr/lib/sasl2, not /usr/local/lib/sasl2. The next step is installing the Cyrus IMAP server itself.: Shell>make depend Shell>make all CFLAGS=-O Shell>make install Next we need to create a user for the server. Create a user called "cyrus" and set it's primary group to "mail". Next create the cyradmin user, with mail as the primary group: You MAY need to create the log files: Shell>touch /var/log/imapd.log /var/log/auth.log This may not be necessary, as syslogd may have already created them. Next create the cyradmin user, with mail as the primary group: Shell>useradd -g mail cyradmin Next we have to create the configuration, partition and sieve directories for cyrus: Shell>cd /var Shell>mkdir imap Shell>chown cyrus.mail imap/ Shell>chmod 750 imap Shell>cd /var/spool/ Shell>mkdir imap Shell>chown cyrus.mail imap/ Shell>chmod 750 imap Shell>cd /usr/local/ Shell>mkdir sieve Shell>chown cyrus.mail sieve chmod 750 sieve Check to make sure there is a directory called /var/state/saslauthd. If not, create it. This was done automatically for me once but not the next time I installed. I didn't have the time to research why, but you should be able to just create the directory as root and not have any problems. Next move to the root of the cyrus imapd source directory and do the following: Shell>su cyrus Shell>tools/mkimap Shell>exit To use normal.conf, do: Shell>cp master/conf/normal.conf /etc/cyrus.conf This sets up the directories for use with cyrus. There is a file in this module under var/imap/db called DB_CONFIG. It's very important that you place this file in /var/imap/db. It increases the size of the Berkeley DB cache from it's default of 256kb (way too low) to 2MB. Optionally, you can edit /etc/cyrus.conf to disable or enabling certain services, or to tune the number of preforked copies. Be sure not to remove the entries that are labeled required. Start the service: Shell>/usr/cyrus/bin/master & Configuring Sendmail For Sendmail 8.12.4 and higher, use the cyrusv2 mailer definition in the Sendmail distribution: Shell>vi /etc/mail/sendmail.mc define(`confLOCAL_MAILER', `cyrusv2') MAILER(`cyrusv2') >From your normal account, telnet to the IMAP port on the server you're setting up: Shell>telnet foobar imap If your server is running, you'll get the following message: Trying 128.2.232.95... Connected to foobar.andrew.cmu.edu. Escape character is '^]'. * OK foobar.andrew.cmu.edu Cyrus IMAP4 v2.0.0 server ready Any message other than one starting with "* OK" means there is a problem. To terminate the connection, type ". logout". Naturally the version number should match the version you just installed. Use "imtest" to test logging in with plaintext passwords: Shell>/usr/local/bin/imtest -m login foobar If you want to specify a different user, do: Shell>/usr/local/bin/imtest -m login -a USER foobar If your server is running, you'll get the following message: % /usr/local/bin/imtest -m login foobar S: * OK mail1.andrew.cmu.edu Cyrus IMAP4 v2.0.0 server ready C: C01 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME AUTH=GSSAPI AUTH=ANONYMOUS AUTH=KERBEROS_V4 UNSELECT S: C01 OK Completed Password: + go ahead L01 OK User logged in Authenticated. Security strength factor: 0 Any message other than one starting with a "L01 OK" means there is a problem. If the test fails, a more specific error message should be written through syslog to the server log. To terminate the connection, type ". logout". Making Cyrus Start On Boot Credit(http://www.phildev.net/cyr
Re: Re: Cyrus Login
That did it Thank you EVERYONE who helped me with this. I had a few people at work tell me to switch to another software but it wasn't the programs fault it wasn't working and this is a DEFINITE learning experience so once again hats off to those who took the time to look at and answer my emails so promptly. Just a small final question if I want to create new accounts and/or folders will I have to login to the cyradm and create them or will they be created when you add a user to the machine? I would assume you would have to create the account in the cyradm since you don't necessarily want every user you create to have an email account. > On Thu, Aug 05, 2004 at 09:08:52AM -0500, Cory D. Wiles wrote: > > >saslpasswd2 -c > > Should the 'yourname' be my regular account, or the cyrus-master account > > You will probably have to add both: > > saslpasswd2 -c cyrus > saslpasswd2 -c cory > > (I'm assuming "cyrus" is listed under "admins:" in /etc/imapd.conf) > > --- > 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
Re: Cyrus Login
Derrick, I ran into some problems with this. When I ran $gdb cyradm I get $GNU gdb Red Hat Linux (6.0post-0.20040223.19rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"..."/usr/local/bin/cyradm": not in executable format: File format not recognized I still tried to execute it. $(gdb) run /usr/local/bin/cyradm --user cyradmin stasis Starting program: /usr/local/bin/cyradm --user cyradmin stasis No executable file specified. Use the "file" or "exec-file" command. (gdb) exec-file /usr/local/bin/cyradm --user cyradmin stasis "/usr/local/bin/cyradm": not in executable format: File format not recognized (gdb) file /usr/local/bin/cyradm --user cyradmin stasis "/usr/local/bin/cyradm": not in executable format: File format not recognized Was there something that I wasn't executing correctly? Derrick J Brashear wrote: On Wed, 4 Aug 2004, Cory D. Wiles wrote: When i try to run: $cyradm -user cyradmin stasis and enter my password is when I get the segmentation fault error. Can you do the following? gdb cyradm run -user cyradmin stasis (type your password) and when you get the SEGV, type where and tell us the backtrace you get? --- 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
Re: Cyrus Login
>saslpasswd2 -c Should the 'yourname' be my regular account, or the cyrus-master account Andreas wrote: On Thu, Aug 05, 2004 at 08:51:02AM -0500, Cory D. Wiles wrote: I looked at the bug report and the problem is VERY similar to mine. Also I tried to force the method and got the same error that you received did: $cyradm --user cyrus --auth DIGEST-MD5 stasis Password: $cyradm: cannot authenticate to server with DIGEST-MD5 as cyrus That's because you don't have digest-md5 setup properly. The segfault happens whenever gssapi comes into play here and is not configured, that is, it fails. If no mechanisms are specified, cyradm will try several, in order, including gssapi, where the segfault occurs if gssapi is not configured. So, to sum things up, you may want to remove the gssapi sasl plugin from your sistem for now and configure digest-md5 or some other mechanism. To use digest-md5 is not that hard, basically: - saslpasswd2 -c - check that /etc/sasldb2 is created - check permissions on that file: the cyrus-master daemon has to be able to read it --- 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 Login
I wish I had gotten this email just about an hour sooner. I got so frustrated with everything that I recompiled sasl2 and cyrus-imap. During the compile process I was still looking up reference material and ran across some cyradm information and realized that I hadn't created the mailbox 'user.cwiles'. However when i try to get into the cyradm and login i get a 'Segmentation Fault' error. Just when I could have had everything fixed. My saslauthd config line is: ./configure --disable-krb4 --disable-gssapi --disable-cram --disable-digest --enable-plain My cyrus-imap config line is: ./configure --with-auth=unix --with-perl=/usr/bin/perl --with-comm_err=/usr/include/et/com_err.h --with-idle=idled --with-mboxlist-db=skiplist --with-seen-db=skiplist --with-duplicate-db=skiplist --with-sasl=/usr/lib/sasl2 When i try to run: $cyradm -user cyradmin stasis and enter my password is when I get the segmentation fault error. here is my auth.log Aug 4 13:53:54 stasis imap[22007]: unable to open Berkeley db /etc/sasldb2: No such file or directory Aug 4 13:53:54 stasis imap[22007]: no OTP secret in database Aug 4 13:53:57 stasis perl: GSSAPI Error: Miscellaneous failure (No credentials cache found) Aug 4 13:53:57 stasis imap[22007]: DIGEST-MD5 server step 1 Aug 4 13:53:57 stasis perl: DIGEST-MD5 client step 2 Aug 4 13:53:57 stasis imap[22007]: DIGEST-MD5 server step 2 Aug 4 13:53:57 stasis imap[22007]: unable to open Berkeley db /etc/sasldb2: No such file or directory Aug 4 13:53:57 stasis imap[22007]: unable to open Berkeley db /etc/sasldb2: No such file or directory Aug 4 13:53:57 stasis imap[22007]: no secret in database Imapd.log - Aug 4 13:53:51 stasis master[22007]: about to exec /usr/cyrus/bin/imapd Aug 4 13:53:51 stasis imap[22007]: executed Aug 4 13:53:51 stasis imap[22007]: accepted connection Aug 4 13:53:54 stasis imap[22007]: badlogin: stasis.randomthoughtprocess.com [127.0.0.1] OTP [SASL(-13): user not found: no OTP secret in database] Aug 4 13:53:57 stasis imap[22007]: badlogin: stasis.randomthoughtprocess.com [127.0.0.1] DIGEST-MD5 [SASL(-13): user not found: no secret in database] Thoughts on why I can't login into cyradm? > I sent this yesterday but I think I forgot some important information. > > I have been working getting cyrus 2.2.8 running for the past two days but > I am having some serious issues. When my email client prompts me for the > password I get the following error: 'Sending password did not succeed. > Mail server stasis.randomthoughtprocess.com responded:Unable to locate > maildrop: Mailbox doesn't exist.' Did you create the mailbox for cwiles? Cyrus doesn't create it automagically (until you patched cyrus to do it). Login with cyradm and do a 'cm user.cwiles'. Simon > > Here are some of the files that I think might help diagnos the problem. > Like i said I have tried everything to get this to work, but I know that > there is something that I am missing. > > ++Latest auth.log file > Aug 2 06:39:13 stasis sshd(pam_unix)[18076]: authentication failure; > logname= uid=0 euid=0 tty=NODEVssh ruser= > rhost=168-215-137-46.cmcsmart.com user=cwiles > Aug 2 06:39:19 stasis sshd(pam_unix)[18078]: session opened for user > cwiles by (uid=500) > Aug 2 07:32:20 stasis pop3[18118]: could not find auxprop plugin, was > searching for '[all]' > ++end auth.log file > > ++Latest imapd.log+ > Aug 2 07:32:17 stasis master[18118]: about to exec /usr/cyrus/bin/pop3d > Aug 2 07:32:17 stasis pop3[18118]: executed > Aug 2 07:32:17 stasis pop3[18118]: accepted connection > Aug 2 07:32:20 stasis pop3[18118]: login: jenna.randomthoughtprocess.com > [192.168.1.100] cwiles plaintext User logged in > Aug 2 07:32:23 stasis pop3[18118]: Unable to locate maildrop for cwiles: > Mailbox does not exist > Aug 2 07:33:45 stasis master[17414]: process 18118 exited, status 0 > ++end imapd.log+ > > ++Latest messages+++ > Aug 2 07:27:35 stasis ctl_cyrusdb[18116]: checkpointing cyrus databases > Aug 2 07:27:35 stasis ctl_cyrusdb[18116]: done checkpointing cyrus > databases > Aug 2 07:32:20 stasis pop3[18118]: login: jenna.randomthoughtprocess.com > [192.168.1.100] cwiles plaintext User logged in > Aug 2 07:32:23 stasis pop3[18118]: Unable to locate maildrop for cwiles: > Mailbox does not exist > Aug 2 07:38:23 stasis su(pam_unix)[18124]: session opened for user root > by cwiles(uid=500) > + > > ++Begin /etc/imapd.conf+ > configdirectory: /var/imap > partition-default: /var/spool/imap > admins: cyradmin > sasl_pwcheck_method: saslauthd > sievedir: /usr/local/sieve
cyrus login troubles
I sent this yesterday but I think I forgot some important information.
I have been working getting cyrus 2.2.8 running for the past two days but I am having
some serious issues. When my email client prompts me for the password I get the
following error: 'Sending password did not succeed. Mail server
stasis.randomthoughtprocess.com responded:Unable to locate maildrop: Mailbox doesn't
exist.'
Here are some of the files that I think might help diagnos the problem. Like i said I
have tried everything to get this to work, but I know that there is something that I
am missing.
++Latest auth.log file
Aug 2 06:39:13 stasis sshd(pam_unix)[18076]: authentication failure; logname= uid=0
euid=0 tty=NODEVssh ruser= rhost=168-215-137-46.cmcsmart.com user=cwiles
Aug 2 06:39:19 stasis sshd(pam_unix)[18078]: session opened for user cwiles by
(uid=500)
Aug 2 07:32:20 stasis pop3[18118]: could not find auxprop plugin, was searching for
'[all]'
++end auth.log file
++Latest imapd.log+
Aug 2 07:32:17 stasis master[18118]: about to exec /usr/cyrus/bin/pop3d
Aug 2 07:32:17 stasis pop3[18118]: executed
Aug 2 07:32:17 stasis pop3[18118]: accepted connection
Aug 2 07:32:20 stasis pop3[18118]: login: jenna.randomthoughtprocess.com
[192.168.1.100] cwiles plaintext User logged in
Aug 2 07:32:23 stasis pop3[18118]: Unable to locate maildrop for cwiles: Mailbox does
not exist
Aug 2 07:33:45 stasis master[17414]: process 18118 exited, status 0
++end imapd.log+
++Latest messages+++
Aug 2 07:27:35 stasis ctl_cyrusdb[18116]: checkpointing cyrus databases
Aug 2 07:27:35 stasis ctl_cyrusdb[18116]: done checkpointing cyrus databases
Aug 2 07:32:20 stasis pop3[18118]: login: jenna.randomthoughtprocess.com
[192.168.1.100] cwiles plaintext User logged in
Aug 2 07:32:23 stasis pop3[18118]: Unable to locate maildrop for cwiles: Mailbox does
not exist
Aug 2 07:38:23 stasis su(pam_unix)[18124]: session opened for user root by
cwiles(uid=500)
+
++Begin /etc/imapd.conf+
configdirectory: /var/imap
partition-default: /var/spool/imap
admins: cyradmin
sasl_pwcheck_method: saslauthd
sievedir: /usr/local/sieve
hashimapspool: true
altnamespace: yes
unixhierarchysep: yes
sendmail: /usr/sbin/sendmail
timeout: 90
allowplaintext: yes
++end /etc/imapd.conf+++
++Begin /etc/cyrus.conf+
# standard standalone server implementation
START {
# do not delete this entry!
recover cmd="ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
# idledcmd="idled"
}
# UNIX sockets start with a slash and are put into /var/imap/socket
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=0
imaps cmd="imapd -s" listen="imaps" prefork=0
pop3 cmd="pop3d" listen="pop3" prefork=0
pop3s cmd="pop3d -s" listen="pop3s" prefork=0
sieve cmd="timsieved" listen="sieve" prefork=0
# these are only necessary if receiving/exporting usenet via NNTP
# nntp cmd="nntpd" listen="nntp" prefork=0
# nntpscmd="nntpd -s" listen="nntps" prefork=0
# at least one LMTP is required for delivery
# lmtp cmd="lmtpd" listen="lmtp" prefork=0
lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
# this is only necessary if using notifications
# notify cmd="notifyd" listen="/var/imap/socket/notify" proto="udp" prefork=1
}
EVENTS {
# this is required
checkpointcmd="ctl_cyrusdb -c" period=30
# this is only necessary if using duplicate delivery suppression,
# Sieve or NNTP
delprune cmd="cyr_expire -E 3" at=0400
# this is only necessary if caching TLS sessions
tlsprune cmd="tls_prune" at=0400
}
++end /etc/cyrus.conf+++
Any insight to this would be greatly appreciated. Setting up a mail server is a NEW
concept for me and guidance would be greatly appreciated.
---
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
