7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Integration with ...
FromSent OnAttachments
Paul TansomFeb 10, 2002 8:07 am 
Duck-Ki HongFeb 10, 2002 9:26 am 
Phil BrutscheFeb 10, 2002 11:02 am 
Paul TansomFeb 10, 2002 12:35 pm 
Michael J. Tubby B.Sc (Hons) G8TICFeb 10, 2002 10:56 pm 
Tomas FasthFeb 11, 2002 12:30 am 
Francois PHILIPPOFeb 11, 2002 1:00 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Integration with EximActions...
From:Michael J. Tubby B.Sc (Hons) G8TIC (mike@thorcom.co.uk)
Date:Feb 10, 2002 10:56:40 pm
List:net.sourceforge.lists.courier-users

----- Original Message ----- From: "Paul Tansom" <pa@aptanet.com> To: "Phil Brutsche" <ph@giedi.obix.com> Cc: <cour@lists.sourceforge.net> Sent: Sunday, February 10, 2002 8:35 PM Subject: Re: [courier-users] Integration with Exim

On Sun, Feb 10, 2002 at 01:02:00PM -0600, Phil Brutsche typed the

following...

On Sun, 2002-02-10 at 10:07, Paul Tansom wrote:

My main question at this point (apart from is there a good page for details on configuration!) is: do you have to set exim to drop mail into courier or does courier access the imap directories that exim drops the mail into?

The latter: You define in the Courier-IMAP config where to find the Maildirs, then you tell Exim to put the messages there.

That's good news, I'm thinking along the right lines then.

As an aside to this, from previous experience as a client user of exim I found that it insists on using hidden .files for it's folders. Is there a way of disabling this, as it causes me problems when I use Mutt to access the mail?

It's not something Exim insists on, it's something Courier insists on.

Configure mutt to be an IMAP client.

Funnily enough courier is what I meant to type, the mta was qmail in that setup. Looks like I may have to do the IMAP thing with mutt then, I was hoping to avoid it, but there you go.

...and that's all Phil Brutsche wrote I'm afraid

I think I've narrowed things down to being an authentication issue now. Kind of you not to pick up on my 'doh' moment that I have now twigged :-)

This is corect assuming that you're using Courier-IMAP (rather than full Courier) - I use Exim + Courier-IMAP in this way with a mixture of configurations (simple user account based maildirs, through complex systems with filtering, shared folders and complex in-bound filtering etc.)

You need to ensure that your Exim binary has been built with Maildir support compiled in, from file ../exim-3.34/Local/Makefile:

# The appendfile transport can write messages as individual files in a number # of formats. The code for three specialist formats, maildir, mailstore, and # MBX, is included only when requested by the following settings:

SUPPORT_MAILDIR=yes # SUPPORT_MAILSTORE=yes # SUPPORT_MBX=yes

For the simplest form of delivery (user accounts with Maildir format mailboxes) you need to change the specification of the Exim transport for 'local_delivery' thus

# # old configuration was 'mbox' format # #local_delivery: # driver = appendfile # file = /var/spool/mail/${local_part} # delivery_date_add # envelope_to_add # return_path_add # group = mail # mode = 0660

# # deliver locally into 'maildir' format mailboxes (top level - real users) # local_delivery: driver = appendfile maildir_format directory = ${home}/Maildir/ create_directory prefix = "" suffix = "" check_string = "" escape_string = "" delivery_date_add envelope_to_add return_path_add

Once you've got your Exim configuration you can test it, thus:

/usr/exim/bin/exim -d9 -bt <local email address>

and check that Exim goes through the motions.

Then you can go off and do the fancy LDAP auth stuff with virtual mailboxes etc.