On 01/06/13 12:21, Jasen Betts wrote:
On 2013-06-01, Sebastian Arcus wrote:
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 de
On 01/06/13 12:21, Jasen Betts wrote:
RFC4954 only allows (successful) AUTH once per SMTP connection so any
subsequent emails are going out under same authority as the the first
email.
Note that there's an optional AUTH= addition to the MAIL FROM:
which is distinct from the AUTH for the SMTP co
On 2013-06-01, Sebastian Arcus wrote:
>>> 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
On 01/06/13 05:10, Jasen Betts wrote:
On 2013-05-30, Sebastian Arcus 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 = ^$sende
On 2013-05-30, Sebastian Arcus 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_add
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}{$
