On Wed, Jul 24, 2019 at 11:29:21AM +0100, Jeremy Harris via Exim-users wrote:
> On 19/07/2019 08:12, Viktor Dukhovni via Exim-users wrote:
> > On Fri, Jul 19, 2019 at 09:15:26AM +0300, Evgeniy Berdnikov via Exim-users
> > wrote:
> >>> Might there be a dnssec-related difference?
> >>
> >>
On 19/07/2019 08:12, Viktor Dukhovni via Exim-users wrote:
> On Fri, Jul 19, 2019 at 09:15:26AM +0300, Evgeniy Berdnikov via Exim-users
> wrote:
>>> Might there be a dnssec-related difference?
>>
>> Definitely NO, because this difference is in client's initial packets.
>
> Actually, the
Thanks for your help. I've been away for a few days and not able to test
things. Here's the results of what you ask:
On Fri, Jul 19, 2019 at 01:08:28AM +0300, Evgeniy Berdnikov via Exim-users
wrote:
[SNIP]
> Quite puzzling... The only difference I see here is the presence of one
> authority
On Fri, Jul 19, 2019 at 03:12:38AM -0400, Viktor Dukhovni via Exim-users wrote:
> Actually, the "tcpdump" documentation is misleading. In the attached
> PCAP file (single outbound query), "tcpdump" reports "[1au]", but the
> query has no authority records, rather it has an EDNS(0) OPT record:
On Fri, Jul 19, 2019 at 09:15:26AM +0300, Evgeniy Berdnikov via Exim-users
wrote:
> > Might there be a dnssec-related difference?
>
> Definitely NO, because this difference is in client's initial packets.
Actually, the "tcpdump" documentation is misleading. In the attached
PCAP file (single
> On Jul 18, 2019, at 6:32 PM, Jeremy Harris via Exim-users
> wrote:
>
>> A few anomalies are checked and may result in extra fields enclosed in
>> square brackets: If a query contains an answer, authority records or
>> additional records section, ancount, nscount, or
On Thu, Jul 18, 2019 at 11:32:17PM +0100, Jeremy Harris via Exim-users wrote:
> On 18/07/2019 23:08, Evgeniy Berdnikov via Exim-users wrote:
> > Running tcpdump with -vvv shows that there is an authority record for root.
> > I don't know is this behaviour legal or not, and why this record is
On 18/07/2019 23:08, Evgeniy Berdnikov via Exim-users wrote:
> Quite puzzling... The only difference I see here is the presence of one
> authority record in dns query from Exim, marked as [1au].
> Tcpdump man page states:
>
>A few anomalies are checked and may result in extra fields
On Thu, Jul 18, 2019 at 02:55:54PM +0930, David Purton via Exim-users wrote:
> On Wed, Jul 17, 2019 at 11:12:16AM +0300, Evgeniy Berdnikov via Exim-users
> wrote:
...
> > I propose to install tcpdump and run it in parallel with "exim -qf":
> >
> >tcpdump -nlUv -s0 -i any port domain
...
>
On Wed, Jul 17, 2019 at 11:12:16AM +0300, Evgeniy Berdnikov via Exim-users
wrote:
> On Wed, Jul 17, 2019 at 02:31:59PM +0930, David Purton via Exim-users wrote:
> > On Tue, Jul 16, 2019 at 02:43:12PM +0100, Jeremy Harris via Exim-users
> > wrote:
> ...
> > > ( and grab stderr to a file; it'll be
On Wed, Jul 17, 2019 at 02:31:59PM +0930, David Purton via Exim-users wrote:
> On Tue, Jul 16, 2019 at 02:43:12PM +0100, Jeremy Harris via Exim-users wrote:
...
> > ( and grab stderr to a file; it'll be long.
> > "exim -d+all -qf 2>&1 | tee log" )
>
> Thanks. The relevant part of the resulting
On Tue, Jul 16, 2019 at 11:44:12AM -0700, Ian Zimmerman via Exim-users wrote:
> On 2019-07-16 15:03, David Purton wrote:
>
> > 2019-07-16 14:23:14 Start queue run: pid=12322 -qf
> > 2019-07-16 14:23:14 1hnFQ2-000379-9I no IP address found for host
> > smtp.gmail.com
> > 2019-07-16
On Tue, Jul 16, 2019 at 02:43:12PM +0100, Jeremy Harris via Exim-users wrote:
> On 16/07/2019 06:33, David Purton via Exim-users wrote:
> > I then sign into the network and try and run exim -qf to clear the
> > queue.
> >
> > But the logs then show:
> >
> > 2019-07-16 14:23:14 Start queue
On 2019-07-16 15:03, David Purton wrote:
> 2019-07-16 14:23:14 Start queue run: pid=12322 -qf
> 2019-07-16 14:23:14 1hnFQ2-000379-9I no IP address found for host
> smtp.gmail.com
> 2019-07-16 14:23:14 1hnFQ2-000379-9I == exam...@hotmail.com R=smarthost
> defer (-1): lookup failed
On 16/07/2019 06:33, David Purton via Exim-users wrote:
> I then sign into the network and try and run exim -qf to clear the
> queue.
>
> But the logs then show:
>
> 2019-07-16 14:23:14 Start queue run: pid=12322 -qf
> 2019-07-16 14:23:14 1hnFQ2-000379-9I no IP address found for host
>
I'm having all sorts of problems getting Exim to deliver via the right
smart host (based on domain of from email). This is running on a laptop
so I'm often moving between networks. *Mostly* it works. But on some
networks, one or other of the smarthost routers fails for varying
reasons.
I'm not
16 matches
Mail list logo
