thr3ads.net - CentOS - [CentOS] Mail has quit working [Aug 2018]

If this information is useful, please help other people find it:
Share via:

TE Dukes

2018-Jul-25 00:10 UTC

[CentOS] Mail has quit working

> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of mark
> Sent: Tuesday, July 24, 2018 5:21 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] Mail has quit working
> 
> TE Dukes wrote:
> >> -----Original Message-----
> >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of
> Alexander
> >> Dalloz
> >> Sent: Tuesday, July 24, 2018 4:19 PM
> >> To: centos at centos.org
> >> Subject: Re: [CentOS] Mail has quit working
> >>
> >>
> >> Am 24.07.2018 um 21:07 schrieb TE Dukes:
> >>
> >>> Output from tail:
> >>>
> >>>
> >>>
> >>>
> >>> Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546:
from=<
> >>> <mailto:root at ts130.palmettodomains.com>
> >>>
> >> root at ts130.palmettodomains.com>,
> >>> size=949, nrcpt=1 (queue active) Jul 24 10:36:29 ts130
> >>> postfix/smtp[19763]: connect to
> >>> <http://paalmettodomains.com>
> >>>
> >> paalmettodomains.com[198.105.254.65]:25:
> >>
> >>> Connection timed out
> >>> Jul 24 10:36:59 ts130 postfix/smtp[19763]: connect to
> >>> <http://paalmettodomains.com>
> >>>
> >> paalmettodomains.com[104.239.198.84]:25:
> >>
> >>> Connection timed out
> >>>
> >>
> >> That looks totally broken: <http://paalmettodomains.com>
> >> Where does that come from? An HTTP adddress has no valid function
in
> >> SMTP communication.
> >> Even the domain seems to be a typo.
> >>
> >
> > It's a typo.
> >
> >
> >>
> >>> Jul 24 10:36:59 ts130 postfix/smtp[19763]: C33128410546:
to=<
> >>> <mailto:tdukes at paalmettodomains.com>
> >>>
> >> tdukes at paalmettodomains.com>,
> >>> relay=none, delay=13075, delays=13015/0.02/60/0, dsn=4.4.1,
> >> status=deferred
> >>> (connect to<http://paalmettodomains.com>
> >>> paalmettodomains.com[104.239.198.84]:25: Connection timed out)
> >>> Jul 24 10:45:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 10:55:02 ts130 clamd[3226]: SelfCheck: Database status
OK.
> >>> Jul 24 11:04:19 ts130 postfix/pickup[19912]: 55271840D734:
uid=0
> >>>
> >> from=<root>
> >>> Jul 24 11:04:19 ts130 postfix/cleanup[21840]: 55271840D734:
> >>> message-id=<
> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
> >>> 20180724150419.55271840D734 at ts130.palmettodomains.com>
> >>> Jul 24 11:04:19 ts130 postfix/qmgr[8283]: 55271840D734:
from=<
> >>> <mailto:root at ts130.palmettodomains.com>
> >>>
> >> root at ts130.palmettodomains.com>,
> >>> size=466, nrcpt=1 (queue active)
> >>
> >> mailto:root at ts130.palmettodomains.com  <- What is the
purpose to send
> >> yourself a mail locally? Did you even specify a valid, fully
qualified
> >> recipient address?
> >
> > A previous person instructed to do so.
> >
> >
> >>
> >>> Jul 24 11:04:20 ts130 postfix/smtpd[21846]: connect from
> >>> localhost[127.0.0.1] Jul 24 11:04:20 ts130
postfix/smtpd[21846]:
> >>> 49161841ED92:
> >>> client=localhost[127.0.0.1] Jul 24 11:04:20 ts130
> >>> postfix/cleanup[21840]: 49161841ED92: message-id=<
> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
> >>> 20180724150419.55271840D734 at ts130.palmettodomains.com>
> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92:
from=<
> >>> <mailto:root at ts130.palmettodomains.com>
> >>>
> >> root at ts130.palmettodomains.com>,
> >>> size=951, nrcpt=1 (queue active) Jul 24 11:04:20 ts130
> >>> postfix/smtpd[21846]: disconnect from
> >>> localhost[127.0.0.1] Jul 24 11:04:20 ts130 amavis[423]:
(00423-03)
> >>> Passed CLEAN
> >>>
> >> {RelayedInbound},
> >>
> >>> [127.0.0.1] <<mailto:root at
ts130.palmettodomains.com>
> >>> root at ts130.palmettodomains.com> -> <
> >> <mailto:tdukes at palmettodomains.com>
> >>
> >>> tdukes at palmettodomains.com>, Message-ID: <
> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
> >>> 20180724150419.55271840D734 at ts130.palmettodomains.com>,
mail_id:
> >>> eYD2cL7fZ7rY, Hits: -0.001, size: 466, queued_as:
49161841ED92, 941 ms
> >>>  Jul 24 11:04:20 ts130 postfix/smtp[21842]: 55271840D734:
to=<
> >>> <mailto:tdukes at palmettodomains.com>
> >>>
> >> tdukes at palmettodomains.com>,
> >>> relay=127.0.0.1[127.0.0.1]:10024, delay=1,
delays=0.07/0.01/0/0.94,
> >>> dsn=2.0.0, status=sent (250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025):
> >>> 250
> >>> 2.0.0 Ok: queued as 49161841ED92)
> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 55271840D734:
removed
> >>> Jul 24 11:04:20 ts130 dovecot: lda(tdukes): msgid=<
> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
> >>> 20180724150419.55271840D734 at ts130.palmettodomains.com>:
saved
> mail
> >>>
> >> to INBOX
> >>> Jul 24 11:04:20 ts130 postfix/local[21847]: 49161841ED92:
to=<
> >>> <mailto:tdukes at palmettodomains.com>
> >>>
> >> tdukes at palmettodomains.com>,
> >>> relay=local, delay=0.09, delays=0.02/0.01/0/0.06, dsn=2.0.0,
> >>> status=sent (delivered to command:
/usr/libexec/dovecot/dovecot-lda -
> f
> >>> "$SENDER" -a
> >>> "$RECIPIENT")
> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92:
removed
> >>>
> >>
> >> Mail got delivered locally after passing amavis at the mailbox
> >> tdukes at palmettodomains.com.
> >>
> >> Alexander
> >>
> >
> > I am unable to read my system's mail. Cannot read it from
roundcube or
> > usermin. Roundcube times out on login attemps. In usermin there is no
> mail
> >  in the mailbox. There is no mail in /Maildir.
> >
> > This just started this past Saturday morning. Everything was fine up
to
> > then.
> >
> 1. Have you checked /var/log/yum.log?
> 2. Is everything correct in /cron.*?
> 3. Have you considered running yum reinstall crony?
> 
>         mark
Thanks!

Everything seems to be OK.

I did find where the mail is going. I found it in /Maildir/new/ 

Postfix is set to home_mailbox = Maildir/ Changing it doesn't help.

Still can't login to roundcube.

James (CentOS ML)

2018-Jul-25 02:53 UTC

head link

[CentOS] Mail has quit working

On 2018-07-24 20:10, TE Dukes wrote:>> -----Original Message-----
>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of mark
>> Sent: Tuesday, July 24, 2018 5:21 PM
>> To: CentOS mailing list
>> Subject: Re: [CentOS] Mail has quit working
>> 
>> TE Dukes wrote:
>> >> -----Original Message-----
>> >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf
Of
>> Alexander
>> >> Dalloz
>> >> Sent: Tuesday, July 24, 2018 4:19 PM
>> >> To: centos at centos.org
>> >> Subject: Re: [CentOS] Mail has quit working
>> >>
>> >>
>> >> Am 24.07.2018 um 21:07 schrieb TE Dukes:
>> >>
>> >>> Output from tail:
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546:
from=<
>> >>> <mailto:root at ts130.palmettodomains.com>
>> >>>
>> >> root at ts130.palmettodomains.com>,
>> >>> size=949, nrcpt=1 (queue active) Jul 24 10:36:29 ts130
>> >>> postfix/smtp[19763]: connect to
>> >>> <http://paalmettodomains.com>
>> >>>
>> >> paalmettodomains.com[198.105.254.65]:25:
>> >>
>> >>> Connection timed out
>> >>> Jul 24 10:36:59 ts130 postfix/smtp[19763]: connect to
>> >>> <http://paalmettodomains.com>
>> >>>
>> >> paalmettodomains.com[104.239.198.84]:25:
>> >>
>> >>> Connection timed out
>> >>>
>> >>
>> >> That looks totally broken: <http://paalmettodomains.com>
>> >> Where does that come from? An HTTP adddress has no valid
function in
>> >> SMTP communication.
>> >> Even the domain seems to be a typo.
>> >>
>> >
>> > It's a typo.
>> >
>> >
>> >>
>> >>> Jul 24 10:36:59 ts130 postfix/smtp[19763]: C33128410546:
to=<
>> >>> <mailto:tdukes at paalmettodomains.com>
>> >>>
>> >> tdukes at paalmettodomains.com>,
>> >>> relay=none, delay=13075, delays=13015/0.02/60/0,
dsn=4.4.1,
>> >> status=deferred
>> >>> (connect to<http://paalmettodomains.com>
>> >>> paalmettodomains.com[104.239.198.84]:25: Connection timed
out)
>> >>> Jul 24 10:45:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 10:55:02 ts130 clamd[3226]: SelfCheck: Database
status OK.
>> >>> Jul 24 11:04:19 ts130 postfix/pickup[19912]: 55271840D734:
uid=0
>> >>>
>> >> from=<root>
>> >>> Jul 24 11:04:19 ts130 postfix/cleanup[21840]:
55271840D734:
>> >>> message-id=<
>> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> 20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> Jul 24 11:04:19 ts130 postfix/qmgr[8283]: 55271840D734:
from=<
>> >>> <mailto:root at ts130.palmettodomains.com>
>> >>>
>> >> root at ts130.palmettodomains.com>,
>> >>> size=466, nrcpt=1 (queue active)
>> >>
>> >> mailto:root at ts130.palmettodomains.com  <- What is the
purpose to send
>> >> yourself a mail locally? Did you even specify a valid, fully
qualified
>> >> recipient address?
>> >
>> > A previous person instructed to do so.
>> >
>> >
>> >>
>> >>> Jul 24 11:04:20 ts130 postfix/smtpd[21846]: connect from
>> >>> localhost[127.0.0.1] Jul 24 11:04:20 ts130
postfix/smtpd[21846]:
>> >>> 49161841ED92:
>> >>> client=localhost[127.0.0.1] Jul 24 11:04:20 ts130
>> >>> postfix/cleanup[21840]: 49161841ED92: message-id=<
>> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> 20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92:
from=<
>> >>> <mailto:root at ts130.palmettodomains.com>
>> >>>
>> >> root at ts130.palmettodomains.com>,
>> >>> size=951, nrcpt=1 (queue active) Jul 24 11:04:20 ts130
>> >>> postfix/smtpd[21846]: disconnect from
>> >>> localhost[127.0.0.1] Jul 24 11:04:20 ts130 amavis[423]:
(00423-03)
>> >>> Passed CLEAN
>> >>>
>> >> {RelayedInbound},
>> >>
>> >>> [127.0.0.1] <<mailto:root at
ts130.palmettodomains.com>
>> >>> root at ts130.palmettodomains.com> -> <
>> >> <mailto:tdukes at palmettodomains.com>
>> >>
>> >>> tdukes at palmettodomains.com>, Message-ID: <
>> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> 20180724150419.55271840D734 at
ts130.palmettodomains.com>, mail_id:
>> >>> eYD2cL7fZ7rY, Hits: -0.001, size: 466, queued_as:
49161841ED92, 941 ms
>> >>>  Jul 24 11:04:20 ts130 postfix/smtp[21842]: 55271840D734:
to=<
>> >>> <mailto:tdukes at palmettodomains.com>
>> >>>
>> >> tdukes at palmettodomains.com>,
>> >>> relay=127.0.0.1[127.0.0.1]:10024, delay=1,
delays=0.07/0.01/0/0.94,
>> >>> dsn=2.0.0, status=sent (250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025):
>> >>> 250
>> >>> 2.0.0 Ok: queued as 49161841ED92)
>> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 55271840D734:
removed
>> >>> Jul 24 11:04:20 ts130 dovecot: lda(tdukes): msgid=<
>> >>> <mailto:20180724150419.55271840D734 at
ts130.palmettodomains.com>
>> >>> 20180724150419.55271840D734 at
ts130.palmettodomains.com>: saved
>> mail
>> >>>
>> >> to INBOX
>> >>> Jul 24 11:04:20 ts130 postfix/local[21847]: 49161841ED92:
to=<
>> >>> <mailto:tdukes at palmettodomains.com>
>> >>>
>> >> tdukes at palmettodomains.com>,
>> >>> relay=local, delay=0.09, delays=0.02/0.01/0/0.06,
dsn=2.0.0,
>> >>> status=sent (delivered to command:
/usr/libexec/dovecot/dovecot-lda -
>> f
>> >>> "$SENDER" -a
>> >>> "$RECIPIENT")
>> >>> Jul 24 11:04:20 ts130 postfix/qmgr[8283]: 49161841ED92:
removed
>> >>>
>> >>
>> >> Mail got delivered locally after passing amavis at the mailbox
>> >> tdukes at palmettodomains.com.
>> >>
>> >> Alexander
>> >>
>> >
>> > I am unable to read my system's mail. Cannot read it from
roundcube or
>> > usermin. Roundcube times out on login attemps. In usermin there is
no
>> mail
>> >  in the mailbox. There is no mail in /Maildir.
>> >
>> > This just started this past Saturday morning. Everything was fine
up to
>> > then.
>> >
>> 1. Have you checked /var/log/yum.log?
>> 2. Is everything correct in /cron.*?
>> 3. Have you considered running yum reinstall crony?
>> 
>>         mark
> 
> Thanks!
> 
> Everything seems to be OK.
> 
> I did find where the mail is going. I found it in /Maildir/new/
> 
> Postfix is set to home_mailbox = Maildir/ Changing it doesn't help.
> 
> Still can't login to roundcube.
> 
Postfix only handles the outgoing email.  What IMAP/POP server are you 
using?  Verify that is running, and check for errors in the logs.  
Additionally, check your Roundcube config to make sure that the settings 
didn't get clobbered as part of an upgrade (if installed using yum).

James

Peter

2018-Jul-25 04:05 UTC

head link

[CentOS] Mail has quit working

On 25/07/18 12:10, TE Dukes wrote:>>> I am unable to read my system's mail. Cannot read it from
roundcube or
>>> usermin. Roundcube times out on login attemps. In usermin there is
no
>>> mail in the mailbox. There is no mail in /Maildir.
This is new information.  It points to the issue being in dovecot or
roundcube.
> I did find where the mail is going. I found it in /Maildir/new/ 
This indicates that dovecot is working.
> Postfix is set to home_mailbox = Maildir/ Changing it doesn't help.
It won't, this setting only applies when you're using the postfix
local(8) delivery agent, but you have postfix configured to use dovecot
so this setting does not actually do anything.
> Still can't login to roundcube.
Check roundcube settings, check dovecot logs.  See my previous email for
where to get more help with dovecot.


Peter

Pete Biggs

2018-Jul-25 09:44 UTC

head link

[CentOS] Mail has quit working

> 
> I did find where the mail is going. I found it in /Maildir/new/ 
Yes, that's how Maildir mail works - delivery to a Maildir folder means
that the mail is put in Maildir/new until it is seen, when it is moved
to Maildir/cur via Maildir/tmp - it's complicated, but it's necessary
in order to maintain appropriate locks on the files when multiple
clients are accessing them.
> 
> Still can't login to roundcube.
> When you say "can't login" - what is the error?

What do the dovecot logs say? You can see where dovecot logs to by
looking in /etc/dovecot/conf.d/10-logging.conf - can you see your
roundcube install attempting to authenticate?

P.

TE Dukes

2018-Jul-25 11:05 UTC

head link

[CentOS] Mail has quit working

> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Pete Biggs
> Sent: Wednesday, July 25, 2018 5:45 AM
> To: centos at centos.org
> Subject: Re: [CentOS] Mail has quit working
> 
> 
> >
> > I did find where the mail is going. I found it in /Maildir/new/
> 
> Yes, that's how Maildir mail works - delivery to a Maildir folder means
> that the mail is put in Maildir/new until it is seen, when it is moved
> to Maildir/cur via Maildir/tmp - it's complicated, but it's
necessary
> in order to maintain appropriate locks on the files when multiple
> clients are accessing them.
> 
> >
> > Still can't login to roundcube.
> >
> When you say "can't login" - what is the error?
> 
> What do the dovecot logs say? You can see where dovecot logs to by
> looking in /etc/dovecot/conf.d/10-logging.conf - can you see your
> roundcube install attempting to authenticate?
> 
> P.
Geeeez!! Its working again. All I did was restart the system.

I stopped and restarted postfix, dovecot, mariadb several times over the
past couple days. Pretty sure I did a system reboot a time or two.

Decided to do one a few minutes ago and now its working. Hate I never found
the problem that caused this issue!

Thanks for all the help!!

TE Dukes

2018-Aug-20 01:21 UTC

head link

[CentOS] Mail has quit working

Another kernel update and things are broken again!

YEARS with no problems. About tired of messing with this!

Gordon Messmer

2018-Aug-23 20:55 UTC

head link

[CentOS] Mail has quit working

On 08/19/2018 06:21 PM, TE Dukes wrote:> Another kernel update and things are broken again!
> YEARS with no problems. About tired of messing with this!
Earlier in this thread, you indicated that you saw "warning hostname 
localhost does not resolve to address 127.0.0.1" in /var/log/maillog, 
and some other logs indicated that postfix was timing out connecting to 
its locally hosted domains.? Both of those suggest that you have DNS or 
network related problems, and not something resulting from package updates.

You might consider posting /etc/resolv.conf, /etc/hosts, 
/etc/sysconfig/network-scripts/ifcfg-<your network interface>, and 
/etc/postfix/main.cfg on https://paste.fedoraproject.org/ for review.? 
It would also be useful to see the output of "ip addr show", "ip
route
show", and "ip -6 route show".? If the system starts working
suddenly,
as it did earlier, compare the output of those commands when the system 
is working to the output when it is not.

Possibly Parallel Threads

Search for more possibly parallel threads

CentOS - Aug 2018 - Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

[CentOS] Mail has quit working

Possibly Parallel Threads