Re: [CentOS] Mail has quit working

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Monday, August 27, 2018 10:16 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Mail has quit working
> 
> 
> > Date: Monday, August 27, 2018 09:57:01 -0400
> > From: TE Dukes 
> >
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> centos--- via CentOS
> >> Sent: Monday, August 27, 2018 9:31 AM
> >>
> >> On 08/27/2018 09:05 AM, TE Dukes wrote:
> >> >
> >> >
> >> > Thanks again! I still think it's a mail issue. I can't get mail
> >> > using usermin either.
> >> >
> >> > Think I'm going to remove the TLS stuff from postfix main.cf
> >> > that I added yesterday and retry.
> >>
> >> If I missed this further up thread my apologies - is SELinux
> >> enabled and are there any relevant exceptions being logged?
> >
> > Pretty sure SELinux is turned off unless it got turned on without my
> > knowledge through an updtate/upgrade.
> >
> > I removed the TLS lines from main.cf I added last night and
> > remotely did a reboot from here at work.
> >
> > Mail is again working!! I am skeptical to mark this thread solved
> > as I thought it was solved back in July.
> >
> > I think, removing my ISP's DNS servers from resolve.conf was the
> > fix, could be removing IPV6 from etc/hosts. Might put it back in
> > just to see.
> >
> 
> As I indicated earlier, removing those lines from your postfix config
> will have no impact on your ability to reach your roundcube instance.
> 
> Unlike the windowz world, you mostly don't need to "reboot" a machine
> after making changes to a service (e.g., your postfix config change).
> An unnecessary reboot can bring in many issues so makes debugging a
> problem difficult. Instead, restart the service in question (often a
> reload is all that's needed, but a service restart generally doesn't
> hurt in a single/lower user environment).
> 
> Unless you are VPN-ing (or equiv) my sense is that you are currently
> getting to your mail (roundcube) from outside your network. Earlier,
> when it wasn't working, my sense was that you were inside. If that's
> true you can't really tell if your issue has been resolved as you are
> coming at things from different network directions.
> 

The mail in question is system mail sent via cron. I access it from both
inside the network and outside. Due to being on a dynamic ip, I can't send
mail to the outside but I can receive it.

Again, really appreciate the help!!

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Very odd: /proc/sys/net/ipv6/conf/all/disable_ipv6

[mark]

CentOS 7.5, and on one system, I'm getting:
 setroubleshoot: SELinux is preventing /usr/sbin/sendmail.sendmail from
read access on the file disable_ipv6

ll -Z shows
-rw-r--r--. root root system_u:object_r:sysctl_net_t:s0
/proc/sys/net/ipv6/conf/all/disable_ipv6

I find this peculiar. Anyone have a resolution, or is this a bug?

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-es] SAMBA + Postadmin

[David González Romero]

Hola gente!!

Existe forma de que SAMBA use la estructura y BD de un postadmin para los
usuarios de SAMBA?

Solo pregunto para saber si es posible...No he intentado nada... aun 
Saludos,
David
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] Mail has quit working

[Richard]

> Date: Monday, August 27, 2018 09:57:01 -0400
> From: TE Dukes 
>
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> centos--- via CentOS
>> Sent: Monday, August 27, 2018 9:31 AM
>> 
>> On 08/27/2018 09:05 AM, TE Dukes wrote:
>> > 
>> > 
>> > Thanks again! I still think it's a mail issue. I can't get mail
>> > using usermin either.
>> > 
>> > Think I'm going to remove the TLS stuff from postfix main.cf
>> > that I added yesterday and retry.
>> 
>> If I missed this further up thread my apologies - is SELinux
>> enabled and are there any relevant exceptions being logged?
> 
> Pretty sure SELinux is turned off unless it got turned on without my
> knowledge through an updtate/upgrade.
> 
> I removed the TLS lines from main.cf I added last night and
> remotely did a reboot from here at work.
> 
> Mail is again working!! I am skeptical to mark this thread solved
> as I thought it was solved back in July.
> 
> I think, removing my ISP's DNS servers from resolve.conf was the
> fix, could be removing IPV6 from etc/hosts. Might put it back in
> just to see.
> 

As I indicated earlier, removing those lines from your postfix config
will have no impact on your ability to reach your roundcube instance.

Unlike the windowz world, you mostly don't need to "reboot" a machine
after making changes to a service (e.g., your postfix config change).
An unnecessary reboot can bring in many issues so makes debugging a
problem difficult. Instead, restart the service in question (often a
reload is all that's needed, but a service restart generally doesn't
hurt in a single/lower user environment).

Unless you are VPN-ing (or equiv) my sense is that you are currently
getting to your mail (roundcube) from outside your network. Earlier,
when it wasn't working, my sense was that you were inside. If that's
true you can't really tell if your issue has been resolved as you are
coming at things from different network directions.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of centos---
> via CentOS
> Sent: Monday, August 27, 2018 9:31 AM
> To: centos@centos.org
> Subject: Re: [CentOS] Mail has quit working
> 
> 
> 
> On 08/27/2018 09:05 AM, TE Dukes wrote:
> >
> >> -Original Message-
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> >> Sent: Monday, August 27, 2018 7:58 AM
> >> To: CentOS mailing list
> >> Subject: Re: [CentOS] Mail has quit working
> >>
> >>> Date: Monday, August 27, 2018 07:42:48 -0400
> >>> From: TE Dukes 
> >>>
>  From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>  Richard Sent: Monday, August 27, 2018 7:29 AM
> >>>
> 
>  Since the localhost4 approach worked, commend out the ipv6
>  localhost entries in your /etc/hosts file, then try:
> 
> >>> IP6 is commented out
> >>>
>   dig @localhost localhost a
> >>>
> >>> That works
> 
>  again. If that works try:
> 
>   telnet localhost 143
> >>>
> >>> This also works
> 
>  once again. If those work, it would seem that your ipv6 is messed
>  up and your system is trying it first and not falling back to ipv4.
> 
>  Regarding your nameserver list in /etc/resolv.conf. If you have a
>  working 127.0.0.1 nameserver you generally don't include external
>  nameservers in that list. So, if non-ipv6 things seem to work, I'd
>  remove the two non-127 nameservers from that list.
> 
> >>> Removed the two nameservers. Still can't access mail. Getting
> >>> connection to storage server failed on the roundcube login page.
> 
> >>
> >> That you can now successfully get to "localhost" is good progress.
> >> Seems you want to stay away from ipv6 networking issues unless/until
> >> you resolve whatever that issue is.
> >>
> >> Roundcube is, potentially, a totally separate issue. I don't use it,
> >> so can only suggest minimal debugging ideas.
> >>
> >> What is the hostname that you use to get to your roundcube instance?
> >> Can you resolve that:
> >>
> >> dig  a
> >>
> >> If you get an answer, is the ipnumber correct?
> >>
> >
> > ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a
> > ;; global options: +cmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652
> > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3
> >
> > ;; OPT PSEUDOSECTION:
> > ; EDNS: version: 0, flags:; udp: 4096
> > ;; QUESTION SECTION:
> > ;mail.palmettodomains.com.  IN  A
> >
> > ;; ANSWER SECTION:
> > mail.palmettodomains.com. 86400 IN  A   192.169.1.110
> >
> > ;; AUTHORITY SECTION:
> > palmettodomains.com.86400   IN  NS
>   dns1.palmettodomains.com.
> >
> > ;; ADDITIONAL SECTION:
> > dns1.palmettodomains.com. 86400 IN  A   192.168.1.110
> > dns1.palmettodomains.com. 86400 IN  :::110
> >
> > ;; Query time: 0 msec
> > ;; SERVER: 127.0.0.1#53(127.0.0.1)
> > ;; WHEN: Mon Aug 27 09:01:48 EDT 2018
> > ;; MSG SIZE  rcvd: 132
> >
> >> Note, if the hostname for your roundcube instance is one of the ipv6
> >> entries in your /etc/hosts file, I'd remove that - and either put in
> >> an ipv4 entry or put an entry for it in your dns.
> >>
> >
> > Thanks again! I still think it's a mail issue. I can't get mail using
> > usermin either.
> >
> > Think I'm going to remove the TLS stuff from postfix main.cf that I
added
> > yesterday and retry.
> 
> If I missed this further up thread my apologies - is SELinux enabled and
> are there any relevant exceptions being logged?

Pretty sure SELinux is turned off unless it got turned on without my
knowledge through an updtate/upgrade.

I removed the TLS lines from main.cf I added last night and remotely did a
reboot from here at work.

Mail is again working!! I am skeptical to mark this thread solved as I
thought it was solved back in July.

I think, removing my ISP's DNS servers from resolve.conf was the fix, could
be removing IPV6 from etc/hosts. Might put it back in just to see.

Again, many, many thanks!!

I really want to thank everyone for their help and patience!!

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[centos--- via CentOS]

On 08/27/2018 09:05 AM, TE Dukes wrote:



-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
Sent: Monday, August 27, 2018 7:58 AM
To: CentOS mailing list
Subject: Re: [CentOS] Mail has quit working


Date: Monday, August 27, 2018 07:42:48 -0400
From: TE Dukes 


From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
Richard Sent: Monday, August 27, 2018 7:29 AM




Since the localhost4 approach worked, commend out the ipv6
localhost entries in your /etc/hosts file, then try:


IP6 is commented out


 dig @localhost localhost a


That works


again. If that works try:

 telnet localhost 143


This also works


once again. If those work, it would seem that your ipv6 is messed
up and your system is trying it first and not falling back to ipv4.

Regarding your nameserver list in /etc/resolv.conf. If you have a
working 127.0.0.1 nameserver you generally don't include external
nameservers in that list. So, if non-ipv6 things seem to work, I'd
remove the two non-127 nameservers from that list.


Removed the two nameservers. Still can't access mail. Getting
connection to storage server failed on the roundcube login page.




That you can now successfully get to "localhost" is good progress.
Seems you want to stay away from ipv6 networking issues unless/until
you resolve whatever that issue is.

Roundcube is, potentially, a totally separate issue. I don't use it,
so can only suggest minimal debugging ideas.

What is the hostname that you use to get to your roundcube instance?
Can you resolve that:

dig  a

If you get an answer, is the ipnumber correct?



; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mail.palmettodomains.com.  IN  A

;; ANSWER SECTION:
mail.palmettodomains.com. 86400 IN  A   192.169.1.110

;; AUTHORITY SECTION:
palmettodomains.com.86400   IN  NS  dns1.palmettodomains.com.

;; ADDITIONAL SECTION:
dns1.palmettodomains.com. 86400 IN  A   192.168.1.110
dns1.palmettodomains.com. 86400 IN  :::110

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Aug 27 09:01:48 EDT 2018
;; MSG SIZE  rcvd: 132


Note, if the hostname for your roundcube instance is one of the ipv6
entries in your /etc/hosts file, I'd remove that - and either put in
an ipv4 entry or put an entry for it in your dns.



Thanks again! I still think it's a mail issue. I can't get mail using
usermin either.

Think I'm going to remove the TLS stuff from postfix main.cf that I added
yesterday and retry.


If I missed this further up thread my apologies - is SELinux enabled and 
are there any relevant exceptions being logged?

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[mark]

Richard wrote:
>> Date: Monday, August 27, 2018 09:05:05 -0400
>> From: TE Dukes 
>>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>>> Richard Sent: Monday, August 27, 2018 7:58 AM
 Date: Monday, August 27, 2018 07:42:48 -0400
 From: TE Dukes 
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> Richard Sent: Monday, August 27, 2018 7:29 AM
>
> Since the localhost4 approach worked, commend out the ipv6
> localhost entries in your /etc/hosts file, then try:
>
 IP6 is commented out


> dig @localhost localhost a

 That works

>
> again. If that works try:
>
> telnet localhost 143

 This also works

>
> once again. If those work, it would seem that your ipv6 is messed
> up and your system is trying it first and not falling back to
> ipv4.
>
> Regarding your nameserver list in /etc/resolv.conf. If you have
> a working 127.0.0.1 nameserver you generally don't include external
> nameservers in that list. So, if non-ipv6 things seem to work, I'd
> remove the two non-127 nameservers from that list.
>
 Removed the two nameservers. Still can't access mail. Getting
 connection to storage server failed on the roundcube login page.
>
>>>
>>> That you can now successfully get to "localhost" is good progress.
>>> Seems you want to stay away from ipv6 networking issues
>>> unless/until you resolve whatever that issue is.
>>>
>>> Roundcube is, potentially, a totally separate issue. I don't use
>>> it, so can only suggest minimal debugging ideas.
>>>
>>> What is the hostname that you use to get to your roundcube
>>> instance? Can you resolve that:
>>>
>>> dig  a
>>>
>>> If you get an answer, is the ipnumber correct?
>>>
>>>
>>
>> ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652
>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
>> ADDITIONAL: 3
>>
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 4096
>> ;; QUESTION SECTION:
>> ;mail.palmettodomains.com.   IN  A
>>
>>
>> ;; ANSWER SECTION:
>> mail.palmettodomains.com. 86400  IN  A   192.169.1.110
>>
>> ;; AUTHORITY SECTION:
>> palmettodomains.com. 86400   IN  NS  dns1.palmettodomains.com.
>>
>> ;; ADDITIONAL SECTION:
>> dns1.palmettodomains.com. 86400  IN  A   192.168.1.110
>> dns1.palmettodomains.com. 86400  IN  :::110
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 127.0.0.1#53(127.0.0.1)
>> ;; WHEN: Mon Aug 27 09:01:48 EDT 2018
>> ;; MSG SIZE  rcvd: 132
>>
>>
>>> Note, if the hostname for your roundcube instance is one of the
>>> ipv6 entries in your /etc/hosts file, I'd remove that - and either put
>>> in an ipv4 entry or put an entry for it in your dns.
>>>
>>
>> Thanks again! I still think it's a mail issue. I can't get mail
>> using usermin either.
>>
>> Think I'm going to remove the TLS stuff from postfix main.cf that I
>> added yesterday and retry.
>
> Those TLS lines that you added to your postfix config file yesterday
> have nothing to do with your ability (or not) to get to your roundcube
> instance. I believe that the roundcube frontend is an application that
> runs via httpd/apache. Assuming I am correct on that, debugging your
> apache setup would be the next set of things to look at. Confirm that it
> (apache) is running and listening on the
> port(s) you expect it on (netstat and ps will help there) and then start
> with the access and error logs.
>

Pardon me if I butt in - I haven't really been following this thread, but
what's selinux set to - off, permissive, enforcing?

 mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[Richard]

> Date: Monday, August 27, 2018 09:05:05 -0400
> From: TE Dukes 

>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> Richard Sent: Monday, August 27, 2018 7:58 AM
>> 
>> > Date: Monday, August 27, 2018 07:42:48 -0400
>> > From: TE Dukes 
>> > 
>> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> >> Richard Sent: Monday, August 27, 2018 7:29 AM
>> > 
>> >> 
>> >> Since the localhost4 approach worked, commend out the ipv6
>> >> localhost entries in your /etc/hosts file, then try:
>> >> 
>> > IP6 is commented out
>> > 
>> >> dig @localhost localhost a
>> > 
>> > That works
>> >> 
>> >> again. If that works try:
>> >> 
>> >> telnet localhost 143
>> > 
>> > This also works
>> >> 
>> >> once again. If those work, it would seem that your ipv6 is
>> >> messed up and your system is trying it first and not falling
>> >> back to ipv4.
>> >> 
>> >> Regarding your nameserver list in /etc/resolv.conf. If you have
>> >> a working 127.0.0.1 nameserver you generally don't include
>> >> external nameservers in that list. So, if non-ipv6 things seem
>> >> to work, I'd remove the two non-127 nameservers from that list.
>> >> 
>> > Removed the two nameservers. Still can't access mail. Getting
>> > connection to storage server failed on the roundcube login page.
>> >> 
>> 
>> That you can now successfully get to "localhost" is good progress.
>> Seems you want to stay away from ipv6 networking issues
>> unless/until you resolve whatever that issue is.
>> 
>> Roundcube is, potentially, a totally separate issue. I don't use
>> it, so can only suggest minimal debugging ideas.
>> 
>> What is the hostname that you use to get to your roundcube
>> instance? Can you resolve that:
>> 
>>dig  a
>> 
>> If you get an answer, is the ipnumber correct?
>> 
> 
> ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
> ADDITIONAL: 3
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;mail.palmettodomains.com.IN  A
> 
> ;; ANSWER SECTION:
> mail.palmettodomains.com. 86400   IN  A   192.169.1.110
> 
> ;; AUTHORITY SECTION:
> palmettodomains.com.  86400   IN  NS  dns1.palmettodomains.com.
> 
> ;; ADDITIONAL SECTION:
> dns1.palmettodomains.com. 86400   IN  A   192.168.1.110
> dns1.palmettodomains.com. 86400   IN  :::110
> 
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Mon Aug 27 09:01:48 EDT 2018
> ;; MSG SIZE  rcvd: 132
> 
>> Note, if the hostname for your roundcube instance is one of the
>> ipv6 entries in your /etc/hosts file, I'd remove that - and either
>> put in an ipv4 entry or put an entry for it in your dns.
>> 
> 
> Thanks again! I still think it's a mail issue. I can't get mail
> using usermin either. 
> 
> Think I'm going to remove the TLS stuff from postfix main.cf that I
> added yesterday and retry.

Those TLS lines that you added to your postfix config file yesterday
have nothing to do with your ability (or not) to get to your
roundcube instance. I believe that the roundcube frontend is an
application that runs via httpd/apache. Assuming I am correct on
that, debugging your apache setup would be the next set of things to
look at. Confirm that it (apache) is running and listening on the
port(s) you expect it on (netstat and ps will help there) and then
start with the access and error logs.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Monday, August 27, 2018 7:58 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Mail has quit working
> 
> 
> 
> > Date: Monday, August 27, 2018 07:42:48 -0400
> > From: TE Dukes 
> >
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> Richard Sent: Monday, August 27, 2018 7:29 AM
> >
> >>
> >> Since the localhost4 approach worked, commend out the ipv6
> >> localhost entries in your /etc/hosts file, then try:
> >>
> > IP6 is commented out
> >
> >> dig @localhost localhost a
> >
> > That works
> >>
> >> again. If that works try:
> >>
> >> telnet localhost 143
> >
> > This also works
> >>
> >> once again. If those work, it would seem that your ipv6 is messed
> >> up and your system is trying it first and not falling back to ipv4.
> >>
> >> Regarding your nameserver list in /etc/resolv.conf. If you have a
> >> working 127.0.0.1 nameserver you generally don't include external
> >> nameservers in that list. So, if non-ipv6 things seem to work, I'd
> >> remove the two non-127 nameservers from that list.
> >>
> > Removed the two nameservers. Still can't access mail. Getting
> > connection to storage server failed on the roundcube login page.
> >>
> 
> That you can now successfully get to "localhost" is good progress.
> Seems you want to stay away from ipv6 networking issues unless/until
> you resolve whatever that issue is.
> 
> Roundcube is, potentially, a totally separate issue. I don't use it,
> so can only suggest minimal debugging ideas.
> 
> What is the hostname that you use to get to your roundcube instance?
> Can you resolve that:
> 
>dig  a
> 
> If you get an answer, is the ipnumber correct?
> 

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mail.palmettodomains.com.  IN  A

;; ANSWER SECTION:
mail.palmettodomains.com. 86400 IN  A   192.169.1.110

;; AUTHORITY SECTION:
palmettodomains.com.86400   IN  NS  dns1.palmettodomains.com.

;; ADDITIONAL SECTION:
dns1.palmettodomains.com. 86400 IN  A   192.168.1.110
dns1.palmettodomains.com. 86400 IN  :::110

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Aug 27 09:01:48 EDT 2018
;; MSG SIZE  rcvd: 132

> Note, if the hostname for your roundcube instance is one of the ipv6
> entries in your /etc/hosts file, I'd remove that - and either put in
> an ipv4 entry or put an entry for it in your dns.
> 

Thanks again! I still think it's a mail issue. I can't get mail using
usermin either. 

Think I'm going to remove the TLS stuff from postfix main.cf that I added
yesterday and retry.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[Richard]

> Date: Monday, August 27, 2018 07:42:48 -0400
> From: TE Dukes 
> 
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> Richard Sent: Monday, August 27, 2018 7:29 AM
>
>> 
>> Since the localhost4 approach worked, commend out the ipv6
>> localhost entries in your /etc/hosts file, then try:
>> 
> IP6 is commented out
> 
>> dig @localhost localhost a
> 
> That works
>> 
>> again. If that works try:
>> 
>> telnet localhost 143
> 
> This also works
>> 
>> once again. If those work, it would seem that your ipv6 is messed
>> up and your system is trying it first and not falling back to ipv4.
>> 
>> Regarding your nameserver list in /etc/resolv.conf. If you have a
>> working 127.0.0.1 nameserver you generally don't include external
>> nameservers in that list. So, if non-ipv6 things seem to work, I'd
>> remove the two non-127 nameservers from that list.
>> 
> Removed the two nameservers. Still can't access mail. Getting
> connection to storage server failed on the roundcube login page.
>> 

That you can now successfully get to "localhost" is good progress.
Seems you want to stay away from ipv6 networking issues unless/until
you resolve whatever that issue is.

Roundcube is, potentially, a totally separate issue. I don't use it,
so can only suggest minimal debugging ideas.

What is the hostname that you use to get to your roundcube instance?
Can you resolve that:

   dig  a

If you get an answer, is the ipnumber correct?

Note, if the hostname for your roundcube instance is one of the ipv6
entries in your /etc/hosts file, I'd remove that - and either put in
an ipv4 entry or put an entry for it in your dns.




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Mail has quit working

[TE Dukes]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard
> Sent: Monday, August 27, 2018 7:29 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Mail has quit working
> 
> 
> 
> > Date: Sunday, August 26, 2018 22:37:55 -0400
> > From: TE Dukes 
> >
> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> Richard Sent: Sunday, August 26, 2018 10:25 PM
> >>
> >>
> >> > Date: Sunday, August 26, 2018 21:10:48 -0400
> >> > From: TE Dukes 
> >> >
> >> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> >> Richard Sent: Sunday, August 26, 2018 8:31 PM
> >> >>
> >> >> > Date: Sunday, August 26, 2018 16:25:14 -0400
> >> >> > From: TE Dukes 
> >> >> >
> >> >> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
> >> >> >> Alexander Dalloz
> >> >> >> Sent: Sunday, August 26, 2018 3:46 PM
> >> >> >>
> >> >> >> Am 26.08.2018 um 20:48 schrieb TE Dukes:
> >> >> >> >> You see a basic error message "Could not connect to
> >> >> >> >> localhost:143". So test that without using additional
> >> >> >> >> software. Foremost consult the maillog, in this case the
> >> >> >> >> log content produced by dovecot. And test connectivity on
> >> >> >> >> the lowest level.
> >> >> >> >>
> 
> >> >> >>
> >> >> >> So port 143 is listening. Are we back to the point that your
> >> >> >> DNS or NSS is broken so that even
> >> >> >
> >> >> > I think so. Everything else work, I don't get it.
> >> >> >>
> >> >> >> telnet localhost 143
> >> >> >>
> >> >> >> fails while
> >> >> >>
> >> >> >> telnet 127.0.0.1 143
> >> >> >>
> >> >> >> is successful?
> >> >> >>
> >> >> >
> >> >> > Yes, that is correct localhost fails but 127.0.0.1 responds.
> >> >> >
> >> >>
> >> >> In your pastebin:
> >> >>
> >> >>    A4N3MR0ZA>
> >> >>
> >> >> you show three nameservers:
> >> >>
> >> >>   nameserver 166.102.165.13
> >> >>   nameserver 207.91.5.20
> >> >>   nameserver 127.0.0.1
> >> >>
> >> >
> >> > The first two nameservers belong to my ISP. Should I move
> >> > 127.0.0.1 to the top?
> >> >
> >> >
> >> >> I can't tell if that's what you still have in place, but note
> >> >> that your dns queries will query those DNS servers in that
> >> >> order. Based on that order, the "localhost" (127.0.0.1) server
> >> >> is the last one that will be queried. Unless explicitly queried
> >> >> (e.g., with an @ syntax) it will only be queried if
> >> >> the other two fail.
> >> >>
> >> >> Could you confirm the current order (and perhaps list) the
> >> >> nameservers in your /etc/resolv.conf file - so we are aware of
> >> >> any changes.
> >> >
> >> > They are still in that order.
> >> >
> >> >>
> >> >> I did a "localhost" query against the first two and they respond
> >> >> correctly, e.g.,
> >> >>
> >> >>   ;; QUESTION SECTION:
> >> >>   ;localhost.   IN  A
> >> >>
> >> >>   ;; ANSWER SECTION:
> >> >>   localhost.86400   IN  A   127.0.0.1
> >> >>
> >> >>   ;; Query time: 100 msec
> >> >>   ;; SERVER: 166.102.165.13#53(166.102.165.13)
> >> >>
> >> >> Somewhat related to the:
> >> >>
> >> >>   > telnet localhost 143
> >> >>   >
> >> >>   > fails [while it works when you try 127.0.0.1]
> >> >>
> >> >
> >> > Not sure what I have done, but telnet localhost 143 now works but
> >> > telnet 127.0.0.1 143 fails.
> >> >
> >> >
> 
> >> >>
> >> > 127.0.0.1localhost localhost.localdomain localhost4
> >> > localhost4.localdomain4
> >> ># 127.0.0.1 localhost.localdomain localhost
> >> > 192.168.1.110ts130.palmettodomains.com   ts130
> >> > 192.168.1.110 mail.palmettodomains.com mail
> >> >
> >> > ::1 localhost localhost.localdomain localhost6
> >> > localhost6.localdomain6
> >> ># ::1   localhost6.localdomain6 localhost6
> >> > 192.168.1.102edukes1.palmettodomains.com edukes1
> >> > 192.168.1.105hp8200.palmettodomains.com hp8200
> >> > ::1  localhost localhost.localdomain localhost6
> >> > localhost6.localdomain6
> >> >
> >> > -rw-r--r--1 root root509 Aug 26 14:02 hosts
> >>
> >> Since your:
> >>
> >>dig @localhost localhost
> >>
> >> failed, try:
> >>
> >>dig @127.0.0.1 localhost a
> >>
> >> (in this context, i like the longer output as it reveals more).
> >
> > From dig @127.0.0.1 localhost a
> >
> >
> > ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @127.0.0.1 localhost a
> > ; (1 server found)
> > ;; global options: +cmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36452
> > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
> > ADDITIONAL: 2
> >
> > ;; OPT PSEUDOSECTION:
> > ; EDNS: version: 0, flags:; udp: 4096
> > ;; QUESTION SECTION:
> > ;localhost. IN  A
> >
> > ;; ANSWER SECTION:
> > localhost.  86400   IN  A   127.0.0.1
> >
> > ;; AUTHORITY SECTION:
> > localhost.  86400   IN  NS  localhost.
> >
> > ;; ADDITIONAL SECTION:
> > localhost.  86400  

Re: [CentOS] Mail has quit working

[Richard]

> Date: Sunday, August 26, 2018 22:37:55 -0400
> From: TE Dukes 
> 
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> Richard Sent: Sunday, August 26, 2018 10:25 PM
>> 
>> 
>> > Date: Sunday, August 26, 2018 21:10:48 -0400
>> > From: TE Dukes 
>> > 
>> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> >> Richard Sent: Sunday, August 26, 2018 8:31 PM
>> >> 
>> >> > Date: Sunday, August 26, 2018 16:25:14 -0400
>> >> > From: TE Dukes 
>> >> > 
>> >> >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
>> >> >> Alexander Dalloz
>> >> >> Sent: Sunday, August 26, 2018 3:46 PM
>> >> >> 
>> >> >> Am 26.08.2018 um 20:48 schrieb TE Dukes:
>> >> >> >> You see a basic error message "Could not connect to
>> >> >> >> localhost:143". So test that without using additional
>> >> >> >> software. Foremost consult the maillog, in this case the
>> >> >> >> log content produced by dovecot. And test connectivity on
>> >> >> >> the lowest level.
>> >> >> >> 

>> >> >> 
>> >> >> So port 143 is listening. Are we back to the point that your
>> >> >> DNS or NSS is broken so that even
>> >> > 
>> >> > I think so. Everything else work, I don't get it.
>> >> >> 
>> >> >> telnet localhost 143
>> >> >> 
>> >> >> fails while
>> >> >> 
>> >> >> telnet 127.0.0.1 143
>> >> >> 
>> >> >> is successful?
>> >> >> 
>> >> > 
>> >> > Yes, that is correct localhost fails but 127.0.0.1 responds.
>> >> > 
>> >> 
>> >> In your pastebin:
>> >> 
>> >>   
>> >> 
>> >> you show three nameservers:
>> >> 
>> >>   nameserver 166.102.165.13
>> >>   nameserver 207.91.5.20
>> >>   nameserver 127.0.0.1
>> >> 
>> > 
>> > The first two nameservers belong to my ISP. Should I move
>> > 127.0.0.1 to the top?
>> > 
>> > 
>> >> I can't tell if that's what you still have in place, but note
>> >> that your dns queries will query those DNS servers in that
>> >> order. Based on that order, the "localhost" (127.0.0.1) server
>> >> is the last one that will be queried. Unless explicitly queried
>> >> (e.g., with an @ syntax) it will only be queried if
>> >> the other two fail.
>> >> 
>> >> Could you confirm the current order (and perhaps list) the
>> >> nameservers in your /etc/resolv.conf file - so we are aware of
>> >> any changes.
>> > 
>> > They are still in that order.
>> > 
>> >> 
>> >> I did a "localhost" query against the first two and they respond
>> >> correctly, e.g.,
>> >> 
>> >>   ;; QUESTION SECTION:
>> >>   ;localhost. IN  A
>> >> 
>> >>   ;; ANSWER SECTION:
>> >>   localhost.  86400   IN  A   127.0.0.1
>> >> 
>> >>   ;; Query time: 100 msec
>> >>   ;; SERVER: 166.102.165.13#53(166.102.165.13)
>> >> 
>> >> Somewhat related to the:
>> >> 
>> >>   > telnet localhost 143
>> >>   > 
>> >>   > fails [while it works when you try 127.0.0.1]
>> >> 
>> > 
>> > Not sure what I have done, but telnet localhost 143 now works but
>> > telnet 127.0.0.1 143 fails.
>> > 
>> > 

>> >> 
>> > 127.0.0.1  localhost localhost.localdomain localhost4
>> > localhost4.localdomain4
>> ># 127.0.0.1 localhost.localdomain localhost
>> > 192.168.1.110  ts130.palmettodomains.com   ts130
>> > 192.168.1.110 mail.palmettodomains.com mail
>> > 
>> > ::1 localhost localhost.localdomain localhost6
>> > localhost6.localdomain6
>> ># ::1   localhost6.localdomain6 localhost6
>> > 192.168.1.102  edukes1.palmettodomains.com edukes1
>> > 192.168.1.105  hp8200.palmettodomains.com hp8200
>> > ::1localhost localhost.localdomain localhost6
>> > localhost6.localdomain6
>> > 
>> > -rw-r--r--1 root root509 Aug 26 14:02 hosts
>> 
>> Since your:
>> 
>>dig @localhost localhost
>> 
>> failed, try:
>> 
>>dig @127.0.0.1 localhost a
>> 
>> (in this context, i like the longer output as it reveals more).
> 
> From dig @127.0.0.1 localhost a
> 
> 
> ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @127.0.0.1 localhost a
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36452
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
> ADDITIONAL: 2
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;localhost.   IN  A
> 
> ;; ANSWER SECTION:
> localhost.86400   IN  A   127.0.0.1
> 
> ;; AUTHORITY SECTION:
> localhost.86400   IN  NS  localhost.
> 
> ;; ADDITIONAL SECTION:
> localhost.86400   IN  ::1
> 
> ;; Query time: 0 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Sun Aug 26 22:29:21 EDT 2018
> ;; MSG SIZE  rcvd: 96
> 
>> 
>> If that fails, then there is, at minimum, a problem with your local
>> dns server. If that works, try:
>> 
>>dig @localhost4 localhost a
> 
> From dig @localhost4 localhost a
> 
> ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> @localhost4 localhost a
> ; (1 server found)
> ;; global options: +cmd