On 01/06/13 05:10, Jasen Betts wrote:
> On 2013-05-30, Sebastian Arcus <shop@???> wrote:
>> I use the following client authenticator to connect my Exim in smart
>> relay to my provider's SMTP server and send email:
>>
>> fixed_plain_client:
>> driver = plaintext
>> public_name = PLAIN
>> client_send = ^$sender_address^${lookup{$sender_address}\
>> lsearch{/etc/exim/exim-client.passwd}{$value}{fail}}
>>
>> It is all working fine, but there are two things I would need some
>> clarification about:
>>
>> 1. Does Exim authenticate as a client and send one message at a time by
>> default (and authenticate again for next message to be sent) - or does
>> it try to send several messages on the same authentication session?
>
> By default the smtp transport will send as many emails as possible,
> you can set connection_max_messages to 1 to limit this to a single
> email per connection, or you can create several tranports one for each
> user.
>
>> 2. If it tries to send several messages in one go after authenticating -
>> what does $sender_address refer to? Is it the sender address of the
>> first message which it tries to send?
>
> It's empty unless they all have the same sender. (same deal with all
> other variables in the smtp transport)
>
Thank you for the info Jasen. I've been using $sender_address in client
authenticator for smtp smart relay for 3-4 years now. I don't use
$connection_max_messages (yet). These are sites with up to 10
workstations connecting to the internal smtp server (which in turn
relays to the provider's smtp server). I haven't had any problems with
this so far - as far as I know. Would this mean that I was just lucky,
and exim happened to be sending just one message at a time out of sheer
luck?
Sebastian
--
Linux vehicle CCTV -
www.open-t.co.uk/iroko
