Re: Cyrus Muder
Hi, Have been googling for a while now on murder and trying a test set it up on fedora + Mailscanner + postfix + ldap. when I run mupdatetest -u murder -a murder -w murder master (where murder is the username and passwd and master is the name of the master mc defined in /etc/hosts file.) All seems to worl fine from the fronend as well as the backend I can authenticate. The problem arises when I try to send mails from the front end I keep getting a error Nov 23 12:28:59 location postfix/lmtp[19396]: 2DE2E11E5C6: to=[EMAIL PROTECTED], relay=none, delay=68543, delays=68542/0.37/0/0, dsn=4.4.1, status=deferred (connect to location.exampledomain.com[/var/imap/socket/lmtp]: Connection refused) Cant seem to figure this one out... Has any one faced the same problem before? Is your postfix running chrooted? If yes check in master.cf that at least lmtp is not running chrooted. Regards, Simon 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: Murder in replicated mode
On Fri, Nov 23, 2007 at 12:49:38AM -0500, Wesley Craig wrote: On 22 Nov 2007, at 21:01, Diego Woitasen wrote: I tried with that, but doesn't work. I delivered a message in both serves and nothing. Again, the mailbox was replicated when I restart Cyrus. I haven't run mupdate_config: replicated myself, but I assume you need to run mupdate on the backends. Your problem description suggests that ctl_mboxlist is updating mailboxes.db when it's run from the cyrus.conf START section, but you're not getting continuous updates. :wes I have running mupdate in all servers. In my setup, there is no backends. Only two servers, master and slave. -- -- Diego Woitasen 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 and Postfix on separate machines -- how?
I currently have both Postfix (2.3.5) and Cyrus (2.3.9) running on a single server. Postfix does its thing (including spam and virus filtering) and then invokes Cyrus's deliver program to deliver messages. I would like to move my Cyrus onto a separate system from my Postfix. The reason is because I'm having problems with my Cyrus and want to try setting up a new version of Cyrus (2.3.10) on a different platform, but I would prefer to keep my working Postfix setup where it is for now. What's confusing me here is that I'm not sure how to configure Postfix so it can deliver a message over my LAN to a separate Cyrus server, instead of delivering it over a Unix-domain socket to Cyrus running on the same box. Any suggestions? -- Rich Wales === Palo Alto, CA, USA === [EMAIL PROTECTED] http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales 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: LARGE single-system Cyrus installs?
Andrew McNamara wrote: Note that ext3 effectively does the same thing as ZFS on fsync() - because the journal layer is block based and does no know which block belongs to which file, the entire journal must be applied to the filesystem to achieve the expected fsync() symantics (at least, with data=ordered, it does). Well, does not know which block belongs to which file sounds weird. :) With data=ordered, the journal holds only metadata. If you fsync() a file, ordered means that ext3 syncs the data blocks first (with no overhead, just like any other filesystem, of course it knows what blocks to write), then the journal. Now, yes, the journal possibly contains metadata updates for other files too, and the ordered semantics requires the data blocks of those files to be synced as well, before the journal sync. I'm not sure if a fsync() flushes the whole journal or just up to the point it's necessary (that is, up to the last update on the file you're fsync()ing). data=writeback is what some (most) other journalled filesystems do. Metadata updates are allowed to hit the disk _before_ data updates. So, on fsync(), the FS writes all data blocks (still required by fsync() semantics), then the journal (or part of it), but if updates of other files metadata are included in the journal sync, there's not need to write the corresponding data blocks. They'll be written later, and they'll hit the disk _after_ the metadata changes. If power fails in between, you can have a file whose size/time is updated, but contents not. That's the problem with data=writeback, but it should be noted that's pretty normal for other journalled filesystems, too. It applies only to files that were not fsync()'ed. I think that if you're running into performance problems, and your system is doing a lot of fsync(), data=orderer is the worst option. data=journal is fsync()-friendly in one sense, it does write *everything* out, but in one nice sequential (thus extremely fast) shot. Later, data blocks will be written again to the right places. It doubles the I/O bandwith requirements, but if you have a lot of bandwidth, it may be a win. We're talking sequential write bandwidth, which is hardly a problem. data=writeback is fsync() friendly in the sense that it writes only the data blocks of the fsync()'ed file plus (all) metadata. It's the lowest overhead option. If you have a heavy sustained write traffic _and_ lots of fsync()'s, then data=writeback may be the only option. I think some people are scared by data=writeback, but they don't realize it's just what other journalled FS do. I'm not familiar with ReiserFS, it think it's metadata-only as well. data=ordered is good, for general purpose systems. For any application that uses fsync(), it's useless overhead. I've never hit performance problems, my numbers are 200 users with 2000 messages/day delivered to lmtp, _any_ decent PC handles that load easily, and I've never considered turning data=ordered to data=writeback for my filesystems. Now that I think about it, I've also forgot to set noatime after the last HW upgrade (what a luxury!). /me fires vi on /etc/fstab and adds 'noatime' .TM. 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: LARGE single-system Cyrus installs?
On Thu, 22 Nov 2007, Gabor Gombas wrote: On Tue, Nov 20, 2007 at 09:56:37AM -0800, David Lang wrote: for cyrus you should have the same sort of requirements that you would have for a database server, including the fact that without a battery-backed disk cache (or solid state drive) to handle your updates, you end up being throttled by your disk rotation rate (you can only do a single fsync write per rotation, and that good only if you don't have to seek), RAID 5/6 arrays are even worse, as almost all systems will require a read of the entire stripe before writing a single block (and it's parity block) back out, and since the stripe is frequently larger then the OS readahead, the OS throws much of the data away immediatly. You're mixing things up. Readahead has absolutely zero influence on when data is evicted from the cache. if the system is set to do a 1M readahead and to do that readahead it needs to read in 5M of data to verify the integrity, the system doesn't keep all 5M of data in it's cache, only the 1M that is it's readahead (or at least in some cases this is true) David Lang 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 and Postfix on separate machines -- how?
Rich Wales wrote, at 11/23/2007 11:05 PM: I currently have both Postfix (2.3.5) and Cyrus (2.3.9) running on a single server. Postfix does its thing (including spam and virus filtering) and then invokes Cyrus's deliver program to deliver messages. I would like to move my Cyrus onto a separate system from my Postfix. The reason is because I'm having problems with my Cyrus and want to try setting up a new version of Cyrus (2.3.10) on a different platform, but I would prefer to keep my working Postfix setup where it is for now. What's confusing me here is that I'm not sure how to configure Postfix so it can deliver a message over my LAN to a separate Cyrus server, instead of delivering it over a Unix-domain socket to Cyrus running on the same box. Any suggestions? Use LMTP. See lmtp(8) for more details, but you'll probably use something like this in main.cf: mailbox_transport = lmtp:inet:mail.example.com And enable lmtp in cyrus.conf on the destination: lmtp cmd=lmtpd listen=lmtp prefork=0 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 and Postfix on separate machines -- how?
What's confusing me here is that I'm not sure how to configure Postfix so it can deliver a message over my LAN to a separate Cyrus server, instead of delivering it over a Unix-domain socket to Cyrus running on the same box. Any suggestions? Trivial postfix on the cyrus box which accepts mail relayed from the original postfix. More of a postfix configuration problem than cyrus. Or lmtp over tcp. Try man lmtp for the postfix side. I can't imagine the cyrus side is much more complicated. If you're looking for a step-by-step, you'll have to wait for a true guru to respond, but it looks like a little quality time with the Google and the documentation should take you far. 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 and Postfix on separate machines -- how?
Jorey Bump wrote: Use LMTP. See lmtp(8) for more details, but you'll probably use something like this in main.cf: . . . Thanks. That appears to work (I set up a test account and made it use LMTP to the new server via a line in Postfix's transport map). Not surprisingly, I had to add a line to /etc/services on the machines involved to define LMTP (as TCP port 24). -- Rich Wales === Palo Alto, CA, USA === [EMAIL PROTECTED] http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales 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
