Re: Lost mail 2.3.8

2007-04-17 Thread Mike Husmann
 Casper wrote:
 i have userids.

 Thats not the problem, the problem is that the imapserverlog say the mail
 is delivered but the user say it never arrived...


   You might try asking the user if they have thread view turned on (depending
on the MUA).  I had a few users that 'lost' messages when they were thread
sorted to #345 in the list because the incoming mail was a reply to an
email was originally dated months ago.

HTH,

Mike


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: vanished folders

2007-01-03 Thread Mike Husmann
Hi Matthias,

On Wed, January 3, 2007 7:45 am, Matthias Henze wrote:
 hi,

 i've moved several users with imapsync from an other cyrus setup to kolab
 which uses cyrus imapd. now i can only see the inbox, NONE of the
 subfolders.

  What command line options did you pass to imapsync?  Are the folders present
at a filesystem level?

Mike


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: vanished folders

2007-01-03 Thread Mike Husmann
On Wed, January 3, 2007 8:34 am, Matthias Henze wrote:
 Am Mittwoch, 3. Januar 2007 15:03 schrieb Mike Husmann:
 Hi Matthias,

 On Wed, January 3, 2007 7:45 am, Matthias Henze wrote:
  hi,
 
  i've moved several users with imapsync from an other cyrus setup to
  kolab which uses cyrus imapd. now i can only see the inbox, NONE of the
  subfolders.

   What command line options did you pass to imapsync?  Are the folders
 present at a filesystem level?

 hi mike,

 no special options. and: yes, they are present an all mails too. they are
 just invisible.

  Check out the imapsync man page (or run imapsync --help).  You're looking
for the --subscribe option (auto subscribes you to all folders that were
subscribed to on the old server).  Give the instructions a good read - there
are lots of good options like preserving internal date/time stamps and
read/unread status.

Mike


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 DBERROR with avelsieve

2006-10-08 Thread Mike Husmann

On Sat, October 7, 2006 7:38 pm, Andreas Winkelmann wrote:
 Oct  5 08:24:38 rusty sieve[18879]: DBERROR: error exiting application: 
 Invalid
argument

 This invalid argument Stuff appears most time, if there is a Version 
 mismatch
with Berkeley DB.

 Do you have more than one Version installed?

 Are all DBs of the same version? tls_caching.db?


Only have one version of the db installed, which is 4.3.  The problem popped up 
when
the Squirrelmail plugin I'm using was upgraded, and so started using tls... 
Apparantly, this is part of the problem:
http://www.sleepycat.com/docs/ref/upgrade.4.3/err.html

Which explains the ^H being displayed instead of the actual error message,

and other discussions about cyrus 2.2.12 and db 4.3 not being fully compatible. 
 I'm
using Trustix Secure Linux 3.0, and I'm asking why they chose to use 4.3 if 
this is
a known issue.

So for now, is it safe to assume it's ok to turn tls back on and live with the
errors?  I have no data corruption from this, as far as I can tell, and the 
sieve
filters compile and execute just fine..


Mike




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 DBERROR with avelsieve

2006-10-06 Thread Mike Husmann
 Oct  5 11:57:15 rusty sieve[29932]: DBERROR #65533;^H^H: db4
 When using sivtest, I get the same error every time I execute LOGOUT, but 
 only when
 using TLS...

 sivtest -a bebo -u bebo -t  imap.morningside.edu
   this yields the error

 sivtest -a bebo -u bebo imap.morningside.edu
   this does not

  Until I get this figured out on the cyrus side, I have eliminated the errors 
by
disabling the use of tls for the avelsieve plugin in Squirrelmail
(managesieve.lib.php).  If anyone has any ideas (especially if I've missed
something obvious), I'd love to hear them.

Thanks,

Mike


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


Sieve DBERROR with avelsieve

2006-10-05 Thread Mike Husmann
Hey all,
  I just upgraded the avelsieve plugin in my Squirrelmail site install to 1.9.7 
and
have suddenly started receiving errors.  Every time I make a modification using
the sieve plugin, I get the following error:

Oct  5 08:24:38 rusty sieve[18879]: DBERROR: error exiting application: Invalid
argument

But for that same transaction, there is no mention of any error in the debug 
log:

Oct  5 08:24:37 rusty sieve[18879]: executed
Oct  5 08:24:37 rusty sieve[18879]: accepted connection
Oct  5 08:24:37 rusty sieve[18879]: mystore: starting txn 2147484734
Oct  5 08:24:37 rusty sieve[18879]: mystore: committing txn 2147484734
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 16
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 96
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 192
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 300
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 528
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 644
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 748
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 860
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 988
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1108
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1232
Oct  5 08:24:37 rusty sieve[18879]: entered bc_action_emit with filelen: 1404
Oct  5 08:24:38 rusty sieve[18879]: entered bc_action_emit with filelen: 1508
Oct  5 08:24:38 rusty master[18370]: process 18879 exited, status 0

I have passed this on as a probable bug in the plugin, but I wanted to see if 
there
was anything I can do about it (or if I had anything wrong) as well.

imapd.conf:
# server conf
servername: rusty.morningside.edu
umask: 077
reject8bit: no
quotawarn: 90
timeout: 30
poptimeout: 10
# singleinstancestore: yes

username_to_lower: yes
lmtp_downcase_rcpt: yes
lmtp_over_quota_perm_failure: yes

altnamespace: yes

# user conf
postmaster: postmaster
admins: cyrus cyrusadm

# directory and file locations
configdirectory: /var/spool/cyrus-imap
partition-default: /var/spool/cyrus-imap
sievedir: /var/spool/cyrus-imap/sieve
sievenotifier: mailto

sendmail: /usr/sbin/sendmail

# authentication
allowanonymouslogin: no
allowplaintext: yes
sasl_mech_list: plain
sasl_minimum_layer: 0
sasl_pwcheck_method: saslauthd

# new user automated creates
autocreate_sieve_script: /var/spool/cyrus-imap/sieve/phpscript
autocreate_sieve_compiledscript: /var/spool/cyrus-imap/sieve/phpscript.bc
generate_compiled_sieve_script: yes
sieve_maxscriptsize: 64
sieve_maxscripts: 50


autocreateinboxfolders: Spam
autosubscribeinboxfolders: Spam
autocreatequota: 51200
createonpost: yes


# security certificate information
tls_cert_file: /etc/ssl/certs/imap.morningside.edu.crt
tls_key_file: /etc/ssl/certs/imap.morningside.edu.key
tls_ca_file: /etc/ssl/certs/imap.morningside.edu.ca-bundle

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/spool/cyrus-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

  # at least one LMTP is required for delivery
#  lmtp cmd=lmtpd listen=lmtp prefork=0
  lmtpunix  cmd=lmtpd listen=/var/spool/cyrus-imap/socket/lmtp prefork=0

  # this is only necessary if using notifications
  notifycmd=notifyd listen=/var/spool/cyrus-imap/socket/notify
proto=udp prefork=1
}

EVENTS {
  # this is required
  checkpointcmd=ctl_cyrusdb -c period=15

  # this is only necessary if using duplicate delivery suppression
  delprune  cmd=ctl_deliver -E 3 at=0400

  # this is only necessary if caching TLS sessions
  tlsprune  cmd=tls_prune at=0400

Thanks in advance,

Mike


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 DBERROR with avelsieve

2006-10-05 Thread Mike Husmann


On Thu, October 5, 2006 8:49 am, Mike Husmann wrote:
 Hey all,
   I just upgraded the avelsieve plugin in my Squirrelmail site install to 
 1.9.7 and
 have suddenly started receiving errors.  Every time I make a modification 
 using
 the sieve plugin, I get the following error:

 Oct  5 08:24:38 rusty sieve[18879]: DBERROR: error exiting application: 
 Invalid
 argument

I found one additional error coming from sieve that corresponds with the above 
error:

Oct  5 11:57:15 rusty sieve[29932]: DBERROR #65533;^H^H: db4
When using sivtest, I get the same error every time I execute LOGOUT, but only 
when
using TLS...

sivtest -a bebo -u bebo -t  imap.morningside.edu
  this yields the error

sivtest -a bebo -u bebo imap.morningside.edu
  this does not

I am using tls on cyrus 2.2.12..

Something wrong in my config?  Possible bug?

Thanks in advance.

Mike


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 authentication

2006-09-15 Thread Mike Husmann

 Hmm, I don't see a reason, why sieve-logins from a Remote-Machine can fail.

 Except for the Remote-Machine(s) itself. You have the Server configured to
 offer PLAIN to the Clients. Check if the Clients have the Cyrus-SASL
 Mechanism PLAIN (libplain.*) installed.

 If PLAIN is installed, the next step would be to use a network-sniffer and
 look for the Dialog between Server and Client.

This is where things get weird..

If I do a sivtest from a remote machine, here is the result:
---
sivtest -a bebo -u bebo imap.morningside.edu
S: IMPLEMENTATION Cyrus timsieved v2.2.12
S: SASL PLAIN
S: SIEVE fileinto reject envelope vacation imapflags notify subaddress 
relational
comparator-i;ascii-numeric regex
S: STARTTLS
S: OK
Authentication failed. no mechanism available
Security strength factor: 0
C: LOGOUT
Connection closed.
---

On the local machine, this works fine, and prompts for a password.  But from 
what
I'm seeing here, it's dropping the connection because it doesn't think there 
are any
auth mechs available...?

sieveshell has a similar result:
---
\sieveshell -a bebo -u bebo imap.morningside.edu
connecting to imap.morningside.edu
unable to connect to server at /usr/bin/sieveshell line 169.
---
  This is different from the others that include a line about STDIN 
(password). 
Once again, the server drops the connection before it has a chance to
authenticate.

My /etc/pam.d/sieve looks like:
#%PAM-1.0
auth   required pam_nologin.so
auth   sufficient   pam_ldap.so
auth   required pam_pwdb.so shadow nodelay
accountrequired pam_pwdb.so
sessionrequired pam_pwdb.so

And the strangest part of this whole deal is that it has worked flawlessly, as 
it is
set up now, since April.

Mike



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 authentication

2006-09-15 Thread Mike Husmann
 Except for the Remote-Machine(s) itself. You have the Server configured to
 offer PLAIN to the Clients. Check if the Clients have the Cyrus-SASL
 Mechanism PLAIN (libplain.*) installed.


   That's the ticket..  I installed the extra library on my test system and 
found
that indeed network auth had never been broken!  A simple upgrade of my
squirrelmail plugin made it compatible with the php upgrade that had just 
happned
a couple days ago.  I'm off and running again.

Thanks so much,

Mike


 --
   Andreas
 
 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


sieve authentication

2006-09-14 Thread Mike Husmann
Hey Everyone,
  I'm running cyrus-imap v2.2.12 on a Trustix Linux box with saslauthd 
configured to
look to Active Directory via LDAP.  It's worked great since we put it up in 
April.

However, this morning, timsieved quit working out of the blue.  The avelsieve
squirrelmail plugin no longer would authenticate.

Here's what I get from sivtest if I connect from any remote machine:

sivtest -a husmann -u husmann imap -v
S: IMPLEMENTATION Cyrus timsieved v2.2.12
S: SASL PLAIN
S: SIEVE fileinto reject envelope vacation imapflags notify subaddress 
relational
comparator-i;ascii-numeric regex
S: STARTTLS
S: OK
Authentication failed. no mechanism available
Security strength factor: 0
C: LOGOUT
Connection closed.

However, if I connect on localhost, everything (sivtest and sieveshell) work 
great.

I have confirmed that cyrus-master is listening on port 2000:

netstat -tulpen | grep 2000

tcp0  0 0.0.0.0:20000.0.0.0:*   LISTEN  0
  814437418188/cyrus-master
tcp0  0 :::2000 :::*LISTEN  0
  814437218188/cyrus-master

Which explains why I can telnet in, etc...  To my knowledge, nothing has 
changed, so
I'm puzzled as to why it would stop working all of a sudden.

When I try to use sieveshell to log in, I get this in /var/log/imapd/debug:
It doesn't matter whether I log in from localhost or remote, in this case.

Sep 14 11:36:06 rusty master[22152]: about to exec 
/usr/lib/cyrus-imapd/bin/timsieved
Sep 14 11:36:06 rusty sieve[22152]: executed
Sep 14 11:36:06 rusty sieve[22152]: accepted connection

Restarting cyrus doesn't help, and I'm not running any firewall rules with 
iptables...

Any ideas?

Thanks in advance.

Mike


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 authentication

2006-09-14 Thread Mike Husmann

 Show your configuration imapd.conf, cyrus.conf. Hmm, maybe
 hosts.allow/hosts.deny, too.

imapd.conf

# server conf
servername: rusty.morningside.edu
umask: 077
reject8bit: no
quotawarn: 90
timeout: 30
poptimeout: 10
# singleinstancestore: yes

username_to_lower: yes
lmtp_downcase_rcpt: yes
lmtp_over_quota_perm_failure: yes

altnamespace: yes

# user conf
postmaster: postmaster
admins: cyrus cyrusadm

# directory and file locations
configdirectory: /var/spool/cyrus-imap
partition-default: /var/spool/cyrus-imap
sievedir: /var/spool/cyrus-imap/sieve
sendmail: /usr/sbin/sendmail

# authentication
allowanonymouslogin: no
allowplaintext: yes
sasl_mech_list: plain
sasl_minimum_layer: 0
sasl_pwcheck_method: saslauthd

# new user automated creates
autocreate_sieve_script: /var/spool/cyrus-imap/sieve/phpscript
autocreate_sieve_compiledscript: /var/spool/cyrus-imap/sieve/phpscript.bc
generate_compiled_sieve_script: yes
sieve_maxscriptsize: 64
sieve_maxscripts: 50


autocreateinboxfolders: Spam
autosubscribeinboxfolders: Spam
autocreatequota: 51200
createonpost: yes


# security certificate information
tls_cert_file: /etc/ssl/certs/imap.morningside.edu.crt
tls_key_file: /etc/ssl/certs/imap.morningside.edu.key
tls_ca_file: /etc/ssl/certs/imap.morningside.edu.ca-bundle
---
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/spool/cyrus-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

  # at least one LMTP is required for delivery
#  lmtp cmd=lmtpd listen=lmtp prefork=0
  lmtpunix  cmd=lmtpd listen=/var/spool/cyrus-imap/socket/lmtp prefork=0

  # this is only necessary if using notifications
#  notify   cmd=notifyd listen=/var/spool/cyrus-imap/socket/notify
proto=udp prefork=1
}

EVENTS {
  # this is required
  checkpointcmd=ctl_cyrusdb -c period=15

  # this is only necessary if using duplicate delivery suppression
  delprune  cmd=ctl_deliver -E 3 at=0400

  # this is only necessary if caching TLS sessions
  tlsprune  cmd=tls_prune at=0400
}
---
hosts.allow and hosts.deny are both empty.
---
I have been using nscd to cache lookups..  here is it's config:

logfile /var/log/nscd.log
threads 10
max-threads 128
#   server-user nobody
#   stat-user   somebody
debug-level 0
#   reload-count5
paranoiano
#   restart-interval3600

enable-cachepasswd  yes
positive-time-to-live   passwd  660
negative-time-to-live   passwd  20
suggested-size  passwd  1051
check-files passwd  yes
persistent  passwd  yes
shared  passwd  yes

enable-cachegroup   yes
positive-time-to-live   group   3600
negative-time-to-live   group   60
suggested-size  group   1051
check-files group   yes
persistent  group   yes
shared  group   yes

enable-cachehosts   yes
positive-time-to-live   hosts   3600
negative-time-to-live   hosts   20
suggested-size  hosts   1051
check-files hosts   yes
persistent  hosts   yes
shared  hosts   yes

---
Thanks again,

Mike



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