Home › Forums › OS X Server and Client Discussion › Mail › Sieve broken with new Apple security patch
- This topic has 7 replies, 4 voices, and was last updated 20 years, 1 month ago by
BryanDH.
-
AuthorPosts
-
March 22, 2005 at 5:34 am #361041
BryanDH
ParticipantHi:
It looks like the new security patch breaks sieve filtering. My guess is that the Cyrus SASL update in the patch has changed things around…here’s my logs:
Mar 21 21:32:56 localhost master[375]: service sieve pid 3 in BUSY state: sent unavailable message but it is already busy
Mar 21 21:32:56 localhost timsieved[2080]: unable to open LA file: /usr/lib/sasl2/pwauxprop.la
Mar 21 21:32:56 localhost timsieved[2080]: unable to dlopen /usr/lib/sasl2/pwauxprop.so: dlcompat: can’t read object file
Mar 21 21:32:56 localhost timsieved[2080]: Bad IPLOCALPORT value
Mar 21 21:32:56 localhost timsieved[2080]: could not find auxprop plugin, was searching for [all]
Mar 21 21:32:56 localhost timsieved[2080]: OTP: auxprop backend can’t store properties
Mar 21 21:32:56 localhost timsieved[2080]: could not find auxprop plugin, was searching for [all]
Mar 21 21:32:56 localhost timsieved[2080]: OTP: auxprop backend can’t store properties
Mar 21 21:32:56 localhost timsieved[2080]: could not find auxprop plugin, was searching for [all]
Mar 21 21:32:56 localhost timsieved[2080]: OTP: auxprop backend can’t store propertiesI tried reinstalling all of the sieve components, but no luck. Anybody else experiencing this?
Bryan
March 22, 2005 at 1:21 pm #361042woz
ParticipantHey count yourself lucky – my imapd won’t start at all and I’ve been pulling my hair out for the last two hours with no joy.
Mar 22 11:41:17 localhost ./imapd: could not getenv(CYRUS_SERVICE); exiting
Mar 22 11:45:58 localhost deliver[793]: connect(/var/imap/socket/lmtp) failed: Connection refused
Mar 22 11:45:58 localhost deliver[796]: connect(/var/imap/socket/lmtp) failed: Connection refused
Mar 22 11:45:59 localhost deliver[799]: connect(/var/imap/socket/lmtp) failed: Connection refused
Mar 22 11:49:12 localhost deliver[812]: connect(/var/imap/socket/lmtp) failed: Connection refused
Mar 22 11:49:12 localhost deliver[813]: connect(/var/imap/socket/lmtp) failed: Connection refusedAny ideas anyone. I’m running postfix/cyrus/clamav/amavisd as described in the article on this site.
Cheers,
Woz
March 22, 2005 at 4:00 pm #361044BryanDH
ParticipantYeah…it seems like this update has broken quite a few things. It’s unfortunate, because it’s an important security update for cyrus and SASL.
March 23, 2005 at 12:11 am #361051[email protected]
ParticipantAfter the update I ran into two Mail server problems.
1) I was having problems with filters, but after deleting the timsieved.pkg package receipt in /Library/Receipts and then reinstalling the timsieved.pkg.
Filters are now working again.
But I am still having problems with APOP.
When I try to connect with my mail client with APOP I get
-ERR [AUTH] weird SASL error -6 getting SASL_USERNAME
I had to turn APOP off on the mail server before it would allow my mail client to connect via POP3.
I have SSL on my mail server, so clear text passwords aren’t awful, but I would like to get APOP running again.
March 23, 2005 at 1:10 am #361052BryanDH
ParticipantHi:
I think you posted this on the Apple board. I tried the reinstall. No luck on my side.
Bryan
March 23, 2005 at 2:18 pm #361059BryanDH
ParticipantI applied the 10.3.8 Combo Update and things are working again. And it seems Apple pulled the security update.
Bryan
March 23, 2005 at 4:22 pm #361063Dan Dickinson
ParticipantOur /var/imap/mailboxes.db got corrupted. Restoring just that from backup didn’t help; now I’m trying to restore the entire previous version of cyrus.
Real pleasant stuff. If only they had pulled it yesterday BEFORE we installed it.
March 23, 2005 at 9:42 pm #361068BryanDH
ParticipantOne strange side effect after applying the 10.3.8 update…
My IMAP users have no problems at all. POP users discoverd that all messages saved on the server were downloaded again, resulting in duplicate messages. I got a lot of calls this morning about this. One user had 6000 messages stored, all of which came down again! =-O
Bryan
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed