CentOS - Jan 2017 - firewalld

> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Gordon
> Messmer
> Sent: Sunday, January 29, 2017 6:56 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] firewalld
> 
> On 01/29/2017 01:54 PM, TE Dukes wrote:
> > I telnet to localhost 143 or 993  and I can connect, telneting to 25
> > or 465, connection refused.
> 
> 
> As I mentioned before: firewalld allows all traffic to localhost.  If
you're
> getting connection refused, then those services aren't running.
> 
> As for dealing with login denied errors, you should be looking at the IMAP
> server's logs, not the HTTP server's.
Here's the excerpts from maillog:

Jan 29 13:52:28 ts130 MailScanner[3941]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:28 ts130 logger[3944]: MailScanner started
Jan 29 13:52:28 ts130 MailScanner[3941]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:28 ts130 MailScanner[3941]: Reading configuration file
/etc/MailScanner/conf.d/README
Jan 29 13:52:28 ts130 MailScanner[3941]: Read 1501 hostnames from the
phishing whitelist
Jan 29 13:52:28 ts130 MailScanner[3941]: Read 12749 hostnames from the
phishing blacklists
Jan 29 13:52:28 ts130 MailScanner[3941]: Using SpamAssassin results cache
Jan 29 13:52:28 ts130 MailScanner[3941]: Connected to SpamAssassin cache
database
Jan 29 13:52:28 ts130 MailScanner[3941]: Enabling SpamAssassin
auto-whitelist functionality...
Jan 29 13:52:33 ts130 MailScanner[4235]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:33 ts130 MailScanner[4235]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:33 ts130 MailScanner[4235]: Reading configuration file
/etc/MailScanner/conf.d/README
Jan 29 13:52:33 ts130 MailScanner[4235]: Read 1501 hostnames from the
phishing whitelist
Jan 29 13:52:33 ts130 MailScanner[4235]: Read 12749 hostnames from the
phishing blacklists
Jan 29 13:52:33 ts130 MailScanner[4235]: Using SpamAssassin results cache
Jan 29 13:52:33 ts130 MailScanner[4235]: Connected to SpamAssassin cache
database
Jan 29 13:52:33 ts130 MailScanner[4235]: Enabling SpamAssassin
auto-whitelist functionality...
Jan 29 13:52:38 ts130 MailScanner[4363]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:38 ts130 MailScanner[4363]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:38 ts130 MailScanner[4363]: Reading configuration file
/etc/MailScanner/conf.d/README
Jan 29 13:52:38 ts130 MailScanner[4363]: Read 1501 hostnames from the
phishing whitelist
Jan 29 13:52:38 ts130 MailScanner[4363]: Read 12749 hostnames from the
phishing blacklists
Jan 29 13:52:38 ts130 MailScanner[4363]: Using SpamAssassin results cache
Jan 29 13:52:38 ts130 MailScanner[4363]: Connected to SpamAssassin cache
database
Jan 29 13:52:38 ts130 MailScanner[4363]: Enabling SpamAssassin
auto-whitelist functionality...
Jan 29 13:52:43 ts130 MailScanner[4459]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:43 ts130 MailScanner[4459]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:43 ts130 MailScanner[4459]: Reading configuration file
/etc/MailScanner/conf.d/README
Jan 29 13:52:43 ts130 MailScanner[4459]: Read 1501 hostnames from the
phishing whitelist
Jan 29 13:52:43 ts130 MailScanner[4459]: Read 12749 hostnames from the
phishing blacklists
Jan 29 13:52:43 ts130 MailScanner[4459]: Using SpamAssassin results cache
Jan 29 13:52:43 ts130 MailScanner[4459]: Connected to SpamAssassin cache
database
Jan 29 13:52:43 ts130 MailScanner[4459]: Enabling SpamAssassin
auto-whitelist functionality...
Jan 29 13:52:48 ts130 MailScanner[4528]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:48 ts130 MailScanner[4528]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:48 ts130 MailScanner[4528]: Reading configuration file
/etc/MailScanner/conf.d/README
Jan 29 13:52:48 ts130 MailScanner[4528]: Read 1501 hostnames from the
phishing whitelist
Jan 29 13:52:48 ts130 MailScanner[4528]: Read 12749 hostnames from the
phishing blacklists
Jan 29 13:52:48 ts130 MailScanner[4528]: Using SpamAssassin results cache
Jan 29 13:52:48 ts130 MailScanner[4528]: Connected to SpamAssassin cache
database
Jan 29 13:52:48 ts130 MailScanner[4528]: Enabling SpamAssassin
auto-whitelist functionality...
Jan 29 13:53:03 ts130 MailScanner[4235]: Auto: Found virus scanners:
clamavmodule
Jan 29 13:53:03 ts130 MailScanner[3941]: Auto: Found virus scanners:
clamavmodule
Jan 29 13:53:05 ts130 MailScanner[4363]: Auto: Found virus scanners:
clamavmodule
Jan 29 13:53:05 ts130 MailScanner[4459]: Auto: Found virus scanners:
clamavmodule
Jan 29 13:53:11 ts130 MailScanner[4528]: Auto: Found virus scanners:
clamavmodule
Jan 29 13:53:17 ts130 MailScanner[4459]: Connected to Processing Attempts
Database
Jan 29 13:53:17 ts130 MailScanner[4459]: Found 0 messages in the Processing
Attempts Database
Jan 29 13:53:17 ts130 MailScanner[4459]: Using locktype = flock
Jan 29 13:53:17 ts130 MailScanner[4235]: Connected to Processing Attempts
Database
Jan 29 13:53:17 ts130 MailScanner[4235]: Found 0 messages in the Processing
Attempts Database
Jan 29 13:53:17 ts130 MailScanner[4235]: Using locktype = flock
Jan 29 13:53:17 ts130 MailScanner[4363]: Connected to Processing Attempts
Database
Jan 29 13:53:17 ts130 MailScanner[4363]: Found 0 messages in the Processing
Attempts Database
Jan 29 13:53:17 ts130 MailScanner[4363]: Using locktype = flock
Jan 29 13:53:17 ts130 MailScanner[3941]: Connected to Processing Attempts
Database
Jan 29 13:53:17 ts130 MailScanner[3941]: Found 0 messages in the Processing
Attempts Database
Jan 29 13:53:17 ts130 MailScanner[3941]: Using locktype = flock
Jan 29 13:53:21 ts130 MailScanner[4528]: Connected to Processing Attempts
Database
Jan 29 13:53:21 ts130 MailScanner[4528]: Found 0 messages in the Processing
Attempts Database
Jan 29 13:53:21 ts130 MailScanner[4528]: Using locktype = flock

Last login attempt from roundcube

Jan 29 16:38:08 ts130 dovecot: imap-login: Login: user=<tdukes>,
method=PLAIN, rip=::1, lip=::1, mpid=2076, secured,
session=<dVTVg0JHkAAAAAAAAAAAAAAAAAAAAAAB>
Jan 29 16:38:08 ts130 dovecot: imap(tdukes): Error: user tdukes:
Initialization failed: Namespace '': Mail storage autodetection failed
with
home=/home/tdukes
Jan 29 16:38:08 ts130 dovecot: imap(tdukes): Error: Invalid user settings.
Refer to server log for more information.
Jan 29 16:44:47 ts130 dovecot: imap-login: Login: user=<tdukes>,
method=PLAIN, rip=::1, lip=::1, mpid=2282, secured,
session=<OEeVm0JHkgAAAAAAAAAAAAAAAAAAAAAB>
Jan 29 16:44:47 ts130 dovecot: imap(tdukes): Error: user tdukes:
Initialization failed: Namespace '': Mail storage autodetection failed
with
home=/home/tdukes
Jan 29 16:44:47 ts130 dovecot: imap(tdukes): Error: Invalid user settings.
Refer to server log for more information.
Jan 29 16:44:56 ts130 dovecot: imap-login: Login: user=<tdukes>,
method=PLAIN, rip=::1, lip=::1, mpid=2290, secured,
session=<FyIlnEJHlAAAAAAAAAAAAAAAAAAAAAAB>
Jan 29 16:44:56 ts130 dovecot: imap(tdukes): Error: user tdukes:
Initialization failed: Namespace '': Mail storage autodetection failed
with
home=/home/tdukes
Jan 29 16:44:56 ts130 dovecot: imap(tdukes): Error: Invalid user settings.
Refer to server log for more information.
Jan 29 16:45:05 ts130 dovecot: imap-login: Login: user=<tdukes>,
method=PLAIN, rip=::1, lip=::1, mpid=2301, secured,
session=<yISwnEJHlgAAAAAAAAAAAAAAAAAAAAAB>
Jan 29 16:45:05 ts130 dovecot: imap(tdukes): Error: user tdukes:
Initialization failed: Namespace '': Mail storage autodetection failed
with
home=/home/tdukes
Jan 29 16:45:05 ts130 dovecot: imap(tdukes): Error: Invalid user settings.
Refer to server log for more information.

???

I have no clue

> Last login attempt from roundcube
> 
> Jan 29 16:38:08 ts130 dovecot: imap-login: Login: user=<tdukes>,
> method=PLAIN, rip=::1, lip=::1, mpid=2076, secured,
> session=<dVTVg0JHkAAAAAAAAAAAAAAAAAAAAAAB>
> Jan 29 16:38:08 ts130 dovecot: imap(tdukes): Error: user tdukes:
> Initialization failed: Namespace '': Mail storage autodetection
failed with
> home=/home/tdukes
> Jan 29 16:38:08 ts130 dovecot: imap(tdukes): Error: Invalid user settings.
> Refer to server log for more information.
It's a dovecot configuration error. The login has clearly worked, so
stop fussing with the firewall.

You need to look in /etc/dovecot/conf.d/10-mail.conf and set
'mail_location' to where the user's email is stored. If you are
using
Maildir then it will probably be 

  mail_location =??maildir:~/Maildir

if mbox, then probably

  mail_location = mbox:~/mail:INBOX=/var/mail/%u

but adjust the paths to where things are actually stored.

You will, obviously, have to set your MTA to deliver the mail to the
correct location and in the correct format as well.

P.

> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Pete Biggs
> Sent: Sunday, January 29, 2017 8:27 PM
> To: centos at centos.org
> Subject: Re: [CentOS] firewalld
> 
> 
> > Last login attempt from roundcube
> >
> > Jan 29 16:38:08 ts130 dovecot: imap-login: Login: user=<tdukes>,
> > method=PLAIN, rip=::1, lip=::1, mpid=2076, secured,
> > session=<dVTVg0JHkAAAAAAAAAAAAAAAAAAAAAAB>
> > Jan 29 16:38:08 ts130 dovecot: imap(tdukes): Error: user tdukes:
> > Initialization failed: Namespace '': Mail storage
autodetection failed
> > with home=/home/tdukes Jan 29 16:38:08 ts130 dovecot: imap(tdukes):
> > Error: Invalid user settings.
> > Refer to server log for more information.
> 
> It's a dovecot configuration error. The login has clearly worked, so
stop
> fussing with the firewall.
> 
> You need to look in /etc/dovecot/conf.d/10-mail.conf and set
'mail_location'
> to where the user's email is stored. If you are using Maildir then it
will
> probably be
> 
>   mail_location =  maildir:~/Maildir
> 
> if mbox, then probably
> 
>   mail_location = mbox:~/mail:INBOX=/var/mail/%u
> 
> but adjust the paths to where things are actually stored.
> 
> You will, obviously, have to set your MTA to deliver the mail to the
correct
> location and in the correct format as well.
> 
Thank you!!!!!!

Its working now! Never had to do that before, everything always worked out of
the box.

# Location for users' mailboxes. The default is empty, which means that
Dovecot
# tries to find the mailboxes automatically. This won't work if the user
# doesn't yet have any mail, so you should explicitly tell Dovecot the full
# location.
#
# If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u)
# isn't enough. You'll also need to tell Dovecot where the other
mailboxes are
# kept. This is called the "root mail directory", and it must be the
first
# path given in the mail_location setting.
#
# There are a few special variables you can use, eg.:
#
#   %u - username
#   %n - user part in user at domain, same as %u if there's no domain
#   %d - domain part in user at domain, empty if there's no domain
#   %h - home directory
#
# See doc/wiki/Variables.txt for full list. Some examples:
#
#   mail_location = maildir:~/Maildir
#   mail_location = mbox:~/mail:INBOX=/var/mail/%u
#   mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n
#
# <doc/wiki/MailLocation.txt>
#
mail_location = maildir:~/Maildir  <<<<<------ this!!

Really appreciate the help!!