Demi M. Obenour:
> >> I am not sure whether adding such a feature motivated by just the
> >> presented use-case is warranted.
> >
> > My take: not if it only solves only one problem.
>
> I agree. In particular, we should avoid a pile of features with very
> narrow use-cases.
I think that this n
On 1/16/21 5:12 PM, Wietse Venema wrote:
> Viktor Dukhovni:
>> On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
>>
>>> On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
>>>
My goal is to conditionally select the relayhost based on the total size
of the outgoing m
On 16 Jan 2021, at 02:48, Viktor Dukhovni wrote:
> Since the queue manager has no mechanism for size-dependent selection of
> a default transport
Postfix does, however, know the size of the message based if it is over or
under the message_size_limit, and it must know that before the message hits
Viktor Dukhovni:
> On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
>
> > On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
> >
> > > My goal is to conditionally select the relayhost based on the total size
> > > of the outgoing message. The rationale is that I'm using A
On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
> On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
>
> > My goal is to conditionally select the relayhost based on the total size
> > of the outgoing message. The rationale is that I'm using Amazon AWS SES
> > for the mo
On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
> My goal is to conditionally select the relayhost based on the total size
> of the outgoing message. The rationale is that I'm using Amazon AWS SES
> for the most part. Alas, SES only accepts messages up to 10 MB in size
> (this includ
