@lbutlr:
> On 2018-03-16 (05:10 MDT), Wietse Venema wrote:
> >=20
> > @lbutlr:
> >>=20
> >> This could be done with a queue scheduler that pre-processes the =
> queue when "a lot" of messages get queued for sending and then sorts =
> them based on destination and the destinations that exceed some
On 2018-03-16 (05:10 MDT), Wietse Venema wrote:
>
> @lbutlr:
>>
>> This could be done with a queue scheduler that pre-processes the queue when
>> "a lot" of messages get queued for sending and then sorts them based on
>> destination and the destinations that exceed some pre-defined threshold g
On 16/03/2018 15:36, Michael Munger wrote:
We've successfully written milters (Google pymilter) that check a
MySQL database to accept inbound mails for anyone who is in this
client's CRM system. Since the postfix box is a front-end to an
Exchange server, the milter triggers a FILTER relay:192.168
We've successfully written milters (Google pymilter) that check a MySQL
database to accept inbound mails for anyone who is in this client's CRM
system. Since the postfix box is a front-end to an Exchange server, the
milter triggers a FILTER relay:192.168.x.x response to pass the email to
Exchange w
@lbutlr:
> On 2018-03-15 (09:01 MDT), Viktor Dukhovni =
> wrote:
> >=20
> > Caching open TLS connections in the smtp(8) delivery agent for
> > reuse by scheduling repeated deliveries to the same delivery
> > agent runs into complex scheduling difficulties. The presence
> > of open con
