--
[ Picked text/plain from multipart/alternative ]
I tried the lmtp driver and got the following error message on startup:
Starting exim: 2003-04-04 15:59:36 Exim configuration error in line 538:
transport local_delivery: cannot find transport driver "lmtp"
As a sidenote, I've always been confused as to what valid values for the 'driver' option are; I haven't found anything in the exim documentation that lists them. Any thoughts? For the time being I guess I'll keep the pipe and 'deliver' combination in place...
At 10:51 AM 4/4/2003, you wrote:
>Should be more efficient. No need to startup the deliver program each
>time a message is delivered.
>
>The cyrus imap mail archives can probably help (give you better info)
>with that question. :-)
>
>
>
>Derek Stevenson wrote:
>>--
>>[ Picked text/plain from multipart/alternative ]
>>Cyrus 2.1.12. What is the advantage of the lmtp socket delivery over 'deliver'?
>>
>>At 09:32 AM 4/4/2003, you wrote:
>>
>>>What version of Cyrus are you running? If you are running 2.1.x you can
>>>deliver to an LMTP socket instead of using deliver. An example transport:
>>>
>>>local_delivery_cyruslmtpsocket:
>>>driver = lmtp
>>>batch_max = 35
>>>socket = /var/imap/socket/lmtp
>>>user = cyrus
>>>
>>>
>>>Derek Stevenson wrote:
>>>
>>>>--
>>>>[ Picked text/plain from multipart/alternative ]
>>>>Ack! I'm retarded. I mistakenly set user=mail instead of user=exim (DUH!). When user=exim in the sa transport all works as expected, quite handy dandy. Sorry for the confusion! Thanks to Kirill, Patrick, Matthew, and Tony for their patience and helpfulness.
>>>>
>>>>Would it be useful to detail my setup process on this newsgroup, e.g. how to configure exim plus cyrus plus spamassassin? I suspect other more advanced users (read: more competent) haven't had the problems I have run into, but as a relative newcomer I found it difficult to find all the right information to glue these pieces in place. Let me know and I can put together a howto.
>>>>
>>>>Thanks again,
>>>>Derek
>>>>
>>>>At 03:05 AM 4/4/2003, you wrote:
>>>>
>>>>
>>>>>Derek,
>>>>>
>>>>>In your spamcheck transport you have the following:
>>>>>
>>>>># must use a privileged user to set $received_protocol on the way back in!
>>>>>user = cyrus
>>>>>group = mail
>>>>>
>>>>>The cyrus user most likely can not set the $received_protocol so the
>>>>>mail keeps looping back into the spamcheck_router router. Try using:
>>>>>
>>>>>user = root
>>>>>
>>>>>and see if that works.
>>>>
>>>>
>>>>My exim.conf contains a 'never_users = root' and when I set user=root for the sa transport the exim log states 'User 0 set for spamcheck transport is on the never_users list'. If I clear the never_users setting and retry the email, everything works fine! That's good, but I assume the never_users=root is on purpose... Should I leave never_users=root? Can I subsequently give the mail user permission to set the $received_protocol in the transport? Right now if I set 'user = mail' on the transport, I don't think it properly sets the $received_protocol.
>>>>
>>>>--
>>>>
>>>>
>>>>--
>>>>
>>>>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>>>
>>>
>>>--
>>>
>>>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>>>
>>
>>--
>>
>>
>>--
>>
>>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
>--
>
>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
--
