Re: Resolve before transport

2017-10-02 Thread Wietse Venema
Wietse Venema: > Viktor Dukhovni: > > On Sat, Sep 30, 2017 at 09:18:44AM -0400, Wietse Venema wrote: > > > > > > When the concurrency limit for "[addr]:port" permits, the queue > > > > manager would call smtp(8) again (with the original delivery request > > > > and the list of already used address

Re: Resolve before transport

2017-10-02 Thread Viktor Dukhovni
> On Oct 2, 2017, at 7:13 AM, Wietse Venema wrote: > >> An SMTP nexthop corresponds to an unknown >> (to the queue manager) set of destination MX hosts. Lots of domains >> have various google, outlook.com, ... MX hosts, but there's no way >> to know this without doing the MX lookup first. How

Re: Resolve before transport

2017-10-02 Thread Wietse Venema
Viktor Dukhovni: > On Sat, Sep 30, 2017 at 09:18:44AM -0400, Wietse Venema wrote: > > > > When the concurrency limit for "[addr]:port" permits, the queue > > > manager would call smtp(8) again (with the original delivery request > > > and the list of already used addresses, and smtp(8) would attem

Re: Resolve before transport

2017-10-01 Thread Viktor Dukhovni
On Sat, Sep 30, 2017 at 09:18:44AM -0400, Wietse Venema wrote: > > When the concurrency limit for "[addr]:port" permits, the queue > > manager would call smtp(8) again (with the original delivery request > > and the list of already used addresses, and smtp(8) would attemt > > delivery to the first

Re: Resolve before transport

2017-10-01 Thread @lbutlr
On 30 Sep 2017, at 07:18, Wietse Venema wrote: > It could be simple. Suppose there is a 'popular site' counter table > (the opposite of the 'dead site' list) which is indexed by some > idea of 'destination' and which is updated in real time as delivery > agents announce what they are doing. To det

Re: Resolve before transport

2017-09-30 Thread Wietse Venema
Viktor Dukhovni: > On Fri, Sep 29, 2017 at 02:35:14PM -0400, Wietse Venema wrote: > > > > I send my emails via different gateways based on my transport file. Many > > > domains, however, use the same email providers, such as outlook or > > > gmail. Is there a way to check the MX records before the

Re: Resolve before transport

2017-09-29 Thread Viktor Dukhovni
On Fri, Sep 29, 2017 at 02:35:14PM -0400, Wietse Venema wrote: > > I send my emails via different gateways based on my transport file. Many > > domains, however, use the same email providers, such as outlook or > > gmail. Is there a way to check the MX records before the email is sent > > and tran

Re: Resolve before transport

2017-09-29 Thread Wietse Venema
Peter: > Hi guys, > > I send my emails via different gateways based on my transport file. Many > domains, however, use the same email providers, such as outlook or > gmail. Is there a way to check the MX records before the email is sent > and transport it using a specific gateway? Not yet. The s

Re: Resolve before transport

2017-09-29 Thread Marco Pizzoli
On Fri, Sep 29, 2017 at 10:12 AM, Peter wrote: > Hi guys, > > I send my emails via different gateways based on my transport file. Many > domains, however, use the same email providers, such as outlook or > gmail. Is there a way to check the MX records before the email is sent > and transport it u

Re: Resolve before transport

2017-09-29 Thread Viktor Dukhovni
> On Sep 29, 2017, at 12:45 PM, Noel Jones wrote: > >> I send my emails via different gateways based on my transport file. Many >> domains, however, use the same email providers, such as outlook or >> gmail. Is there a way to check the MX records before the email is sent >> and transport it usin

Re: Resolve before transport

2017-09-29 Thread Noel Jones
On 9/29/2017 3:12 AM, Peter wrote: > Hi guys, > > I send my emails via different gateways based on my transport file. Many > domains, however, use the same email providers, such as outlook or > gmail. Is there a way to check the MX records before the email is sent > and transport it using a speci

Resolve before transport

2017-09-29 Thread Peter
Hi guys, I send my emails via different gateways based on my transport file. Many domains, however, use the same email providers, such as outlook or gmail. Is there a way to check the MX records before the email is sent and transport it using a specific gateway? Cheers, Peter