Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-08 Thread Greg Pfister 

Hi Guys,


The problem has been resolved.  It was an upstream DNS server problem.  
Messages queue is processing as it should.




No more soft errors on testmxlookup.




On 1/8/21 11:49 PM, PICCORO McKAY Lenz wrote:

El vie, 8 de ene. de 2021 a la(s) 08:01, Sam Varshavchik
(mr...@courier-mta.com) escribió:

Greg Pfister writes:


« HTML content follows »

Hi Sam,


soft error on the domain.

softfails for  lookups if the A lookup succeeded. Before 1.0.10 the only
option is to rebuild Courier using --without-ipv6

as i fixed in my personal packages.. XD puff i know that was a
problem.. 1.0.14 works better and i also backported  inclusively for
wheezy



___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap


___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap



___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-08 Thread PICCORO McKAY Lenz 
El vie, 8 de ene. de 2021 a la(s) 08:01, Sam Varshavchik
(mr...@courier-mta.com) escribió:
>
> Greg Pfister writes:
>
> > « HTML content follows »
> >
> > Hi Sam,
> >
> >
> > soft error on the domain.
> softfails for  lookups if the A lookup succeeded. Before 1.0.10 the only
> option is to rebuild Courier using --without-ipv6
as i fixed in my personal packages.. XD puff i know that was a
problem.. 1.0.14 works better and i also backported  inclusively for
wheezy

>
>
> ___
> Courier-imap mailing list
> Courier-imap@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap


___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-08 Thread Sam Varshavchik 

Greg Pfister writes:


« HTML content follows »

Hi Sam,


soft error on the domain.


The Debian package "courier-mta-ssl is a transitional package and can be  
ignored.  This system is not new, but years old (more than 5).  Nothing  
recently been done to it other than fail2ban.  However, I've checked both  
with and without fail2ban services - no affect.




Before I posted, I checked mx and A record existence and could access hosted  
server from telnet - from the same system as Courier.


Like I wrote before, this was observed before due to broken IPv6 in either  
the authoritative, intermediate, or caching nameservers. Courier does   
lookups even on IPv4-only hosts; and there was a change in 1.0.10 to ignore  
softfails for  lookups if the A lookup succeeded. Before 1.0.10 the only  
option is to rebuild Courier using --without-ipv6





pgpDZ8lbB7wIP.pgp
Description: PGP signature
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-07 Thread Greg Pfister 

Hi Sam,


soft error on the domain.


The Debian package "courier-mta-ssl is a transitional package and can be 
ignored.  This system is not new, but years old (more than 5).  Nothing 
recently been done to it other than fail2ban. However, I've checked both 
with and without fail2ban services - no affect.




Before I posted, I checked mx and A record existence and could access 
hosted server from telnet - from the same system as Courier.




The recipient domain is eagleofva.com


nslookup -type=mx eagleofva.com

Server:        75.75.75.75
Address:    75.75.75.75#53

Non-authoritative answer:
eagleofva.com    mail exchanger = 20 eagleofva.com.2.0001.arsmtp.com.
eagleofva.com    mail exchanger = 10 eagleofva.com.1.0001.arsmtp.com.


nslookup eagleofva.com.1.0001.arsmtp.com

Server:        192.168.1.13
Address:    192.168.1.13#53

Non-authoritative answer:
Name:    eagleofva.com.1.0001.arsmtp.com
Address: 8.31.233.64



Checked above on another computer outside of the courier server system - 
same results.




telnet 8.31.233.64 25

Trying 8.31.233.64...
Connected to 8.31.233.64.
Escape character is '^]'.
220 server232.appriver.com ESMTP srv-y
ehlo 
250-inbound.appriver.com we trust you 
250-DSN
250-SIZE 104857600
250-STARTTLS
250-ETRN
250-TURN
250-ATRN
250-NO-SOLICITING
250-8BITMIME
250-HELP
250-PIPELINING
250-SMTPUTF8
250 EHLO

Telnet to dns produces same result.





On 1/7/21 7:59 PM, Sam Varshavchik wrote:

Greg Pfister writes:


System: Debian 4.19.0-6-amd64 (Buster 10)


Courier (mta): 1.0.6-1

Courier mta ssl: 0.76.3-5+de


I don't know what this means. There is no "courier mta ssl" package. 
Both 1.0.6 and 0.76.3 look like version of courier, with 0.76 being 
quite old. But I, presume, you only have one version installed.



Any help would be appreciated.


I know I'm missing something, but since I'm able to telnet send an 
email FROM the courier server to one of the servers in question, I 
think it must be a courier issue.  Could be wrong - been known to 
happen.rarely.


Use the testmxlookup command to make DNS MX queries using Courier's 
resolver.


Prior to 1.0.10 a domain with a malfunctioning DNS server that fails 
IPv6 queries would result in this behavior, even on IPv4-only senders 
and recipients.





See what dig comes back with when querying the MX hostnames for  
records.




dig eagleofva.com mx

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> eagleofva.com mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17283
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;eagleofva.com.            IN    MX

;; ANSWER SECTION:
eagleofva.com.        3600    IN    MX    20 
eagleofva.com.2.0001.arsmtp.com.
eagleofva.com.        3600    IN    MX    10 
eagleofva.com.1.0001.arsmtp.com.


;; Query time: 46 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Thu Jan 07 21:11:34 EST 2021
;; MSG SIZE  rcvd: 118





dig eagleofva.com.1.0001.arsmtp.com


; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> eagleofva.com.1.0001.arsmtp.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54906
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 03de54456e6c248571806bd05ff7c1ebcfd04c17b18547c0 (good)
;; QUESTION SECTION:
;eagleofva.com.1.0001.arsmtp.com. IN    A

;; ANSWER SECTION:
eagleofva.com.1.0001.arsmtp.com. 588 IN    A    8.31.233.64

;; AUTHORITY SECTION:
arsmtp.com.        42119    IN    NS    mdns2.appriver.com.
arsmtp.com.        42119    IN    NS    mdns1.appriver.com.

;; ADDITIONAL SECTION:
mdns1.appriver.com.    42119    IN    A    162.159.24.198
mdns2.appriver.com.    42119    IN    A    162.159.25.100
mdns1.appriver.com.    42119    IN     2400:cb00:2049:1::a29f:18c6
mdns2.appriver.com.    42119    IN     2400:cb00:2049:1::a29f:1964

;; Query time: 0 msec
;; SERVER: 192.168.1.13#53(192.168.1.13)
;; WHEN: Thu Jan 07 21:22:35 EST 2021
;; MSG SIZE  rcvd: 241






resent to list


--

Greg Pfister








___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe:https://lists.sourceforge.net/lists/listinfo/courier-imap
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-07 Thread Greg Pfister 

Piccoro McKay Lenz,


Been on Buster as production for some time now (over a year - and no, I 
did not update on initial release, waited almost 6 months). This is the 
first problem I've run into - and it wouldn't have mattered if I was on 
Stretch or Buster, as per Sam.



On 1/7/21 8:25 PM, PICCORO McKAY Lenz wrote:


El jue, 7 de ene. de 2021 a la(s) 21:01, Sam Varshavchik 
(mr...@courier-mta.com ) escribió:


Greg Pfister writes:

> System: Debian 4.19.0-6-amd64 (Buster 10)
>
>
> Courier (mta): 1.0.6-1
>
> Courier mta ssl: 0.76.3-5+de

I don't know what this means. There is no "courier mta ssl"
package. Both
1.0.6 and 0.76.3 look like version of courier, with 0.76 being
quite old.
But I, presume, you only have one version installed.

you have a shit named buster.. use debian 9 strecht..

seems you upgraded f.. cos the 0.76 was the previous and the last from 
buser are 1.0.6, so the old packages xxx-ssl where removed and merged 
inside the non ssl and by default all are ssl..


your problem seems that you still have old files in your system.. 
that's why i never upgraded to that "thing" named buster and pacakaged 
my own debian courier package.. in vegnuli OBS repository


Prior to 1.0.10 a domain with a malfunctioning DNS server that
fails IPv6
queries would result in this behavior, even on IPv4-only senders and
recipients.

grrr that was happened to me i asked so many times.. noted now.. pujff


See what dig comes back with when querying the MX hostnames for
 records.

it seems he said that was working and now does not work.. so i 
guess was an upgrade.. a bad upgrade .. stretch was the one.. not buster


i reported several issues to debian about the package and i backported 
the lasted 1.0.14 to any other but not the shit of buster , Greg Pfister




___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net

Unsubscribe:
https://lists.sourceforge.net/lists/listinfo/courier-imap




___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-07 Thread PICCORO McKAY Lenz 
El jue, 7 de ene. de 2021 a la(s) 21:01, Sam Varshavchik (
mr...@courier-mta.com) escribió:

> Greg Pfister writes:
>
> > System: Debian 4.19.0-6-amd64 (Buster 10)
> >
> >
> > Courier (mta): 1.0.6-1
> >
> > Courier mta ssl: 0.76.3-5+de
>
> I don't know what this means. There is no "courier mta ssl" package. Both
> 1.0.6 and 0.76.3 look like version of courier, with 0.76 being quite old.
> But I, presume, you only have one version installed.
>
you have a shit named buster.. use debian 9 strecht..

seems you upgraded f.. cos the 0.76 was the previous and the last from
buser are 1.0.6, so the old packages xxx-ssl where removed and merged
inside the non ssl and by default all are ssl..

your problem seems that you still have old files in your system.. that's
why i never upgraded to that "thing" named buster and pacakaged my own
debian courier package.. in vegnuli OBS repository


> Prior to 1.0.10 a domain with a malfunctioning DNS server that fails IPv6
> queries would result in this behavior, even on IPv4-only senders and
> recipients.
>
grrr that was happened to me i asked so many times.. noted now.. pujff


>
> See what dig comes back with when querying the MX hostnames for 
> records.
>
it seems he said that was working and now does not work.. so i guess was an
upgrade.. a bad upgrade .. stretch was the one.. not buster

i reported several issues to debian about the package and i backported the
lasted 1.0.14 to any other but not the shit of buster , Greg Pfister


>
>
> ___
> Courier-imap mailing list
> Courier-imap@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
>
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Re: [Courier-imap] Something New: DNS failure messages or "network down" error, yet neither are true

2021-01-07 Thread Sam Varshavchik 

Greg Pfister writes:


System: Debian 4.19.0-6-amd64 (Buster 10)


Courier (mta): 1.0.6-1

Courier mta ssl: 0.76.3-5+de


I don't know what this means. There is no "courier mta ssl" package. Both  
1.0.6 and 0.76.3 look like version of courier, with 0.76 being quite old.  
But I, presume, you only have one version installed.



Any help would be appreciated.


I know I'm missing something, but since I'm able to telnet send an email  
FROM the courier server to one of the servers in question, I think it must  
be a courier issue.  Could be wrong - been known to happen.rarely.


Use the testmxlookup command to make DNS MX queries using Courier's resolver.

Prior to 1.0.10 a domain with a malfunctioning DNS server that fails IPv6  
queries would result in this behavior, even on IPv4-only senders and  
recipients.


See what dig comes back with when querying the MX hostnames for  records.




pgpKyGX8e2gkN.pgp
Description: PGP signature
___
Courier-imap mailing list
Courier-imap@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap