Re: [qmailtoaster] error message spamd: still running as root

[Eric Broch]

The --create-prefs option is for spamassassin mysql user preferences. 
You might just tack on the '-u clamscan' option


On 4/8/2024 1:02 PM, Peter Peterse wrote:

Hi Eric,

My /etc/sysconfig/spamassassin looks like:

# Options to spamd
SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"


I will try yours.

thanks,
Peter

On 4-4-2024 23:56, Eric Broch wrote:

# cat  /etc/sysconfig/spamassassin
# Options to spamd
#SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"

SPAMDOPTIONS="--create-prefs -m10 -q -x -u clamscan"

What's in your /etc/sysconfig/spamassassin file?

On 4/4/2024 2:21 PM, Peter Peterse wrote:
still running as root: user not specified with -u, not found, or set 
to root, falling back to nobody


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error message spamd: still running as root

[Peter Peterse]

Hi Eric,

My /etc/sysconfig/spamassassin looks like:

# Options to spamd
SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"


I will try yours.

thanks,
Peter

On 4-4-2024 23:56, Eric Broch wrote:

# cat  /etc/sysconfig/spamassassin
# Options to spamd
#SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"

SPAMDOPTIONS="--create-prefs -m10 -q -x -u clamscan"

What's in your /etc/sysconfig/spamassassin file?

On 4/4/2024 2:21 PM, Peter Peterse wrote:
still running as root: user not specified with -u, not found, or set 
to root, falling back to nobody


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error message spamd: still running as root

[Eric Broch]

# cat  /etc/sysconfig/spamassassin
# Options to spamd
#SPAMDOPTIONS="-c -m5 -H --razor-home-dir='/var/lib/razor/' 
--razor-log-file='sys-syslog'"

SPAMDOPTIONS="--create-prefs -m10 -q -x -u clamscan"

What's in your /etc/sysconfig/spamassassin file?

On 4/4/2024 2:21 PM, Peter Peterse wrote:
still running as root: user not specified with -u, not found, or set 
to root, falling back to nobody


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error suggestions qq soft.

[Remo Mattei]

Hello Eric, that’s the the issue, I upgraded qmail and it did it again good 
thing I did a snapshot revert :) 

Remo something to look for. I do have the right permissions, I checked before 
reverting. 

> On May 30, 2021, at 1:47 PM, Eric Broch  wrote:
> 
> ls -l /etc/dspam.conf should be:
> 
> -rw-r--r-- 1 root mail 36399 May 28 11:41 /etc/dspam.conf
> 
> On 5/30/2021 2:30 PM, r...@mattei.org wrote:
>> dspam (check_dspam) reading header line: 0, check dspam.conf perms
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [qmailtoaster] error suggestions qq soft.

[Eric Broch]

ls -l /etc/dspam.conf should be:

-rw-r--r-- 1 root mail 36399 May 28 11:41 /etc/dspam.conf

On 5/30/2021 2:30 PM, r...@mattei.org wrote:

dspam (check_dspam) reading header line: 0, check dspam.conf perms


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error when trying to send on submission port

[Dieter Febel]

Hi Finn, 

Thank you, never saw your email, got it in the archive, email is up and
running again. 

submission still does not work without STARTTLS encryption, but at
least the email is flowing again.  

Thanks you, 

Dieter

-Original Message-

Date: Mon, 25 Jan 2021 08:48:22 +0200
Subject: Re: [qmailtoaster] Error when trying to send on submission
port
To: qmailtoaster-list@qmailtoaster.com
From: Dieter Febel 
Hi Eric, 

I restarted the server, now its refusing connections on port 25. So no
incoming email.

I reverted to : 
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD"
\
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SMTPD $VCHKPW /bin/true 2>&1

tcp.smtp
127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPT
LIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQUEUE="/var/
qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-
queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%
/private"



telnet x.xxx.xxx 25 Trying xxx.yyy.zzz.ccc ...telnet: Unable to
connect to remote host: Connection refused

Could you please help? I also restarted after I reverted the changes. 


Kind regards, 


Dieter





-Original Message-

Date: Sun, 24 Jan 2021 10:17:49 -0700
Subject: Re: [qmailtoaster] Error when trying to send on submission
port
To: qmailtoaster-list@qmailtoaster.com
Reply-to: qmailtoaster-list@qmailtoaster.com
From: Eric Broch 
Are there two submission daemons running?

Restart server.

On 1/24/2021 9:10 AM, qm...@mailonly.dk wrote:
> You need to have Your /var/qmail/supervise/smtp/run (port 25) as
> below
> 
> #!/bin/sh
> QMAILDUID=`id -u vpopmail`
> NOFILESGID=`id -g vpopmail`
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> SPAMDYKE="/usr/bin/spamdyke"
> SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
> SMTPD="/var/qmail/bin/qmail-smtpd"
> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> HOSTNAME=`hostname`
> VCHKPW="/home/vpopmail/bin/vchkpw"
> export SMTPAUTH="-"
> 
> exec /usr/bin/softlimit -m 12800 \
>  /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
> "$MAXSMTPD" \
>  -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
>  $SPAMDYKE --config-file $SPAMDYKE_CONF \
>  $SMTPD $VCHKPW /bin/true 2>&1
> 
> 
> 
> Then have the change  (copy the lines from Eric' mail) into the 
> /var/qmail/supervise/submission/run (port 587)
> 
> 
> and lastly here is my /var/run/supervise/smtps/run for port 465
> 
> #!/bin/sh
> QMAILDUID=`id -u vpopmail`
> NOFILESGID=`id -g vpopmail`
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> SMTPD="/var/qmail/bin/qmail-smtpd"
> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> HOSTNAME=`hostname`
> VCHKPW="/home/vpopmail/bin/vchkpw"
> export SMTPS=1
> export FORCETLS=0
> export SMTPAUTH="!+cram"
> 
> exec /usr/bin/softlimit -m 12800 \
>     /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c
> "$MAXSMTPD" \
>     -u "$QMAILDUID" -g "$NOFILESGID" 0 465 \
>     $SMTPD $VCHKPW /bin/true 2>&1
> 
> I may say all 3 run files are default settings from Erics install 
> script - only change I may recall is the softlimit that may have
> been 
> increased
> 
> My clients (mostly TB) are using ssl/tls - encrypted (name/passwd) 
> settings and are only using 465 or 587 to submit mails
> port 25 is only for server to server delivery 😏
> 
> Hope this may help
> 
> 
> Regards
> 
> Finn
> 
> PS I'm on Centos8 and Qmail for same - perfect
> 
> 
> Den 24-01-2021 kl. 07:31 skrev Dieter Febel:
> > Hi Eric,
> > 
> > I changed the file to what you recommended, but I am still getting 
> > the same error. I have authentication turned on in the email
> > client, 
> > and no encryption.
> > The reported error was "MAIL FROM command failed: Authorization 
> > required (#5.7.1)".
> > 
> > #!/bin/sh
> > QMAILDUID=`id -u vpopmail`
> > NOFILESGID=`id -g vpopmail`
> > MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> > SMTPD="/var/qmail/bin/qmail-smtpd"
> > TCP_CDB="/etc/tcpru

Re: [qmailtoaster] Error when trying to send on submission port

[Dieter Febel]

Hi Eric, 

I restarted the server, now its refusing connections on port 25. So no
incoming email.

I reverted to : 
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD"
\
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SMTPD $VCHKPW /bin/true 2>&1

tcp.smtp
127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPT
LIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQUEUE="/var/
qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-
queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%
/private"



telnet x.xxx.xxx 25 Trying xxx.yyy.zzz.ccc ...telnet: Unable to
connect to remote host: Connection refused

Could you please help? I also restarted after I reverted the changes. 


Kind regards, 


Dieter



-Original Message-

Date: Sun, 24 Jan 2021 10:17:49 -0700
Subject: Re: [qmailtoaster] Error when trying to send on submission
port
To: qmailtoaster-list@qmailtoaster.com
Reply-to: qmailtoaster-list@qmailtoaster.com
From: Eric Broch 
Are there two submission daemons running?

Restart server.

On 1/24/2021 9:10 AM, qm...@mailonly.dk wrote:
> You need to have Your /var/qmail/supervise/smtp/run (port 25) as
> below
> 
> #!/bin/sh
> QMAILDUID=`id -u vpopmail`
> NOFILESGID=`id -g vpopmail`
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> SPAMDYKE="/usr/bin/spamdyke"
> SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
> SMTPD="/var/qmail/bin/qmail-smtpd"
> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> HOSTNAME=`hostname`
> VCHKPW="/home/vpopmail/bin/vchkpw"
> export SMTPAUTH="-"
> 
> exec /usr/bin/softlimit -m 12800 \
>  /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
> "$MAXSMTPD" \
>  -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
>  $SPAMDYKE --config-file $SPAMDYKE_CONF \
>  $SMTPD $VCHKPW /bin/true 2>&1
> 
> 
> 
> Then have the change  (copy the lines from Eric' mail) into the 
> /var/qmail/supervise/submission/run (port 587)
> 
> 
> and lastly here is my /var/run/supervise/smtps/run for port 465
> 
> #!/bin/sh
> QMAILDUID=`id -u vpopmail`
> NOFILESGID=`id -g vpopmail`
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> SMTPD="/var/qmail/bin/qmail-smtpd"
> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> HOSTNAME=`hostname`
> VCHKPW="/home/vpopmail/bin/vchkpw"
> export SMTPS=1
> export FORCETLS=0
> export SMTPAUTH="!+cram"
> 
> exec /usr/bin/softlimit -m 12800 \
>     /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c
> "$MAXSMTPD" \
>     -u "$QMAILDUID" -g "$NOFILESGID" 0 465 \
>     $SMTPD $VCHKPW /bin/true 2>&1
> 
> I may say all 3 run files are default settings from Erics install 
> script - only change I may recall is the softlimit that may have
> been 
> increased
> 
> My clients (mostly TB) are using ssl/tls - encrypted (name/passwd) 
> settings and are only using 465 or 587 to submit mails
> port 25 is only for server to server delivery 😏
> 
> Hope this may help
> 
> 
> Regards
> 
> Finn
> 
> PS I'm on Centos8 and Qmail for same - perfect
> 
> 
> Den 24-01-2021 kl. 07:31 skrev Dieter Febel:
> > Hi Eric,
> > 
> > I changed the file to what you recommended, but I am still getting 
> > the same error. I have authentication turned on in the email
> > client, 
> > and no encryption.
> > The reported error was "MAIL FROM command failed: Authorization 
> > required (#5.7.1)".
> > 
> > #!/bin/sh
> > QMAILDUID=`id -u vpopmail`
> > NOFILESGID=`id -g vpopmail`
> > MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> > SMTPD="/var/qmail/bin/qmail-smtpd"
> > TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> > HOSTNAME=`hostname`
> > VCHKPW="/home/vpopmail/bin/vchkpw"
> > export SMTPAUTH="!"
> > exec /usr/bin/softlimit -m 12800\
> >  /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
> > "$MAXSMTPD" \
> >  -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
> >  $SMTPD $VCHKPW /bin/true 2>&1
&

Re: [qmailtoaster] Error when trying to send on submission port

[qmail]

Hi Eric.

Well yes, and I believe they are in the 'default' setup  - at least I 
have 2 (submission, smtps) because I used to use 587 but switched to 465 
and left 587 running just in case...


(actually I responded to the mail because it looked like Dieter was 
making the changes in the smtp run file - and then he will face some 
other difficulties ;-) )


/Finn

Den 24-01-2021 kl. 18:17 skrev Eric Broch:

Are there two submission daemons running?

Restart server.

On 1/24/2021 9:10 AM, qm...@mailonly.dk wrote:

You need to have Your /var/qmail/supervise/smtp/run (port 25) as below

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/bin/spamdyke"
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="-"

exec /usr/bin/softlimit -m 12800 \
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
 $SPAMDYKE --config-file $SPAMDYKE_CONF \
 $SMTPD $VCHKPW /bin/true 2>&1



Then have the change  (copy the lines from Eric' mail) into the 
/var/qmail/supervise/submission/run (port 587)



and lastly here is my /var/run/supervise/smtps/run for port 465

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPS=1
export FORCETLS=0
export SMTPAUTH="!+cram"

exec /usr/bin/softlimit -m 12800 \
    /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
    -u "$QMAILDUID" -g "$NOFILESGID" 0 465 \
    $SMTPD $VCHKPW /bin/true 2>&1

I may say all 3 run files are default settings from Erics install 
script - only change I may recall is the softlimit that may have been 
increased


My clients (mostly TB) are using ssl/tls - encrypted (name/passwd) 
settings and are only using 465 or 587 to submit mails

port 25 is only for server to server delivery 😏

Hope this may help


Regards

Finn

PS I'm on Centos8 and Qmail for same - perfect


Den 24-01-2021 kl. 07:31 skrev Dieter Febel:

Hi Eric,

I changed the file to what you recommended, but I am still getting 
the same error. I have authentication turned on in the email client, 
and no encryption.
The reported error was "MAIL FROM command failed: Authorization 
required (#5.7.1)".


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"
exec /usr/bin/softlimit -m 12800\
     /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 $SMTPD $VCHKPW /bin/true 2>&1





-Original Message-

*Date*: Sat, 23 Jan 2021 10:17:11 -0700
*Subject*: Re: [qmailtoaster] Error when trying to send on submission 
port
*To*: qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com>

Reply-to: qmailtoaster-list@qmailtoaster.com
*From*: Eric Broch <mailto:eric%20broch%20%3cebr...@whitehorsetc.com%3e>>


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"

exec /usr/bin/softlimit -m 12800 \
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 $SMTPD $VCHKPW /bin/true 2>&1

On 1/23/2021 10:09 AM, Dieter Febel wrote:

Hi list,

The server only allows sending of email on port 465 or port 25. When 
I change to 587 with plain or with encryption I get:


Port 587 plain: The reported error was "MAIL FROM command failed: 
Authorization required (#5.7.1)". (Authentication is enabled in the 
mail client)


Here is my /var/qmail/supervise/smtp/run
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/b

Re: [qmailtoaster] Error when trying to send on submission port

[qmail]

You need to have Your /var/qmail/supervise/smtp/run (port 25) as below

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/bin/spamdyke"
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="-"

exec /usr/bin/softlimit -m 12800 \
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
 -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
 $SPAMDYKE --config-file $SPAMDYKE_CONF \
 $SMTPD $VCHKPW /bin/true 2>&1



Then have the change  (copy the lines from Eric' mail) into the 
/var/qmail/supervise/submission/run (port 587)



and lastly here is my /var/run/supervise/smtps/run for port 465

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPS=1
export FORCETLS=0
export SMTPAUTH="!+cram"

exec /usr/bin/softlimit -m 12800 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 465 \
$SMTPD $VCHKPW /bin/true 2>&1

I may say all 3 run files are default settings from Erics install script 
- only change I may recall is the softlimit that may have been increased


My clients (mostly TB) are using ssl/tls - encrypted (name/passwd) 
settings and are only using 465 or 587 to submit mails

port 25 is only for server to server delivery 😏

Hope this may help


Regards

Finn

PS I'm on Centos8 and Qmail for same - perfect


Den 24-01-2021 kl. 07:31 skrev Dieter Febel:

Hi Eric,

I changed the file to what you recommended, but I am still getting the 
same error. I have authentication turned on in the email client, and no 
encryption.
The reported error was "MAIL FROM command failed: Authorization required 
(#5.7.1)".


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"
exec /usr/bin/softlimit -m 12800\
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 $SMTPD $VCHKPW /bin/true 2>&1





-Original Message-

*Date*: Sat, 23 Jan 2021 10:17:11 -0700
*Subject*: Re: [qmailtoaster] Error when trying to send on submission port
*To*: qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com>

Reply-to: qmailtoaster-list@qmailtoaster.com
*From*: Eric Broch <mailto:eric%20broch%20%3cebr...@whitehorsetc.com%3e>>


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"

exec /usr/bin/softlimit -m 12800 \
     /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
     -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
     $SMTPD $VCHKPW /bin/true 2>&1

On 1/23/2021 10:09 AM, Dieter Febel wrote:

Hi list,

The server only allows sending of email on port 465 or port 25. When I 
change to 587 with plain or with encryption I get:


Port 587 plain: The reported error was "MAIL FROM command failed: 
Authorization required (#5.7.1)". (Authentication is enabled in the 
mail client)


Here is my /var/qmail/supervise/smtp/run
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SMTPD $VCHKPW /bin/true 2>&1

And my tcp.smtp
127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%/private" 



Any ideas?

Kind regards,

Dieter



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error when trying to send on submission port

[Eric Broch]

Are there two submission daemons running?

Restart server.

On 1/24/2021 9:10 AM, qm...@mailonly.dk wrote:

You need to have Your /var/qmail/supervise/smtp/run (port 25) as below

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SPAMDYKE="/usr/bin/spamdyke"
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="-"

exec /usr/bin/softlimit -m 12800 \
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
 $SPAMDYKE --config-file $SPAMDYKE_CONF \
 $SMTPD $VCHKPW /bin/true 2>&1



Then have the change  (copy the lines from Eric' mail) into the 
/var/qmail/supervise/submission/run (port 587)



and lastly here is my /var/run/supervise/smtps/run for port 465

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPS=1
export FORCETLS=0
export SMTPAUTH="!+cram"

exec /usr/bin/softlimit -m 12800 \
    /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
    -u "$QMAILDUID" -g "$NOFILESGID" 0 465 \
    $SMTPD $VCHKPW /bin/true 2>&1

I may say all 3 run files are default settings from Erics install 
script - only change I may recall is the softlimit that may have been 
increased


My clients (mostly TB) are using ssl/tls - encrypted (name/passwd) 
settings and are only using 465 or 587 to submit mails

port 25 is only for server to server delivery 😏

Hope this may help


Regards

Finn

PS I'm on Centos8 and Qmail for same - perfect


Den 24-01-2021 kl. 07:31 skrev Dieter Febel:

Hi Eric,

I changed the file to what you recommended, but I am still getting 
the same error. I have authentication turned on in the email client, 
and no encryption.
The reported error was "MAIL FROM command failed: Authorization 
required (#5.7.1)".


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"
exec /usr/bin/softlimit -m 12800\
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 $SMTPD $VCHKPW /bin/true 2>&1





-Original Message-

*Date*: Sat, 23 Jan 2021 10:17:11 -0700
*Subject*: Re: [qmailtoaster] Error when trying to send on submission 
port
*To*: qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com>

Reply-to: qmailtoaster-list@qmailtoaster.com
*From*: Eric Broch <mailto:eric%20broch%20%3cebr...@whitehorsetc.com%3e>>


#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"

exec /usr/bin/softlimit -m 12800 \
 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 $SMTPD $VCHKPW /bin/true 2>&1

On 1/23/2021 10:09 AM, Dieter Febel wrote:

Hi list,

The server only allows sending of email on port 465 or port 25. When 
I change to 587 with plain or with encryption I get:


Port 587 plain: The reported error was "MAIL FROM command failed: 
Authorization required (#5.7.1)". (Authentication is enabled in the 
mail client)


Here is my /var/qmail/supervise/smtp/run
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c 
"$MAXSMTPD" \

-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SMTPD $VCHKPW /bin/true 2>&1

And my tcp.smtp
127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQUEUE="/var/qmail/bin/sim

Re: [qmailtoaster] Error when trying to send on submission port

[Dieter Febel]

Hi Eric, 
I changed the file to what you recommended, but I am still getting the
same error. I have authentication turned on in the email client, and no
encryption. The reported error was "MAIL FROM command failed:
Authorization required (#5.7.1)".
#!/bin/sh

QMAILDUID=`id -u vpopmail`

NOFILESGID=`id -g vpopmail`

MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`

SMTPD="/var/qmail/bin/qmail-smtpd"

TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"

HOSTNAME=`hostname`

VCHKPW="/home/vpopmail/bin/vchkpw"

export SMTPAUTH="!"

exec /usr/bin/softlimit -m 12800 \

 /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c
"$MAXSMTPD" \

 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \

 $SMTPD $VCHKPW /bin/true 2>&1










-----Original Message-
Date: Sat, 23 Jan 2021 10:17:11 -0700Subject: Re: [qmailtoaster] Error
when trying to send on submission portTo: qmailtoaster-list@qmailtoaste
r.comReply-to: qmailtoaster-list@qmailtoaster.comFrom: Eric Broch 
  

  
  
#!/bin/sh

  QMAILDUID=`id -u vpopmail`

  NOFILESGID=`id -g vpopmail`

  MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`

  SMTPD="/var/qmail/bin/qmail-smtpd"

  TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"

  HOSTNAME=`hostname`

  VCHKPW="/home/vpopmail/bin/vchkpw"

  export SMTPAUTH="!"

  

  exec /usr/bin/softlimit -m 12800 \

  /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c
  "$MAXSMTPD" \

  -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \

  $SMTPD $VCHKPW /bin/true 2>&1

  


On 1/23/2021 10:09 AM, Dieter Febel
  wrote:



>   
>   Hi list, 
>   
> 
>   
>   The server only allows sending of email on port 465 or port
> 25. When I change to 587 with plain or with encryption I
> get: 
>   
> 
>   
>   Port 587 plain: The reported error was "MAIL FROM command
> failed: Authorization required (#5.7.1)". (Authentication is
> enabled in the mail client)
>   
> 
>   
>   Here is my /var/qmail/supervise/smtp/run
>   QMAILDUID=`id -u
>   vpopmail`
> 
>   NOFILESGID=`id -g vpopmail`
> 
> 
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> 
> 
> SMTPD="/var/qmail/bin/qmail-smtpd"
> 
> 
> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> 
> 
> HOSTNAME=`hostname`
> 
> 
> VCHKPW="/home/vpopmail/bin/vchkpw"
> 
> 
> REQUIRE_AUTH=0
> 
> 
> export FORCETLS=0
> 
> 
> export SMTPAUTH="+cram"
> 
> 
> exec /usr/bin/softlimit -m 10400 \
> 
> 
> /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c
> "$MAXSMTPD" \
> 
> 
> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
> 
> 
> $SMTPD $VCHKPW /bin/true 2>&1
> 
> 
> 
>   
>   
>   
> 
>   
> 
>   And my tcp.smtp 
>   127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKU
> SER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQU
> EUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-
> queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys
> /%/private"
>   
> 
> 
>   Any ideas? 
>   
> 
> 
>   Kind regards, 
>   
> 
> 
>   Dieter
>   
> 
> 
> 

  

Re: [qmailtoaster] Error when trying to send on submission port

[Eric Broch]

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
export SMTPAUTH="!"

exec /usr/bin/softlimit -m 12800 \
    /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
    -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
    $SMTPD $VCHKPW /bin/true 2>&1

On 1/23/2021 10:09 AM, Dieter Febel wrote:

Hi list,

The server only allows sending of email on port 465 or port 25. When I 
change to 587 with plain or with encryption I get:


Port 587 plain: The reported error was "MAIL FROM command failed: 
Authorization required (#5.7.1)". (Authentication is enabled in the 
mail client)


Here is my /var/qmail/supervise/smtp/run
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SMTPD="/var/qmail/bin/qmail-smtpd"
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
HOSTNAME=`hostname`
VCHKPW="/home/vpopmail/bin/vchkpw"
REQUIRE_AUTH=0
export FORCETLS=0
export SMTPAUTH="+cram"
exec /usr/bin/softlimit -m 10400 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
$SMTPD $VCHKPW /bin/true 2>&1

And my tcp.smtp
127.:allow,RELAYCLIENT="",BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",NOP0FCHECK="1",QMAILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%/private" 



Any ideas?

Kind regards,

Dieter

Re: [qmailtoaster] Error suggestions?

[ChandranManikandan]

Thank you Remo, Error was gone after updating the RAM size in smtp/run file.


On Thu, Jan 7, 2021 at 6:44 AM Eric Broch  wrote:

> Thanks, Remo!!!
> On 1/5/2021 10:48 PM, Remo Mattei wrote:
>
> exec /usr/bin/softlimit -m 10400 \
> In the smtp run file.
>
> Remo
>
> On Jan 5, 2021, at 21:39, ChandranManikandan  wrote:
>
> Hi Remo,
>
> I had the same issue, Are you changing the physical ram or any value in
> any clam file.
>
> I am running COS7 64 bit with 32 GB.
>
> On Wed, Jan 6, 2021 at 7:03 AM Remo Mattei  wrote:
>
>> I have it fixed.. I have changed it to more ram :)
>>
>> > On Jan 5, 2021, at 13:57, Remo Mattei  wrote:
>> >
>> > clamdscan: error while loading shared libraries: libtasn1.so.6: failed
>> to map segment from shared object: Cannot allocate memory
>> >
>> > Has anyone seen this suggestions?
>> >
>> > Thanks
>> > -
>> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> > For additional commands, e-mail:
>> qmailtoaster-list-h...@qmailtoaster.com
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>>
>
> --
>
>
> *Regards, Manikandan.C *
>
>
>

-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Error suggestions?

[Eric Broch]

Thanks, Remo!!!

On 1/5/2021 10:48 PM, Remo Mattei wrote:

exec /usr/bin/softlimit -m 10400 \
In the smtp run file.

Remo

On Jan 5, 2021, at 21:39, ChandranManikandan > wrote:


Hi Remo,

I had the same issue, Are you changing the physical ram or any value 
in any clam file.


I am running COS7 64 bit with 32 GB.

On Wed, Jan 6, 2021 at 7:03 AM Remo Mattei > wrote:


I have it fixed.. I have changed it to more ram :)

> On Jan 5, 2021, at 13:57, Remo Mattei mailto:r...@mattei.org>> wrote:
>
> clamdscan: error while loading shared libraries: libtasn1.so.6:
failed to map segment from shared object: Cannot allocate memory
>
> Has anyone seen this suggestions?
>
> Thanks
>
-
> To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

> For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com

>


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com




--
*/Regards,
Manikandan.C
/*

Re: [qmailtoaster] Error suggestions?

[Remo Mattei]

exec /usr/bin/softlimit -m 10400 \
In the smtp run file. 

Remo 

> On Jan 5, 2021, at 21:39, ChandranManikandan  wrote:
> 
> Hi Remo,
> 
> I had the same issue, Are you changing the physical ram or any value in any 
> clam file.
> 
> I am running COS7 64 bit with 32 GB.
> 
> On Wed, Jan 6, 2021 at 7:03 AM Remo Mattei  > wrote:
> I have it fixed.. I have changed it to more ram :) 
> 
> > On Jan 5, 2021, at 13:57, Remo Mattei  > > wrote:
> > 
> > clamdscan: error while loading shared libraries: libtasn1.so.6: failed to 
> > map segment from shared object: Cannot allocate memory
> > 
> > Has anyone seen this suggestions?
> > 
> > Thanks
> > -
> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
> > 
> > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
> > 
> > 
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
> 
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
> 
> 
> 
> 
> -- 
> Regards,
> Manikandan.C

Re: [qmailtoaster] Error suggestions?

[ChandranManikandan]

Hi Remo,

I had the same issue, Are you changing the physical ram or any value in any
clam file.

I am running COS7 64 bit with 32 GB.

On Wed, Jan 6, 2021 at 7:03 AM Remo Mattei  wrote:

> I have it fixed.. I have changed it to more ram :)
>
> > On Jan 5, 2021, at 13:57, Remo Mattei  wrote:
> >
> > clamdscan: error while loading shared libraries: libtasn1.so.6: failed
> to map segment from shared object: Cannot allocate memory
> >
> > Has anyone seen this suggestions?
> >
> > Thanks
> > -
> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> >
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Error suggestions?

[Remo Mattei]

I have it fixed.. I have changed it to more ram :) 

> On Jan 5, 2021, at 13:57, Remo Mattei  wrote:
> 
> clamdscan: error while loading shared libraries: libtasn1.so.6: failed to map 
> segment from shared object: Cannot allocate memory
> 
> Has anyone seen this suggestions?
> 
> Thanks
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Error on new mailserver setup

[Eric Broch]

In /var/qmail/supervise/smtp/run add

SIMSCAN_DEBUG=5

stop and start qmail

check log

On 10/22/2019 7:30 PM, Jeff Koch wrote:


Hi

On our new QMT7 mailserver we're seeing quite a few incoming emails 
being rejected with this message:


TLS reason: 451_mail_server_temporarily_rejected_message_(#4.3.0)

Anyone know what this is about ?

Thanks, Jeff Koch

P.S. Sorry for all the questions.


On 10/22/2019 9:27 AM, Eric Broch wrote:


Manual.

At some point I'll make an auto install...apologies.

On 10/22/2019 7:25 AM, Jeff Koch wrote:
Eric - thanks again. Question - is DKIM built in now or do we need 
to go through the setup process?


Jeff

On 10/22/2019 8:59 AM, Eric Broch wrote:


# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 
/var/qmail/bin/qmail-queue -> /var/qmail/bin/qmail-dk
-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 
/var/qmail/bin/qmail-queue.orig


Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to 
send email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. 
(#5.3.0)



Thanks, Jeff

Re: [qmailtoaster] Error on new mailserver setup

[Jeff Koch]

Hi

On our new QMT7 mailserver we're seeing quite a few incoming emails 
being rejected with this message:


TLS reason: 451_mail_server_temporarily_rejected_message_(#4.3.0)

Anyone know what this is about ?

Thanks, Jeff Koch

P.S. Sorry for all the questions.


On 10/22/2019 9:27 AM, Eric Broch wrote:


Manual.

At some point I'll make an auto install...apologies.

On 10/22/2019 7:25 AM, Jeff Koch wrote:
Eric - thanks again. Question - is DKIM built in now or do we need to 
go through the setup process?


Jeff

On 10/22/2019 8:59 AM, Eric Broch wrote:


# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 
/var/qmail/bin/qmail-queue -> /var/qmail/bin/qmail-dk
-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 
/var/qmail/bin/qmail-queue.orig


Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to send 
email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. 
(#5.3.0)



Thanks, Jeff

Re: [qmailtoaster] Error on new mailserver setup

[Eric Broch]

Manual.

At some point I'll make an auto install...apologies.

On 10/22/2019 7:25 AM, Jeff Koch wrote:
Eric - thanks again. Question - is DKIM built in now or do we need to 
go through the setup process?


Jeff

On 10/22/2019 8:59 AM, Eric Broch wrote:


# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 
/var/qmail/bin/qmail-queue -> /var/qmail/bin/qmail-dk
-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 
/var/qmail/bin/qmail-queue.orig


Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to send 
email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. 
(#5.3.0)



Thanks, Jeff

Re: [qmailtoaster] Error on new mailserver setup

[Jeff Koch]

Eric - thanks again. Question - is DKIM built in now or do we need to go 
through the setup process?


Jeff

On 10/22/2019 8:59 AM, Eric Broch wrote:


# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 
/var/qmail/bin/qmail-queue -> /var/qmail/bin/qmail-dk
-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 
/var/qmail/bin/qmail-queue.orig


Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to send 
email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. 
(#5.3.0)



Thanks, Jeff

Re: [qmailtoaster] Error on new mailserver setup

[Jeff Koch]

Eric - thanks - you are a life saver - Jeff

On 10/22/2019 8:59 AM, Eric Broch wrote:


# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 
/var/qmail/bin/qmail-queue -> /var/qmail/bin/qmail-dk
-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 
/var/qmail/bin/qmail-queue.orig


Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to send 
email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. 
(#5.3.0)



Thanks, Jeff

Re: [qmailtoaster] Error on new mailserver setup

[Eric Broch]

# ls -l /var/qmail/bin/qmail-queue /var/qmail/bin/qmail-queue.orig 
/var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 52096 Jan 21  2018 /var/qmail/bin/qmail-dk
lrwxrwxrwx 1 root   root 23 Jun 14  2018 /var/qmail/bin/qmail-queue 
-> /var/qmail/bin/qmail-dk

-rws--x--x 1 qmailq qmail 27040 Jan 21  2018 /var/qmail/bin/qmail-queue.orig

Stop qmail

# qmailctl stop

Remove symlink to qmail-dk

# unlink /var/qmail/bin/qmail-queue

Move qmail-queue.orig to qmail-queue

# mv /var/qmail/bin/qmail-queue.orig /var/qmail/bin/qmail-queue

Start qmail

# qmailctl start

Remove DKSIGN, DKVERIFY, DKQUEUE (DomainKeys) from tcp.smtp.

# qmailctl cdb

On 10/22/2019 6:50 AM, Jeff Koch wrote:


Hi:

Anyone know why we would be seeing this message when trying to send 
email on a new QMT7 setup?


554 qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0)


Thanks, Jeff

RE: [qmailtoaster] Error on new mailserver setup

[CarlC Internet Services Service Desk]

I think this is the old issue where /var/qmail/bin/qmail-queue is “ln” to 
queue-dk. You might want to undo the “ln” and create a new one to 
qmail-queue.orig ….

 

Carl

 

From: Jeff Koch [mailto:jeffk...@intersessions.com] 
Sent: Tuesday, October 22, 2019 08:50 AM
To: qmailtoaster-list@qmailtoaster.com; Eric Broch 
Subject: [qmailtoaster] Error on new mailserver setup

 


Hi:

Anyone know why we would be seeing this message when trying to send email on a 
new QMT7 setup?

554 qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0) 


Thanks, Jeff

Re: [qmailtoaster] ERROR: accept() failed

[Eric Broch]

-rw-r--r-- 1 clamav clamav    766976 Dec  6 20:54 bytecode.cld
-rw-r--r-- 1 clamav clamav 131212800 Jan 26 03:46 daily.cld
-rw-r--r-- 1 clamav clamav 307499008 Jun  7  2017 main.cld
-rw--- 1 clamav clamav  1716 Jan 26 09:46 mirrors.dat

ClamAV update process started at Fri Jan 26 10:10:06 2018
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.99.2 Recommended version: 0.99.3
DON'T PANIC! Read http://www.clamav.net/documents/upgrading-clamav
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, 
builder: sigmgr)
daily.cld is up to date (version: 24257, sigs: 1835982, f-level: 63, 
builder: neo)
bytecode.cld is up to date (version: 319, sigs: 75, f-level: 63, 
builder: neo)


This server is working fine


On 1/26/2018 10:05 AM, Michele Federici wrote:


Hi,

I have in my centos 7

drwxr-x---   2 clamav root 6 26 gen 17.44 simscan

and

exec /usr/bin/softlimit -m 6400 \

The server configuration did not change and the anomaly start this 
morning.


What versions do you have of the virus definitions?

Jan 26 17:18:13 mailbox freshclam: daily.cld updated (version: 24257, 
sigs: 1835982, f-level: 63, builder: neo)



thank you

--
Michele Federici
Il 26/01/2018 17:46, Remo Mattei ha scritto:

Michele a me funziona con la versione che hai tu.

I have the same version and it’s all working permissions check my email

Inviato da iPhone


Il giorno 26 gen 2018, alle ore 16:47, Peter Peltonen 
 ha scritto:

First thing that comes to my mind is to check qmail directory
ownerships and permissions?


On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  wrote:
Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return "Unable to
open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com




- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 


--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] ERROR: accept() failed

[Michele Federici]

  
  
Hi, 

I have in my centos 7 

drwxr-x---   2 clamav root 6 26 gen 17.44 simscan
  
  and

exec /usr/bin/softlimit -m 6400 \
The server configuration did not change and the anomaly start
  this morning.

What versions do you have of the virus definitions?

Jan 26 17:18:13 mailbox freshclam: daily.cld updated (version:
  24257, sigs: 1835982, f-level: 63, builder: neo)


  thank you 
-- 
Michele Federici

Il 26/01/2018 17:46, Remo Mattei ha
  scritto:


  Michele a me funziona con la versione che hai tu. 

I have the same version and it’s all working permissions check my email 

Inviato da iPhone


  
Il giorno 26 gen 2018, alle ore 16:47, Peter Peltonen  ha scritto:

First thing that comes to my mind is to check qmail directory
ownerships and permissions?



  On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  wrote:
Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return "Unable to
open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  
  

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com





  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Sean Murphy]

Well, I spoke too soon, soft reject messages started popping up on my 
CentOS 5 server.  I have disabled ClamAV and will continue to monitor.



On 1/26/2018 11:00 AM, Eric Broch wrote:

Ahhh! ClamAV again.


On 1/26/2018 8:57 AM, Havrla wrote:

Peter:
detail my log:
Jan 26 11:24:50 tonda clamd: LibClamAV Error: cli_gentempfd: Can't 
create temporary file 
/tmp/clamav-4cfa012223685613cbdd51ea20c64a9a.tmp/clamav-696c37f51f984623e21bb7af92cbbf08.tmp: 
Too many open files


Havrla

Dne 26.1.2018 v 16:47 Peter Peltonen napsal(a):

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici 
 wrote:

Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: 
OK

Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open 
file or

directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316: 


Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316: 


Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open 
file or

directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return 
"Unable to

open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Remo Mattei]

Michele a me funziona con la versione che hai tu. 

I have the same version and it’s all working permissions check my email 

Inviato da iPhone

> Il giorno 26 gen 2018, alle ore 16:47, Peter Peltonen 
>  ha scritto:
> 
> First thing that comes to my mind is to check qmail directory
> ownerships and permissions?
> 
>> On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  
>> wrote:
>> Hi,
>> 
>> I have a qmail server that today returns in the smtp log "mail server
>> temporarily rejected message (# 4.3.0)".
>> 
>> Everything works fine until the start of these errors on simscan
>> 
>> Fri Jan 26 10:00:52 2018 ->
>> /var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
>> Fri Jan 26 10:01:16 2018 ->
>> /var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
>> Fri Jan 26 10:01:16 2018 ->
>> /var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
>> Fri Jan 26 10:01:16 2018 ->
>> /var/qmail/simscan/1516957274.430368.10271/textfile0: OK
>> Fri Jan 26 10:01:16 2018 ->
>> /var/qmail/simscan/1516957274.430368.10271/textfile1: OK
>> Fri Jan 26 10:01:16 2018 ->
>> /var/qmail/simscan/1516957274.430368.10271/textfile2: OK
>> Fri Jan 26 10:01:20 2018 ->
>> /var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
>> Fri Jan 26 10:01:20 2018 ->
>> /var/qmail/simscan/1516957279.523709.10292/textfile2: OK
>> Fri Jan 26 10:01:20 2018 ->
>> /var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
>> directory ERROR
>> Fri Jan 26 10:01:20 2018 ->
>> /var/qmail/simscan/1516957279.523709.10292/image001.png: OK
>> Fri Jan 26 10:01:20 2018 ->
>> /var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
>> Fri Jan 26 10:01:23 2018 ->
>> /var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
>> Can't open file or directory ERROR
>> Fri Jan 26 10:01:23 2018 ->
>> /var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
>> Can't create new file ERROR
>> Fri Jan 26 10:01:23 2018 ->
>> /var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
>> directory ERROR
>> [..]
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>> 
>> So I restart
>> 
>> # systemctl restart clamav-daemon.service
>> # systemctl restart clamav-daemon.socket
>> 
>> and then everything works fine until simscan restarts to return "Unable to
>> open file or directory ERROR"
>> 
>> I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.
>> 
>> Any suggestions?
>> 
>> --
>> Michele Federici
>> 
>> 
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Remo Mattei]

I recall to fix this with some permissions I am in Europe now will check ASAP 
and share my settings. 

Inviato da iPhone

> Il giorno 26 gen 2018, alle ore 11:24, Michele Federici 
>  ha scritto:
> 
> Hi,
> 
> I have a qmail server that today returns in the smtp log "mail server 
> temporarily rejected message (# 4.3.0)".
> 
> Everything works fine until the start of these errors on simscan
> 
> Fri Jan 26 10:00:52 2018 -> 
> /var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
> Fri Jan 26 10:01:16 2018 -> 
> /var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
> Fri Jan 26 10:01:16 2018 -> 
> /var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
> Fri Jan 26 10:01:16 2018 -> 
> /var/qmail/simscan/1516957274.430368.10271/textfile0: OK
> Fri Jan 26 10:01:16 2018 -> 
> /var/qmail/simscan/1516957274.430368.10271/textfile1: OK
> Fri Jan 26 10:01:16 2018 -> 
> /var/qmail/simscan/1516957274.430368.10271/textfile2: OK
> Fri Jan 26 10:01:20 2018 -> 
> /var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
> Fri Jan 26 10:01:20 2018 -> 
> /var/qmail/simscan/1516957279.523709.10292/textfile2: OK
> Fri Jan 26 10:01:20 2018 -> 
> /var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or 
> directory ERROR
> Fri Jan 26 10:01:20 2018 -> 
> /var/qmail/simscan/1516957279.523709.10292/image001.png: OK
> Fri Jan 26 10:01:20 2018 -> 
> /var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
> Fri Jan 26 10:01:23 2018 -> 
> /var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316: Can't 
> open file or directory ERROR
> Fri Jan 26 10:01:23 2018 -> 
> /var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316: 
> Can't create new file ERROR
> Fri Jan 26 10:01:23 2018 -> 
> /var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or 
> directory ERROR
> [..]
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> 
> So I restart
> 
> # systemctl restart clamav-daemon.service
> # systemctl restart clamav-daemon.socket
> 
> and then everything works fine until simscan restarts to return "Unable to 
> open file or directory ERROR"
> 
> I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.
> 
> Any suggestions?
> 
> -- 
> Michele Federici
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Michele Federici]

  
  
Hi,

I confirm you: after 1 hour the problem caming back

I prefer do not stop clamav. I've create a script who check every
few minutes "/var/log/clamd/clamd.log" and if there is an errore it
restart clamav

thank you 
-- 
Michele Federici

Il 26/01/2018 17:18, Havrla ha scritto:


  
  Hi

Restart clamav fix only for cca 1 hour. After
problem back.


I turned off simscan for clamav.    
file /var/qmail/control/simcontrol
:clam=no,spam=yes,spam_hits=12,attach=.src:.bat:.pif:.js

/etc/init.d/qmail cdb


I'm waiting for another update clamav (antivir base).
  We'll see tomorrow.

  H.

  
Dne 26.1.2018 v 17:08 Michele Federici napsal(a):
  
  
Hi,
I have more than 200 GB
  free.
But i think is the
  current clamav signature problem. This post is similar http://lists.clamav.net/pipermail/clamav-users/2018-January/005658.html

If i restart clamav
  works all fine. 

Thank you 
  
  
  


  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Havrla]

Hi

Restart clamav fix only for cca 1 hour. After problem back.


I turned off simscan for clamav.
file /var/qmail/control/simcontrol
:clam=no,spam=yes,spam_hits=12,attach=.src:.bat:.pif:.js

/etc/init.d/qmail cdb


I'm waiting for another update clamav (antivir base).
We'll see tomorrow.

H.


Dne 26.1.2018 v 17:08 Michele Federici napsal(a):


Hi,

I have more than 200 GB free.

But i think is the current clamav signature problem. This post is 
similar 
http://lists.clamav.net/pipermail/clamav-users/2018-January/005658.html


If i restart clamav works all fine.

Thank you

Re: [qmailtoaster] ERROR: accept() failed

[Sean Murphy]

This seems like the situation we were experiencing back in March of last 
year, where a bad daily hit servers running CentOS 5 until they changed 
how clamav used pcre to link the database.  I don't know if it's the 
same case here.


Our CentOS 5 server (32-bit) and CentOS 7 server (64-bit) are not affected.

Unfortunately, ClamAV 99.3 isn't supported on CentOS 5, so it looks as 
though I'll be having to make that migration I've been putting off :)



On 1/26/2018 11:00 AM, Eric Broch wrote:

Ahhh! ClamAV again.


On 1/26/2018 8:57 AM, Havrla wrote:

Peter:
detail my log:
Jan 26 11:24:50 tonda clamd: LibClamAV Error: cli_gentempfd: Can't 
create temporary file 
/tmp/clamav-4cfa012223685613cbdd51ea20c64a9a.tmp/clamav-696c37f51f984623e21bb7af92cbbf08.tmp: 
Too many open files


Havrla

Dne 26.1.2018 v 16:47 Peter Peltonen napsal(a):

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici 
 wrote:

Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: 
OK

Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open 
file or

directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316: 


Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316: 


Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open 
file or

directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return 
"Unable to

open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Michele Federici]

  
  
Hi,
I have more than 200 GB free.
But i think is the current
  clamav signature problem. This post is similar
  http://lists.clamav.net/pipermail/clamav-users/2018-January/005658.html

If i restart clamav works
  all fine. 

Thank you 

-- 
Michele Federici

Il 26/01/2018 16:59, Eric Broch ha
  scritto:

Hi 
  Michele
  
  
  Is the directory /var/qmail/simscan full? How much space do you
  have?
  
  
  Check out this link on the mailing list for permissions issues
  some have had:
  
  
https://www.mail-archive.com/search?q=SOLVED+-+qq+soft+reject+with+Centos+7&l=qmailtoaster-list%40qmailtoaster.com
  
  
  On 1/26/2018 8:47 AM, Peter Peltonen wrote:
  
  First thing that comes to my mind is to
check qmail directory

ownerships and permissions?


On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici
 wrote:

Hi,
  
  
  I have a qmail server that today returns in the smtp log "mail
  server
  
  temporarily rejected message (# 4.3.0)".
  
  
  Everything works fine until the start of these errors on
  simscan
  
  
  Fri Jan 26 10:00:52 2018 ->
  
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf:
  OK
  
  Fri Jan 26 10:01:16 2018 ->
  
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271:
  OK
  
  Fri Jan 26 10:01:16 2018 ->
  
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271:
  OK
  
  Fri Jan 26 10:01:16 2018 ->
  
  /var/qmail/simscan/1516957274.430368.10271/textfile0: OK
  
  Fri Jan 26 10:01:16 2018 ->
  
  /var/qmail/simscan/1516957274.430368.10271/textfile1: OK
  
  Fri Jan 26 10:01:16 2018 ->
  
  /var/qmail/simscan/1516957274.430368.10271/textfile2: OK
  
  Fri Jan 26 10:01:20 2018 ->
  
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292:
  OK
  
  Fri Jan 26 10:01:20 2018 ->
  
  /var/qmail/simscan/1516957279.523709.10292/textfile2: OK
  
  Fri Jan 26 10:01:20 2018 ->
  
  /var/qmail/simscan/1516957279.523709.10292/textfile3: Can't
  open file or
  
  directory ERROR
  
  Fri Jan 26 10:01:20 2018 ->
  
  /var/qmail/simscan/1516957279.523709.10292/image001.png: OK
  
  Fri Jan 26 10:01:20 2018 ->
  
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf:
  OK
  
  Fri Jan 26 10:01:23 2018 ->
  
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
  
  Can't open file or directory ERROR
  
  Fri Jan 26 10:01:23 2018 ->
  
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
  
  Can't create new file ERROR
  
  Fri Jan 26 10:01:23 2018 ->
  
  /var/qmail/simscan/1516957282.930250.10316/textfile0: Can't
  open file or
  
  directory ERROR
  
  [..]
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
  
  
  So I restart
  
  
  # systemctl restart clamav-daemon.service
  
  # systemctl restart clamav-daemon.socket
  
  
  and then everything works fine until simscan restarts to
  return "Unable to
  
  open file or directory ERROR"
  
  
  I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.
  
  
  Any suggestions?
  
  
  --
  
  Michele Federici
  
  
  
-
  
  To unsubscribe, e-mail:
  qmailtoaster-list-unsubscr...@qmailtoaster.com
  
  For additional commands, e-mail:
  qmailtoaster-list-h...@qmailtoaster.com
  
  

-

To unsubscribe

Re: [qmailtoaster] ERROR: accept() failed

[Eric Broch]

Ahhh! ClamAV again.


On 1/26/2018 8:57 AM, Havrla wrote:

Peter:
detail my log:
Jan 26 11:24:50 tonda clamd: LibClamAV Error: cli_gentempfd: Can't 
create temporary file 
/tmp/clamav-4cfa012223685613cbdd51ea20c64a9a.tmp/clamav-696c37f51f984623e21bb7af92cbbf08.tmp: 
Too many open files


Havrla

Dne 26.1.2018 v 16:47 Peter Peltonen napsal(a):

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici 
 wrote:

Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: 
OK

Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: 
OK

Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open 
file or

directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: 
OK

Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316: 


Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open 
file or

directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return 
"Unable to

open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



--
Eric Broch
White Horse Technical Consulting (WHTC)


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Eric Broch]

Hi  Michele

Is the directory /var/qmail/simscan full? How much space do you have?

Check out this link on the mailing list for permissions issues some have 
had:


https://www.mail-archive.com/search?q=SOLVED+-+qq+soft+reject+with+Centos+7&l=qmailtoaster-list%40qmailtoaster.com

On 1/26/2018 8:47 AM, Peter Peltonen wrote:

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  wrote:

Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return "Unable to
open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



--
Eric Broch
White Horse Technical Consulting (WHTC)


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Havrla]

Peter:
detail my log:
Jan 26 11:24:50 tonda clamd: LibClamAV Error: cli_gentempfd: Can't 
create temporary file 
/tmp/clamav-4cfa012223685613cbdd51ea20c64a9a.tmp/clamav-696c37f51f984623e21bb7af92cbbf08.tmp: 
Too many open files


Havrla

Dne 26.1.2018 v 16:47 Peter Peltonen napsal(a):

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  wrote:

Hi,

I have a qmail server that today returns in the smtp log "mail server
temporarily rejected message (# 4.3.0)".

Everything works fine until the start of these errors on simscan

Fri Jan 26 10:00:52 2018 ->
/var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile0: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile1: OK
Fri Jan 26 10:01:16 2018 ->
/var/qmail/simscan/1516957274.430368.10271/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile2: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
directory ERROR
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/image001.png: OK
Fri Jan 26 10:01:20 2018 ->
/var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
Can't open file or directory ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
Can't create new file ERROR
Fri Jan 26 10:01:23 2018 ->
/var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
directory ERROR
[..]
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:

So I restart

# systemctl restart clamav-daemon.service
# systemctl restart clamav-daemon.socket

and then everything works fine until simscan restarts to return "Unable to
open file or directory ERROR"

I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.

Any suggestions?

--
Michele Federici


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] ERROR: accept() failed

[Peter Peltonen]

First thing that comes to my mind is to check qmail directory
ownerships and permissions?

On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici  wrote:
> Hi,
>
> I have a qmail server that today returns in the smtp log "mail server
> temporarily rejected message (# 4.3.0)".
>
> Everything works fine until the start of these errors on simscan
>
> Fri Jan 26 10:00:52 2018 ->
> /var/qmail/simscan/1516957251.438820.10197/doc05577520180126111044.pdf: OK
> Fri Jan 26 10:01:16 2018 ->
> /var/qmail/simscan/1516957274.430368.10271/msg.1516957274.430368.10271: OK
> Fri Jan 26 10:01:16 2018 ->
> /var/qmail/simscan/1516957274.430368.10271/addr.1516957274.430368.10271: OK
> Fri Jan 26 10:01:16 2018 ->
> /var/qmail/simscan/1516957274.430368.10271/textfile0: OK
> Fri Jan 26 10:01:16 2018 ->
> /var/qmail/simscan/1516957274.430368.10271/textfile1: OK
> Fri Jan 26 10:01:16 2018 ->
> /var/qmail/simscan/1516957274.430368.10271/textfile2: OK
> Fri Jan 26 10:01:20 2018 ->
> /var/qmail/simscan/1516957279.523709.10292/addr.1516957279.523709.10292: OK
> Fri Jan 26 10:01:20 2018 ->
> /var/qmail/simscan/1516957279.523709.10292/textfile2: OK
> Fri Jan 26 10:01:20 2018 ->
> /var/qmail/simscan/1516957279.523709.10292/textfile3: Can't open file or
> directory ERROR
> Fri Jan 26 10:01:20 2018 ->
> /var/qmail/simscan/1516957279.523709.10292/image001.png: OK
> Fri Jan 26 10:01:20 2018 ->
> /var/qmail/simscan/1516957279.523709.10292/doc05577520180126111044.pdf: OK
> Fri Jan 26 10:01:23 2018 ->
> /var/qmail/simscan/1516957282.930250.10316/msg.1516957282.930250.10316:
> Can't open file or directory ERROR
> Fri Jan 26 10:01:23 2018 ->
> /var/qmail/simscan/1516957282.930250.10316/addr.1516957282.930250.10316:
> Can't create new file ERROR
> Fri Jan 26 10:01:23 2018 ->
> /var/qmail/simscan/1516957282.930250.10316/textfile0: Can't open file or
> directory ERROR
> [..]
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
> Fri Jan 26 10:09:15 2018 -> ERROR: accept() failed:
>
> So I restart
>
> # systemctl restart clamav-daemon.service
> # systemctl restart clamav-daemon.socket
>
> and then everything works fine until simscan restarts to return "Unable to
> open file or directory ERROR"
>
> I'm running qmailtoaster on Centos 7 with ClamAV 0.99.2.
>
> Any suggestions?
>
> --
> Michele Federici
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

Forget last post, Squiirrelmail is working after changing the conf file.
Is there a post or guide for roundcube anywhere, or just use generic 
instructions at roundcube?

Thanks to everyone.
David Overman

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

tried your conf file :

[root@mail httpd]# journalctl -xe
--
-- Unit httpd.service has begun shutting down.
Nov 30 07:41:22 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Nov 30 07:41:22 mail.davomail.com httpd[17420]: AH00526: Syntax error on line 1 
of /etc/httpd/conf/squirrelmail.conf:
Nov 30 07:41:22 mail.davomail.com httpd[17420]: Invalid command 
'http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Nov 30 07:41:22 mail.davomail.com systemd[1]: Unit httpd.service entered failed 
state.
Nov 30 07:41:22 mail.davomail.com systemd[1]: httpd.service failed.

[root@mail httpd]# nano +8 /etc/httpd/conf/squirrelmail.conf
[root@mail httpd]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service
[root@mail httpd]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: 
disabled)
Active: active (running) since Wed 2016-11-30 07:42:20 UTC; 17s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 17422 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, 
status=1/FAILURE)
Main PID: 17445 (httpd)
Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec"
CGroup: /system.slice/httpd.service
├─17445 /usr/sbin/httpd -DFOREGROUND
├─17446 /usr/sbin/httpd -DFOREGROUND
├─17447 /usr/sbin/httpd -DFOREGROUND
├─17448 /usr/sbin/httpd -DFOREGROUND
├─17449 /usr/sbin/httpd -DFOREGROUND
└─17450 /usr/sbin/httpd -DFOREGROUND

Nov 30 07:42:20 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
Nov 30 07:42:20 mail.davomail.com systemd[1]: Started The Apache HTTP Server.
[root@mail httpd]# journalctl -xe
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Nov 30 07:41:22 mail.davomail.com systemd[1]: Unit httpd.service entered failed 
state.
Nov 30 07:41:22 mail.davomail.com systemd[1]: httpd.service failed.
Nov 30 07:41:22 mail.davomail.com polkitd[2662]: Unregistered Authentication 
Agent for unix-process:17400:2483501 (system bus name :1.282, object path 
/org/freedesktop/PolicyKit1/
Nov 30 07:42:20 mail.davomail.com polkitd[2662]: Registered Authentication 
Agent for unix-process:17430:2489410 (system bus name :1.283 
[/usr/bin/pkttyagent --notify-fd 5 --fallba
Nov 30 07:42:20 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Nov 30 07:42:20 mail.davomail.com systemd[1]: Started The Apache HTTP Server.
-- Subject: Unit httpd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has finished starting up.
--
-- The start-up result is done.
Nov 30 07:42:20 mail.davomail.com polkitd[2662]: Unregistered Authentication 
Agent for unix-process:17430:2489410 (system bus name :1.283, object path 
/org/freedesktop/PolicyKit1/
lines 1992-2014/2014 (END)
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Nov 30 07:41:22 mail.davomail.com systemd[1]: Unit httpd.service entered failed 
state.
Nov 30 07:41:22 mail.davomail.com systemd[1]: httpd.service failed.
Nov 30 07:41:22 mail.davomail.com polkitd[2662]: Unregistered Authentication 
Agent for unix-process:17400:2483501 (system bus name :1.282, object path 
/org/freedesktop/PolicyKit1
Nov 30 07:42:20 mail.davomail.com polkitd[2662]: Registered Authentication 
Agent for unix-process:17430:2489410 (system bus name :1.283 
[/usr/bin/pkttyagent --notify-fd 5 --fallb
Nov 30 07:42:20 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Nov 30 07:42:20 mail.davomail.com systemd[1]: Started The Apache HTTP Server.
-- Subject: Unit httpd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has finished starting up.
--
-- The start-up result is done.
Nov 30 07:42:20 mail.davomail.com polkitd[2662]: Unregistered Authentication 
Agent for unix-process:17430:2489410 (system bus name :1.283, object path 
/org/freedesktop/PolicyKit1
lines 1992-2014/2014 (END)
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Nov 30 07:41:22 mail.davomail.com systemd[1]: Unit httpd.service entered failed 
state.
Nov 30 07:41:22 mail.davomail.com systemd[1]: httpd.service failed.
Nov 30 07:41:22 mail.davomail.com polkitd[2662]: Un

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Here's my squirrelmail.conf




#
# SquirrelMail is a webmail package written in PHP.
#
Alias /webmail /usr/share/squirrelmail

  
# Apache 2.4
Require all denied
  
  
# Apache 2.2
Order deny,allow
Deny from all
  


# this section makes squirrelmail use https connections only, for this you
# need to have mod_ssl installed. If you want to use unsecure http
# connections, just remove this section:

  RewriteEngine  on
  RewriteCond%{HTTPS} !=on
  RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
  
# Apache 2.4
Require all granted
  
  
# Apache 2.2
Order allow,deny
Allow from all
  




On 11/29/2016 9:49 PM, David Overman wrote:
At least httpd started, but resulted in a 404 error 
https://mail.davomail.com/webmail

and https://davomail.com/webmail logs show named errors.

[root@mail httpd]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service
[root@mail httpd]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor 
preset: disabled)

Active: active (running) since Wed 2016-11-30 04:36:13 UTC; 28s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 4993 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, 
status=1/FAILURE)

Main PID: 11361 (httpd)
Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 
0 B/sec"

CGroup: /system.slice/httpd.service
├─11361 /usr/sbin/httpd -DFOREGROUND
├─11362 /usr/sbin/httpd -DFOREGROUND
├─11363 /usr/sbin/httpd -DFOREGROUND
├─11364 /usr/sbin/httpd -DFOREGROUND
├─11365 /usr/sbin/httpd -DFOREGROUND
└─11366 /usr/sbin/httpd -DFOREGROUND

Nov 30 04:36:13 mail.davomail.com systemd[1]: Starting The Apache HTTP 
Server...
Nov 30 04:36:13 mail.davomail.com systemd[1]: Started The Apache HTTP 
Server.

[root@mail httpd]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor 
preset: disabled)

Active: active (running) since Wed 2016-11-30 04:36:13 UTC; 1min 55s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 4993 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, 
status=1/FAILURE)

Main PID: 11361 (httpd)
Status: "Total requests: 2; Current requests/sec: 0; Current traffic: 
0 B/sec"

CGroup: /system.slice/httpd.service
├─11361 /usr/sbin/httpd -DFOREGROUND
├─11362 /usr/sbin/httpd -DFOREGROUND
├─11363 /usr/sbin/httpd -DFOREGROUND
├─11364 /usr/sbin/httpd -DFOREGROUND
├─11365 /usr/sbin/httpd -DFOREGROUND
├─11366 /usr/sbin/httpd -DFOREGROUND
└─11380 /usr/sbin/httpd -DFOREGROUND

Nov 30 04:36:13 mail.davomail.com systemd[1]: Starting The Apache HTTP 
Server...
Nov 30 04:36:13 mail.davomail.com systemd[1]: Started The Apache HTTP 
Server.

[root@mail httpd]# nano +8 /etc/httpd/conf/squirrelmail.conf
[root@mail httpd]# cat ssl_request_log
[30/Nov/2016:04:39:49 +] 174.69.49.189 TLSv1.2 
ECDHE-RSA-AES128-GCM-SHA256 "GET /webmail HTTP/1.1" 205
[30/Nov/2016:04:39:50 +] 174.69.49.189 TLSv1.2 
ECDHE-RSA-AES128-GCM-SHA256 "GET /favicon.ico HTTP/1.1" 209
[30/Nov/2016:04:40:27 +] 174.69.49.189 TLSv1.2 
ECDHE-RSA-AES128-GCM-SHA256 "GET /webmail HTTP/1.1" 205
[30/Nov/2016:04:40:28 +] 174.69.49.189 TLSv1.2 
ECDHE-RSA-AES128-GCM-SHA256 "GET /favicon.ico HTTP/1.1" 209

[root@mail httpd]# journalctl -xe
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving 'dns1.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving 'dns2.vietel.com.vn/A/IN': 203.113.131.2#53
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving 'dns2.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving '130.214.105.116.in-addr.arpa/PTR/IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving '130.214.105.116.in-addr.arpa/CNAME/IN': 
203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving 'dns1.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE 
REFUSED) resolving 'dns2.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:56 mail.davomail.com spamdyke[11395]: DENIED_RDNS_MISSING 
from: man.erickson.8...@peckerwoodsltd.com to: ad...@davomail.com 
origin_ip: 116.105.214.130 origin_rdns: (u
Nov 30 04:40:01 mail.davomail.com systemd[1]: Started Session 55 of 
user root









On Nov 29, 2016, at 08:32 PM, Eric Broch  wrote:


Change

ErrorDocument 403 "https://mail.davomail.com/webmail/";;

To

ErrorDocument 403 https://mail.davomail.com/webmail/


On 11/29/2016 6:34 PM, David Overman wrote:

RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

At least httpd started, but resulted in a 404 error 
https://mail.davomail.com/webmail
and https://davomail.com/webmail logs show named errors.

[root@mail httpd]# service httpd restart
Redirecting to /bin/systemctl restart httpd.service
[root@mail httpd]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: 
disabled)
Active: active (running) since Wed 2016-11-30 04:36:13 UTC; 28s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 4993 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, 
status=1/FAILURE)
Main PID: 11361 (httpd)
Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec"
CGroup: /system.slice/httpd.service
├─11361 /usr/sbin/httpd -DFOREGROUND
├─11362 /usr/sbin/httpd -DFOREGROUND
├─11363 /usr/sbin/httpd -DFOREGROUND
├─11364 /usr/sbin/httpd -DFOREGROUND
├─11365 /usr/sbin/httpd -DFOREGROUND
└─11366 /usr/sbin/httpd -DFOREGROUND

Nov 30 04:36:13 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
Nov 30 04:36:13 mail.davomail.com systemd[1]: Started The Apache HTTP Server.
[root@mail httpd]# service httpd status
Redirecting to /bin/systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: 
disabled)
Active: active (running) since Wed 2016-11-30 04:36:13 UTC; 1min 55s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 4993 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, 
status=1/FAILURE)
Main PID: 11361 (httpd)
Status: "Total requests: 2; Current requests/sec: 0; Current traffic: 0 B/sec"
CGroup: /system.slice/httpd.service
├─11361 /usr/sbin/httpd -DFOREGROUND
├─11362 /usr/sbin/httpd -DFOREGROUND
├─11363 /usr/sbin/httpd -DFOREGROUND
├─11364 /usr/sbin/httpd -DFOREGROUND
├─11365 /usr/sbin/httpd -DFOREGROUND
├─11366 /usr/sbin/httpd -DFOREGROUND
└─11380 /usr/sbin/httpd -DFOREGROUND

Nov 30 04:36:13 mail.davomail.com systemd[1]: Starting The Apache HTTP Server...
Nov 30 04:36:13 mail.davomail.com systemd[1]: Started The Apache HTTP Server.
[root@mail httpd]# nano +8 /etc/httpd/conf/squirrelmail.conf
[root@mail httpd]# cat ssl_request_log 
[30/Nov/2016:04:39:49 +] 174.69.49.189 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET /webmail HTTP/1.1" 205

[30/Nov/2016:04:39:50 +] 174.69.49.189 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET 
/favicon.ico HTTP/1.1" 209
[30/Nov/2016:04:40:27 +] 174.69.49.189 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET 
/webmail HTTP/1.1" 205
[30/Nov/2016:04:40:28 +] 174.69.49.189 TLSv1.2 ECDHE-RSA-AES128-GCM-SHA256 "GET 
/favicon.ico HTTP/1.1" 209
[root@mail httpd]# journalctl -xe
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving 'dns1.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving 'dns2.vietel.com.vn/A/IN': 203.113.131.2#53
Nov 30 04:38:45 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving 'dns2.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving '130.214.105.116.in-addr.arpa/PTR/IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving '130.214.105.116.in-addr.arpa/CNAME/IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving 'dns1.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:47 mail.davomail.com named[4977]: error (unexpected RCODE REFUSED) 
resolving 'dns2.vietel.com.vn//IN': 203.113.131.2#53
Nov 30 04:38:56 mail.davomail.com spamdyke[11395]: DENIED_RDNS_MISSING from: 
man.erickson.8...@peckerwoodsltd.com to: ad...@davomail.com origin_ip: 
116.105.214.130 origin_rdns: (u
Nov 30 04:40:01 mail.davomail.com systemd[1]: Started Session 55 of user root








On Nov 29, 2016, at 08:32 PM, Eric Broch  wrote:

Change

ErrorDocument 403 "https://mail.davomail.com/webmail/";;

To

ErrorDocument 403 https://mail.davomail.com/webmail/


On 11/29/2016 6:34 PM, David Overman wrote:
RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://mail.davomail.com/webmail/";;


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Change

ErrorDocument 403 "https://mail.davomail.com/webmail/";;

To

ErrorDocument 403 https://mail.davomail.com/webmail/


On 11/29/2016 6:34 PM, David Overman wrote:

RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://mail.davomail.com/webmail/";;



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

ut PAM authentication failures.
- Unit session-3.scope has begun starting up.
Nov 29 16:45:01 mail.davomail.com CROND[3019]: (root) CMD (env LANG=C 
/usr/bin/mrtg



/usr/share/toaster/mrtg/qmailmrtg.cfg > /dev/
Nov 29 16:45:05 mail.davomail.com vpopmail[3170]: vchkpw-smtp: vpopmail user 
not found customers@:119.235.53.75
Nov 29 16:45:14 mail.davomail.com vpopmail[3175]: vchkpw-smtp: vpopmail user 
not found postmaster@:119.235.53.75
Nov 29 16:45:15 mail.davomail.com sshd[3173]: pam_unix(sshd:auth): 
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
Nov 29 16:45:15 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:17 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:18 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:19 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:20 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:21 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:22 mail.davomail.com sshd[3173]: Received disconnect from 
116.31.116.4: 11: [preauth]
Nov 29 16:45:22 mail.davomail.com sshd[3173]: PAM 2 more authentication 
failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.
Nov 29 16:45:22 mail.davomail.com vpopmail[3180]: vchkpw-smtp: vpopmail user 
not found tomcat@:119.235.53.75
Nov 29 16:45:31 mail.davomail.com vpopmail[3184]: vchkpw-smtp: vpopmail user 
not found alex@:119.235.53.75
Nov 29 16:45:39 mail.davomail.com vpopmail[3187]: vchkpw-smtp: vpopmail user 
not found student@:119.235.53.75
Nov 29 16:45:47 mail.davomail.com vpopmail[3190]: vchkpw-smtp: vpopmail user 
not found www@:119.235.53.75
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database status OK.
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database status OK.
Nov 29 16:45:56 mail.davomail.com vpopmail[3195]: vchkpw-smtp: vpopmail user 
not found administrator@:119.235.53.75
Nov 29 16:45:




On Nov 29, 2016, at 10:45 AM, Jaime Lerner  wrote:

I was just mentioning it because David kept pointing to that as an error and 
thinking it was the issue as to why qmail wasn't working. It's definitely not 
an issue on my server. Perhaps that's how it is set up for Digital Ocean 
servers running CentOS 7...not sure. 

He can run 'systemctl status network' to see that his network service is 
running fine. (Mine shows it's using /etc/rc.d/init.d/network, and his may say 
the same)

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:59 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I'm not sure what to tell you to get network management started. It always seems to work on my boxes, vm's included. Maybe I'm taking something for granted. When I configure my network settings on clean install sometimes I leave network settings alone (dhcp), install qmailtoaster, then run qmt_host.sh. Other times I set the hostname and ipv4 ip, gateway, and dns (on fresh install) and run qmt_host.sh to change everything. I've never had a problem with network manager (something I need to investigate now). 
So the way around this (for now) is to edit the ifcfg-'device' file manually, something I hate to do. 


On 11/29/2016 8:48 AM, Jaime Lerner wrote:
Just as an FYI, if I run the command 'nmtui' on my server I get the same response 
"NetworkManager is not running".  Just in case you're thinking that's an 
issue...it's obviously not.

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:45 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

And,
What are these settings: 
IPADDR2=10.13.0.5

PREFIX2=16
If you don't need them remove.

On 11/29/2016 8:34 AM, Eric Broch wrote:
Do below and remove ifcfg-enp0s3

On 11/29/2016 8:32 AM, Eric Broch wrote:
Here's what I would do
# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0    /root/'somewhere'
# vi /etc/sysconfig/network-scripts/ifcfg-eth0
erase all settings, paste below into the file and save
# systemctl restart network
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4
# vi /etc/resolv.conf
clear all ipv6 nameserver settings
add: 
nameserver 8.8.8.8

nameserver 8.8.4.4


On 11/29/2016 7:48 AM, David Overman wrote:
Ok,
I tried th

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Is your network up and running?

Please dump squirrelmail.conf and post on list.

What log is it that you've put here? /var/log/maillog?


On 11/29/2016 9:58 AM, David Overman wrote:

sorry, forgot to post output last post; here goes


[root@mail conf]# systemctl status network
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: active (exited) since Tue 2016-11-29 16:35:44 UTC; 15min ago
Docs: man:systemd-sysv-generator(8)

also, tried restarting apache2 after modifying 
squirrellmail.conf-again. Do not see the ns error, but PAM 
authentication failures.

- Unit session-3.scope has begun starting up.
Nov 29 16:45:01 mail.davomail.com CROND[3019]: (root) CMD (env LANG=C 
/usr/bin/mrtg




/usr/share/toaster/mrtg/qmailmrtg.cfg > /dev/
Nov 29 16:45:05 mail.davomail.com vpopmail[3170]: vchkpw-smtp: 
vpopmail user not found customers@:119.235.53.75
Nov 29 16:45:14 mail.davomail.com vpopmail[3175]: vchkpw-smtp: 
vpopmail user not found postmaster@:119.235.53.75
Nov 29 16:45:15 mail.davomail.com sshd[3173]: pam_unix(sshd:auth): 
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
Nov 29 16:45:15 mail.davomail.com sshd[3173]: 
pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user 
"root"
Nov 29 16:45:17 mail.davomail.com sshd[3173]: Failed password for root 
from 116.31.116.4 port 44382 ssh2
Nov 29 16:45:18 mail.davomail.com sshd[3173]: 
pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user 
"root"
Nov 29 16:45:19 mail.davomail.com sshd[3173]: Failed password for root 
from 116.31.116.4 port 44382 ssh2
Nov 29 16:45:20 mail.davomail.com sshd[3173]: 
pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user 
"root"
Nov 29 16:45:21 mail.davomail.com sshd[3173]: Failed password for root 
from 116.31.116.4 port 44382 ssh2
Nov 29 16:45:22 mail.davomail.com sshd[3173]: Received disconnect from 
116.31.116.4: 11: [preauth]
Nov 29 16:45:22 mail.davomail.com sshd[3173]: PAM 2 more 
authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.
Nov 29 16:45:22 mail.davomail.com vpopmail[3180]: vchkpw-smtp: 
vpopmail user not found tomcat@:119.235.53.75
Nov 29 16:45:31 mail.davomail.com vpopmail[3184]: vchkpw-smtp: 
vpopmail user not found alex@:119.235.53.75
Nov 29 16:45:39 mail.davomail.com vpopmail[3187]: vchkpw-smtp: 
vpopmail user not found student@:119.235.53.75
Nov 29 16:45:47 mail.davomail.com vpopmail[3190]: vchkpw-smtp: 
vpopmail user not found www@:119.235.53.75
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database 
status OK.
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database 
status OK.
Nov 29 16:45:56 mail.davomail.com vpopmail[3195]: vchkpw-smtp: 
vpopmail user not found administrator@:119.235.53.75

Nov 29 16:45:




On Nov 29, 2016, at 10:45 AM, Jaime Lerner 
 wrote:


I was just mentioning it because David kept pointing to that as an 
error and thinking it was the issue as to why qmail wasn't working. 
It's definitely not an issue on my server. Perhaps that's how it is 
set up for Digital Ocean servers running CentOS 7...not sure.


He can run 'systemctl status network' to see that his network service 
is running fine. (Mine shows it's using /etc/rc.d/init.d/network, and 
his may say the same)


From: Eric Broch <mailto:ebr...@whitehorsetc.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Tuesday, November 29, 2016 at 10:59 AM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail conf 
new-install


I'm not sure what to tell you to get network management started. It 
always seems to work on my boxes, vm's included. Maybe I'm taking 
something for granted. When I configure my network settings on clean 
install sometimes I leave network settings alone (dhcp), install 
qmailtoaster, then run qmt_host.sh. Other times I set the hostname 
and ipv4 ip, gateway, and dns (on fresh install) and run qmt_host.sh 
to change everything. I've never had a problem with network manager 
(something I need to investigate now).


So the way around this (for now) is to edit the ifcfg-'device' file 
manually, something I hate to do.



On 11/29/2016 8:48 AM, Jaime Lerner wrote:
Just as an FYI, if I run the command 'nmtui' on my server I get the 
same response "NetworkManager is not running".  Just in case you're 
thinking that's an issue...it's obviously not.


From: Eric Broch <mailto:ebr...@whitehorsetc.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Tuesday, November 29, 2016 at 10:45 AM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail conf 
new-install


And,

What are these settings:

IPADDR2=10.13.0.5
PREFIX2=

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

sorry, forgot to post output last post; here goes


[root@mail conf]# systemctl status network
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: active (exited) since Tue 2016-11-29 16:35:44 UTC; 15min ago
Docs: man:systemd-sysv-generator(8)

also, tried restarting apache2 after modifying squirrellmail.conf-again. Do not 
see the ns error, but PAM authentication failures.
- Unit session-3.scope has begun starting up.
Nov 29 16:45:01 mail.davomail.com CROND[3019]: (root) CMD (env LANG=C 
/usr/bin/mrtg



/usr/share/toaster/mrtg/qmailmrtg.cfg > /dev/
Nov 29 16:45:05 mail.davomail.com vpopmail[3170]: vchkpw-smtp: vpopmail user 
not found customers@:119.235.53.75
Nov 29 16:45:14 mail.davomail.com vpopmail[3175]: vchkpw-smtp: vpopmail user 
not found postmaster@:119.235.53.75
Nov 29 16:45:15 mail.davomail.com sshd[3173]: pam_unix(sshd:auth): 
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
Nov 29 16:45:15 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:17 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:18 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:19 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:20 mail.davomail.com sshd[3173]: pam_succeed_if(sshd:auth): requirement "uid >= 
1000" not met by user "root"
Nov 29 16:45:21 mail.davomail.com sshd[3173]: Failed password for root from 
116.31.116.4 port 44382 ssh2
Nov 29 16:45:22 mail.davomail.com sshd[3173]: Received disconnect from 
116.31.116.4: 11: [preauth]
Nov 29 16:45:22 mail.davomail.com sshd[3173]: PAM 2 more authentication 
failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.
Nov 29 16:45:22 mail.davomail.com vpopmail[3180]: vchkpw-smtp: vpopmail user 
not found tomcat@:119.235.53.75
Nov 29 16:45:31 mail.davomail.com vpopmail[3184]: vchkpw-smtp: vpopmail user 
not found alex@:119.235.53.75
Nov 29 16:45:39 mail.davomail.com vpopmail[3187]: vchkpw-smtp: vpopmail user 
not found student@:119.235.53.75
Nov 29 16:45:47 mail.davomail.com vpopmail[3190]: vchkpw-smtp: vpopmail user 
not found www@:119.235.53.75
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database status OK.
Nov 29 16:45:55 mail.davomail.com clamd[490]: SelfCheck: Database status OK.
Nov 29 16:45:56 mail.davomail.com vpopmail[3195]: vchkpw-smtp: vpopmail user 
not found administrator@:119.235.53.75
Nov 29 16:45:




On Nov 29, 2016, at 10:45 AM, Jaime Lerner  wrote:

I was just mentioning it because David kept pointing to that as an error and 
thinking it was the issue as to why qmail wasn't working. It's definitely not 
an issue on my server. Perhaps that's how it is set up for Digital Ocean 
servers running CentOS 7...not sure. 

He can run 'systemctl status network' to see that his network service is 
running fine. (Mine shows it's using /etc/rc.d/init.d/network, and his may say 
the same)

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:59 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I'm not sure what to tell you to get network management started. It always seems to work on my boxes, vm's included. Maybe I'm taking something for granted. When I configure my network settings on clean install sometimes I leave network settings alone (dhcp), install qmailtoaster, then run qmt_host.sh. Other times I set the hostname and ipv4 ip, gateway, and dns (on fresh install) and run qmt_host.sh to change everything. I've never had a problem with network manager (something I need to investigate now). 
So the way around this (for now) is to edit the ifcfg-'device' file manually, something I hate to do. 


On 11/29/2016 8:48 AM, Jaime Lerner wrote:
Just as an FYI, if I run the command 'nmtui' on my server I get the same response 
"NetworkManager is not running".  Just in case you're thinking that's an 
issue...it's obviously not.

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:45 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

And,
What are these settings: 
IPADDR2=10.13.0.5

PREFIX2=16
If you don't need them remove.

On 11/29/2016 8:34 AM, Eric Broch wrote:
Do below and remove ifcfg-enp0s3

On 11/29/2016 8:32 AM, Eric Broch wrote:
Here's what I would do
# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0    /root/'somewhere'
# vi /etc/sysconfig/network-scripts/ifcfg-eth0
erase all settings, paste below into the file and save
# systemctl restart network
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.7

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

On Nov 29, 2016, at 10:45 AM, Jaime Lerner  wrote:

I was just mentioning it because David kept pointing to that as an error and 
thinking it was the issue as to why qmail wasn't working. It's definitely not 
an issue on my server. Perhaps that's how it is set up for Digital Ocean 
servers running CentOS 7...not sure. 

He can run 'systemctl status network' to see that his network service is 
running fine. (Mine shows it's using /etc/rc.d/init.d/network, and his may say 
the same)

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:59 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I'm not sure what to tell you to get network management started. It always seems to work on my boxes, vm's included. Maybe I'm taking something for granted. When I configure my network settings on clean install sometimes I leave network settings alone (dhcp), install qmailtoaster, then run qmt_host.sh. Other times I set the hostname and ipv4 ip, gateway, and dns (on fresh install) and run qmt_host.sh to change everything. I've never had a problem with network manager (something I need to investigate now). 
So the way around this (for now) is to edit the ifcfg-'device' file manually, something I hate to do. 


On 11/29/2016 8:48 AM, Jaime Lerner wrote:
Just as an FYI, if I run the command 'nmtui' on my server I get the same response 
"NetworkManager is not running".  Just in case you're thinking that's an 
issue...it's obviously not.

From: Eric Broch 
Reply-To: 
Date: Tuesday, November 29, 2016 at 10:45 AM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

And,
What are these settings: 
IPADDR2=10.13.0.5

PREFIX2=16
If you don't need them remove.

On 11/29/2016 8:34 AM, Eric Broch wrote:
Do below and remove ifcfg-enp0s3

On 11/29/2016 8:32 AM, Eric Broch wrote:
Here's what I would do
# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0    /root/'somewhere'
# vi /etc/sysconfig/network-scripts/ifcfg-eth0
erase all settings, paste below into the file and save
# systemctl restart network
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4
# vi /etc/resolv.conf
clear all ipv6 nameserver settings
add: 
nameserver 8.8.8.8

nameserver 8.8.4.4


On 11/29/2016 7:48 AM, David Overman wrote:
Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh
Or
Take a look here:
http://ask.xmodulo.com/configure-static-ip-address-centos7.html
You must get rid of the IPv6 name servers



On 11/29/2016 4:37 AM, David Overman wrote:
[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Jaime Lerner]

I was just mentioning it because David kept pointing to that as an error and
thinking it was the issue as to why qmail wasn't working. It's definitely
not an issue on my server. Perhaps that's how it is set up for Digital Ocean
servers running CentOS 7...not sure.

He can run 'systemctl status network' to see that his network service is
running fine. (Mine shows it's using /etc/rc.d/init.d/network, and his may
say the same)

From:  Eric Broch 
Reply-To:  
Date:  Tuesday, November 29, 2016 at 10:59 AM
To:  
Subject:  Re: [qmailtoaster] error after changing squirrelmail conf
new-install


 

I'm not sure what to tell you to get network management started. It always
seems to work on my boxes, vm's included. Maybe I'm taking something for
granted. When I configure my network settings on clean install sometimes I
leave network settings alone (dhcp), install qmailtoaster, then run
qmt_host.sh. Other times I set the hostname and ipv4 ip, gateway, and dns
(on fresh install) and run qmt_host.sh to change everything. I've never had
a problem with network manager (something I need to investigate now).
 
 

So the way around this (for now) is to edit the ifcfg-'device' file
manually, something I hate to do.
 
 
 
On 11/29/2016 8:48 AM, Jaime Lerner wrote:
 
 
>  
> Just as an FYI, if I run the command 'nmtui' on my server I get the same
> response "NetworkManager is not running".  Just in case you're thinking that's
> an issue...it's obviously not.
>  
> 
>  
>   
> From:  Eric Broch 
>  Reply-To:  
>  Date:  Tuesday, November 29, 2016 at 10:45 AM
>  To:  
>  Subject:  Re: [qmailtoaster] error after changing squirrelmail conf
> new-install
>  
>  
> 
>  
>  
>   
>  
> 
> And,
>  
> 
> What are these settings:
>  
>  
> 
> IPADDR2=10.13.0.5
>  PREFIX2=16
>  
> 
> If you don't need them remove.
>  
>  
>  
> On 11/29/2016 8:34 AM, Eric Broch wrote:
>  
>  
>>   
>> 
>> Do below and remove ifcfg-enp0s3
>>  
>>  
>> On 11/29/2016 8:32 AM, Eric Broch wrote:
>>  
>>  
>>>   
>>> 
>>> Here's what I would do
>>>  
>>> 
>>> # cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0/root/'somewhere'
>>>  
>>> 
>>> # vi /etc/sysconfig/network-scripts/ifcfg-eth0
>>>  
>>> 
>>> erase all settings, paste below into the file and save
>>>  
>>> 
>>> # systemctl restart network
>>>  
>>> 
>>> DEVICE='eth0'
>>>  TYPE=Ethernet
>>>  BOOTPROTO=none
>>>  ONBOOT='yes'
>>>  HWADDR=62:ed:ca:6d:25:73
>>>  IPADDR=162.243.70.109
>>>  NETMASK=255.255.255.0
>>>  GATEWAY=162.243.70.1
>>>  IPADDR2=10.13.0.5
>>>  PREFIX2=16
>>>  IPV6INIT=yes
>>>  IPV6_AUTOCONF=yes
>>>  IPV6_DEFROUTE="yes"
>>>  IPV6_FAILURE_FATAL="no"
>>>  IPV6_PEERDNS=yes
>>>  IPV6_PEERROUTES=yes
>>>  DNS1=8.8.8.8
>>>  DNS2=8.8.4.4
>>>  
>>> 
>>> # vi /etc/resolv.conf
>>>  
>>> 
>>> clear all ipv6 nameserver settings
>>>  
>>> 
>>> add: 
>>>  
>>>  
>>> 
>>> nameserver 8.8.8.8
>>>  
>>> 
>>> nameserver 8.8.4.4
>>>  
>>> 
>>> 
>>>  
>>>  
>>>  
>>> On 11/29/2016 7:48 AM, David Overman wrote:
>>>  
>>>  
>>>>  
>>>> Ok,
>>>>  
>>>> I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
>>>>  
>>>> and with my actual ip and hostname.
>>>>  
>>>> 
>>>>  
>>>>  
>>>> Still getting Error: NetworkManager is not running.
>>>>  
>>>> 
>>>>  
>>>>  
>>>> [root@mail ~]# sh qmt-host.sh
>>>>  
>>>>  Call this script as follows (example below):
>>>>  qmt-host.sh hostname ipv4.address ipv4.gateway
>>>>  qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1
>>>>  
>>>>  
>>>> 
>>>>  
>>>>  
>>>>  Machine ID: f4d13c7c7b144261851b451e00bb999b
>>>>  Boot ID: a73c2022069042cf8d8e58ca859c787e
>>>>  Virtualization: kvm
>>>>  Operating System: CentOS Linux 7 (Core)
>>>>  CPE OS Name: cpe:/o:centos:centos:7
>>>>  Kernel: Linux 3.10.0-327.36.3.el7.x86_64
>>>>  Archite

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

I'm not sure what to tell you to get network management started. It 
always seems to work on my boxes, vm's included. Maybe I'm taking 
something for granted. When I configure my network settings on clean 
install sometimes I leave network settings alone (dhcp), install 
qmailtoaster, then run qmt_host.sh. Other times I set the hostname and 
ipv4 ip, gateway, and dns (on fresh install) and run qmt_host.sh to 
change everything. I've never had a problem with network manager 
(something I need to investigate now).


So the way around this (for now) is to edit the ifcfg-'device' file 
manually, something I hate to do.



On 11/29/2016 8:48 AM, Jaime Lerner wrote:
Just as an FYI, if I run the command 'nmtui' on my server I get the 
same response "NetworkManager is not running".  Just in case you're 
thinking that's an issue...it's obviously not.


From: Eric Broch <mailto:ebr...@whitehorsetc.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Tuesday, November 29, 2016 at 10:45 AM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail conf 
new-install


And,

What are these settings:

IPADDR2=10.13.0.5
PREFIX2=16

If you don't need them remove.


On 11/29/2016 8:34 AM, Eric Broch wrote:


Do below and remove ifcfg-enp0s3


On 11/29/2016 8:32 AM, Eric Broch wrote:


Here's what I would do

# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0 /root/'somewhere'

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

erase all settings, paste below into the file and save

# systemctl restart network

DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4

# vi /etc/resolv.conf

clear all ipv6 nameserver settings

add:

nameserver 8.8.8.8

nameserver 8.8.4.4



On 11/29/2016 7:48 AM, David Overman wrote:

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  
wrote:


Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos 
Instance running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch 
 wrote:



# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit 
NetworkManager.service is

masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 
<mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 
<mailto:qmailtoaster-list-h...@qmailtoaster.com>

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Jaime Lerner]

Just as an FYI, if I run the command 'nmtui' on my server I get the same
response "NetworkManager is not running".  Just in case you're thinking
that's an issue...it's obviously not.

From:  Eric Broch 
Reply-To:  
Date:  Tuesday, November 29, 2016 at 10:45 AM
To:  
Subject:  Re: [qmailtoaster] error after changing squirrelmail conf
new-install


 

And,
 

What are these settings:
 
 

IPADDR2=10.13.0.5
 PREFIX2=16
 

If you don't need them remove.
 
 
 
On 11/29/2016 8:34 AM, Eric Broch wrote:
 
 
>   
> 
> Do below and remove ifcfg-enp0s3
>  
>  
> On 11/29/2016 8:32 AM, Eric Broch wrote:
>  
>  
>>   
>> 
>> Here's what I would do
>>  
>> 
>> # cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0/root/'somewhere'
>>  
>> 
>> # vi /etc/sysconfig/network-scripts/ifcfg-eth0
>>  
>> 
>> erase all settings, paste below into the file and save
>>  
>> 
>> # systemctl restart network
>>  
>> 
>> DEVICE='eth0'
>>  TYPE=Ethernet
>>  BOOTPROTO=none
>>  ONBOOT='yes'
>>  HWADDR=62:ed:ca:6d:25:73
>>  IPADDR=162.243.70.109
>>  NETMASK=255.255.255.0
>>  GATEWAY=162.243.70.1
>>  IPADDR2=10.13.0.5
>>  PREFIX2=16
>>  IPV6INIT=yes
>>  IPV6_AUTOCONF=yes
>>  IPV6_DEFROUTE="yes"
>>  IPV6_FAILURE_FATAL="no"
>>  IPV6_PEERDNS=yes
>>  IPV6_PEERROUTES=yes
>>  DNS1=8.8.8.8
>>  DNS2=8.8.4.4
>>  
>> 
>> # vi /etc/resolv.conf
>>  
>> 
>> clear all ipv6 nameserver settings
>>  
>> 
>> add: 
>>  
>>  
>> 
>> nameserver 8.8.8.8
>>  
>> 
>> nameserver 8.8.4.4
>>  
>> 
>> 
>>  
>>  
>>  
>> On 11/29/2016 7:48 AM, David Overman wrote:
>>  
>>  
>>>  
>>> Ok,
>>>  
>>> I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
>>>  
>>> and with my actual ip and hostname.
>>>  
>>> 
>>>  
>>>  
>>> Still getting Error: NetworkManager is not running.
>>>  
>>> 
>>>  
>>>  
>>> [root@mail ~]# sh qmt-host.sh
>>>  
>>>  Call this script as follows (example below):
>>>  qmt-host.sh hostname ipv4.address ipv4.gateway
>>>  qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1
>>>  
>>>  
>>> 
>>>  
>>>  
>>>  Machine ID: f4d13c7c7b144261851b451e00bb999b
>>>  Boot ID: a73c2022069042cf8d8e58ca859c787e
>>>  Virtualization: kvm
>>>  Operating System: CentOS Linux 7 (Core)
>>>  CPE OS Name: cpe:/o:centos:centos:7
>>>  Kernel: Linux 3.10.0-327.36.3.el7.x86_64
>>>  Architecture: x86-64
>>>  Error: NetworkManager is not running.
>>>  
>>>  
>>> 
>>>  
>>>  
>>> 
>>>  On Nov 29, 2016, at 08:26 AM, Eric Broch 
>>> <mailto:ebr...@whitehorsetc.com>  wrote:
>>>  
>>>  
>>>  
>>>  
>>>>  
>>>>  
>>>> 
>>>> Try running this:
>>>> https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh
>>>>  
>>>> 
>>>> Or
>>>>  
>>>>  
>>>> 
>>>> Take a look here:
>>>>  
>>>> 
>>>> http://ask.xmodulo.com/configure-static-ip-address-centos7.html
>>>>  
>>>> 
>>>> You must get rid of the IPv6 name servers
>>>>  
>>>> 
>>>> 
>>>>  
>>>>  
>>>> 
>>>> 
>>>>  
>>>>  
>>>>  
>>>> On 11/29/2016 4:37 AM, David Overman wrote:
>>>>  
>>>>  
>>>>>  
>>>>> [root@mail ~]# systemctl start network
>>>>>  [root@mail ~]# nmtui
>>>>>  NetworkManager is not running.
>>>>>  
>>>>> 
>>>>>  
>>>>>  
>>>>> 
>>>>>  
>>>>>  
>>>>> Do you think this may have something to do with my Centos Instance running
>>>>> on A digitalocean droplet?
>>>>>  
>>>>> 
>>>>>  On Nov 28, 2016, at 07:37 AM, Eric Broch 
>>>>> <mailto:ebr...@whitehorsetc.com>  wrote:
>>>>>  
>>>>>  
>>>>>  
>>>>>  
>>>>>>  
>>>>>>  
>>>>>> # systemctl start network
>>>>>>  
>>>>>>  
>>>>>>  On 11/28/2016 12:16 AM, David Overman wrote:
>>>>>>  
>>>>>>> Failed to start NetworkManager.service: Unit NetworkManager.service is
>>>>>>  
>>>>>>> masked
>>>>>>  
>>>>>>  
>>>>>> -
>>>>>>  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>>>>>>  For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>>>>>  
>>>>>>  
>>>>>>  
>>>>>>  
>>>>>  
>>>>>  
>>>>  
>>>>  
>>>>  
>>>  
>>>  
>>  
>>  
>  
>  
 
 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

And,

What are these settings:

IPADDR2=10.13.0.5
PREFIX2=16

If you don't need them remove.


On 11/29/2016 8:34 AM, Eric Broch wrote:


Do below and remove ifcfg-enp0s3


On 11/29/2016 8:32 AM, Eric Broch wrote:


Here's what I would do

# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0 /root/'somewhere'

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

erase all settings, paste below into the file and save

# systemctl restart network

DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4

# vi /etc/resolv.conf

clear all ipv6 nameserver settings

add:

nameserver 8.8.8.8

nameserver 8.8.4.4



On 11/29/2016 7:48 AM, David Overman wrote:

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  
wrote:


Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance 
running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch  
wrote:



# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit 
NetworkManager.service is

masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Do below and remove ifcfg-enp0s3


On 11/29/2016 8:32 AM, Eric Broch wrote:


Here's what I would do

# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0 /root/'somewhere'

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

erase all settings, paste below into the file and save

# systemctl restart network

DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4

# vi /etc/resolv.conf

clear all ipv6 nameserver settings

add:

nameserver 8.8.8.8

nameserver 8.8.4.4



On 11/29/2016 7:48 AM, David Overman wrote:

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance 
running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch  
wrote:



# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit 
NetworkManager.service is

masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Here's what I would do

# cp -p  /etc/sysconfig/network-scripts/ifcfg-eth0 /root/'somewhere'

# vi /etc/sysconfig/network-scripts/ifcfg-eth0

erase all settings, paste below into the file and save

# systemctl restart network

DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
DNS1=8.8.8.8
DNS2=8.8.4.4

# vi /etc/resolv.conf

clear all ipv6 nameserver settings

add:

nameserver 8.8.8.8

nameserver 8.8.4.4



On 11/29/2016 7:48 AM, David Overman wrote:

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance 
running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch  
wrote:



# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:

Failed to start NetworkManager.service: Unit NetworkManager.service is
masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

I created the file ifcfg-enp0s3, as it was not in /etc/sysconfig/network-scripts
HWADDR="08:00:27:F3:D4:74"
TYPE="Ethernet"
BOOTPROTO="static"
IPADDR=192.168.0.17
NETMASK=255.255.255.0
NM_CONTROLLED=no
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
NAME="enp0s3"
UUID="63a1bb2b-fe58-4724-84ae-28ec671b083e"
ONBOOT="yes"

Saved the file and rebooted.
upon reboot-this came up 
Warning: NetworkManager.service changed on disk. Run 'systemctl daemon-reload' 
to reload units.

[root@mail ~]# systemctl daemon-reload
[root@mail ~]# nmtui
NetworkManager is not running.

ran the script again, but I am not sure what to put for ip4.gateway? tried 
8.8.8.8
still getting "Networkmanager is not running".

On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh
Or
Take a look here:
http://ask.xmodulo.com/configure-static-ip-address-centos7.html
You must get rid of the IPv6 name servers



On 11/29/2016 4:37 AM, David Overman wrote:
[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh
Or
Take a look here:
http://ask.xmodulo.com/configure-static-ip-address-centos7.html
You must get rid of the IPv6 name servers



On 11/29/2016 4:37 AM, David Overman wrote:
[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Then you'll have to do it manually. You do not need the ipv6 addresses. 
Take a look at the site I sent.



On 11/29/2016 7:48 AM, David Overman wrote:

Ok,
I tried the script with my ip for ip4 address and 8.8.8.8 and 8.8.4.4
and with my actual ip and hostname.

Still getting Error: NetworkManager is not running.

[root@mail ~]# sh qmt-host.sh

Call this script as follows (example below):
qmt-host.sh hostname ipv4.address ipv4.gateway
qmt-host.sh me.mydomain.com 192.168.0.2 192.168.0.1

Machine ID: f4d13c7c7b144261851b451e00bb999b
Boot ID: a73c2022069042cf8d8e58ca859c787e
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-327.36.3.el7.x86_64
Architecture: x86-64
Error: NetworkManager is not running.


On Nov 29, 2016, at 08:26 AM, Eric Broch  wrote:

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance 
running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch  
wrote:



# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:

Failed to start NetworkManager.service: Unit NetworkManager.service is
masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Try running this: 
https://raw.githubusercontent.com/qmtoaster/scripts/master/qmt_host.sh


Or

Take a look here:

http://ask.xmodulo.com/configure-static-ip-address-centos7.html

You must get rid of the IPv6 name servers




On 11/29/2016 4:37 AM, David Overman wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance 
running on A digitalocean droplet?


On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:


# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:

Failed to start NetworkManager.service: Unit NetworkManager.service is
masked



-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com 

For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

Jamie,
I already have this installed(Centos 7.2). Maybe I should look at Roundcube, and forget 
about squirrelmail and the errors that are being generated by apache regarding, 
"unknown nameserver"?

David

On Nov 29, 2016, at 08:18 AM, Jaime Lerner  wrote:


No, Eric's instructions are generic. I'll take a look at my notes, and see if I 
can help you any to get going on this on a digital ocean droplet.

On Nov 29, 2016, at 9:03 AM, David Overman  wrote:

Fantastic Jaime,
Thank You!,

I just opened a ticket on DO. I'll close it now. Does Eric have specific 
instructions for DO?
googling now.

David

On Nov 29, 2016, at 07:57 AM, Jaime Lerner  wrote:


I'm running my install on a digital ocean droplet on Cent OS 7.2 with no 
problems at all. It runs beautifully there. I found Eric's instructions by 
Googling and followed them for the install and everything worked great. I'm 
running roundcube and not squirrelmail, but qmail itself was up and running 
with no problems from Eric's step-by-step. I'm running Apache (for the 
webmail), and Bind for DNS.

On Nov 29, 2016, at 6:37 AM, David Overman  wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Jaime Lerner]

No, Eric's instructions are generic. I'll take a look at my notes, and see if I 
can help you any to get going on this on a digital ocean droplet.

> On Nov 29, 2016, at 9:03 AM, David Overman  wrote:
> 
> Fantastic Jaime,
> Thank You!,
> 
> I just opened a ticket on DO. I'll close it now. Does Eric have specific 
> instructions for DO?
> googling now.
> 
> David
> 
>> On Nov 29, 2016, at 07:57 AM, Jaime Lerner  
>> wrote:
>> 
> 
>> 
>> I'm running my install on a digital ocean droplet on Cent OS 7.2 with no 
>> problems at all. It runs beautifully there. I found Eric's instructions by 
>> Googling and followed them for the install and everything worked great. I'm 
>> running roundcube and not squirrelmail, but qmail itself was up and running 
>> with no problems from Eric's step-by-step. I'm running Apache (for the 
>> webmail), and Bind for DNS.
>> 
>>> On Nov 29, 2016, at 6:37 AM, David Overman  wrote:
>>> 
>>> [root@mail ~]# systemctl start network
>>> [root@mail ~]# nmtui
>>> NetworkManager is not running.
>>> 
>>> 
>>> Do you think this may have something to do with my Centos Instance running 
>>> on A digitalocean droplet?
>>> 
 On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:
 
>>> 
 # systemctl start network
 
 
> On 11/28/2016 12:16 AM, David Overman wrote:
> Failed to start NetworkManager.service: Unit NetworkManager.service is
> masked
 
 
 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

Fantastic Jaime,
Thank You!,

I just opened a ticket on DO. I'll close it now. Does Eric have specific 
instructions for DO?
googling now.

David

On Nov 29, 2016, at 07:57 AM, Jaime Lerner  wrote:


I'm running my install on a digital ocean droplet on Cent OS 7.2 with no 
problems at all. It runs beautifully there. I found Eric's instructions by 
Googling and followed them for the install and everything worked great. I'm 
running roundcube and not squirrelmail, but qmail itself was up and running 
with no problems from Eric's step-by-step. I'm running Apache (for the 
webmail), and Bind for DNS.

On Nov 29, 2016, at 6:37 AM, David Overman  wrote:

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Jaime Lerner]

I'm running my install on a digital ocean droplet on Cent OS 7.2 with no 
problems at all. It runs beautifully there. I found Eric's instructions by 
Googling and followed them for the install and everything worked great. I'm 
running roundcube and not squirrelmail, but qmail itself was up and running 
with no problems from Eric's step-by-step. I'm running Apache (for the 
webmail), and Bind for DNS.

> On Nov 29, 2016, at 6:37 AM, David Overman  wrote:
> 
> [root@mail ~]# systemctl start network
> [root@mail ~]# nmtui
> NetworkManager is not running.
> 
> 
> Do you think this may have something to do with my Centos Instance running on 
> A digitalocean droplet?
> 
>> On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:
>> 
> 
>> # systemctl start network
>> 
>> 
>>> On 11/28/2016 12:16 AM, David Overman wrote:
>>> Failed to start NetworkManager.service: Unit NetworkManager.service is
>>> masked
>> 
>> 
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>> 

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

[root@mail ~]# systemctl start network
[root@mail ~]# nmtui
NetworkManager is not running.


Do you think this may have something to do with my Centos Instance running on A 
digitalocean droplet?

On Nov 28, 2016, at 07:37 AM, Eric Broch  wrote:

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

# systemctl start network


On 11/28/2016 12:16 AM, David Overman wrote:
Failed to start NetworkManager.service: Unit NetworkManager.service is 
masked



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

nmtui
NetworkManager is not running.
[root@mail ~]# service NetworkManager start
Redirecting to /bin/systemctl start NetworkManager.service
Failed to start NetworkManager.service: Unit NetworkManager.service is masked.

On Nov 28, 2016, at 12:40 AM, Eric Broch  wrote:

I'd run nmtui
# nmtui
and put IPv6 on automatic and add 8.8.4.4 to my IPv4 dns settings. Then restart 
the network.
check if the new dns settings went into /etc/resolv.conf:
nameserver 8.8.8.8
nameserver 8.8.4.4



On 11/27/2016 11:10 PM, David Overman wrote:
cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8
[root@mail network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8


root@mail network-scripts]# cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::


On Nov 28, 2016, at 12:01 AM, Eric Broch  wrote:

Now dump your  /etc/sysconfig/network-scripts/ifcfg-eth0 file?
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
and 
# cat /etc/resolv.conf

and post them to the list.
I don't think these issues with DNS that you're experiencing have anything to 
do with qmail.
We'll get to the spamassassin issue later.

On 11/27/2016 9:30 PM, David Overman wrote:

eth0: flags=4163 mtu 1500
inet 162.243.70.109 netmask 255.255.255.0 broadcast 162.243.70.255
inet6 2604:a880:0:1010::12d2:f001 prefixlen 64 scopeid 0x0
inet6 fe80::60ed:caff:fe6d:2573 prefixlen 64 scopeid 0x20
ether 62:ed:ca:6d:25:73 txqueuelen 1000 (Ethernet)
RX packets 275111 bytes 377153866 (359.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119044 bytes 10979851 (10.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1898 bytes 203728 (198.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1898 bytes 203728 (198.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Nov 27, 2016, at 06:48 PM, Eric Broch  wrote:

At the command line type
# ifconfig 
or 
# ip addr 
and post your output



On 11/27/2016 5:26 PM, David Overman wrote:
Thanks,
It is 7.2 I made the changes, but this did not resolve the error. 
I'm not sure how to configure
spamassassin
and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping whole os 
clean.

David 

On Nov 27, 2016, at 05:27 PM, Eric Broch  wrote:

can you change /etc/resolv.conf to what Jamie posted, do the spamassassin 
config change and restart httpd? Also, on CentOS 7, not sure about 6, merely 
changing resolv.conf will not keep nameserver changes on restart. They have to 
be made in the /etc/sysconfig/network-scripts/ifcfg-your-active-interface.

On 11/27/2016 3:01 PM, David Overman wrote:
cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner  wrote:

Looks to me like he has an ipv6 version of the Google IPs in his resolve.conf 
file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf 
search [whatever his mailserver is, i.e. mail.example.com]
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

From: David Overman 
Reply-To: 
Date: Sunday, November 27, 2016 at 3:05 PM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

I'd run nmtui

# nmtui

and put IPv6 on automatic and add 8.8.4.4 to my IPv4 dns settings. Then 
restart the network.


check if the new dns settings went into /etc/resolv.conf:

nameserver 8.8.8.8

nameserver 8.8.4.4




On 11/27/2016 11:10 PM, David Overman wrote:

cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8
[root@mail network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8


root@mail network-scripts]# cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::


On Nov 28, 2016, at 12:01 AM, Eric Broch  wrote:


Now dump your  /etc/sysconfig/network-scripts/ifcfg-eth0 file?

# cat /etc/sysconfig/network-scripts/ifcfg-eth0

and

# cat /etc/resolv.conf

and post them to the list.

I don't think these issues with DNS that you're experiencing have 
anything to do with qmail.


We'll get to the spamassassin issue later.


On 11/27/2016 9:30 PM, David Overman wrote:


eth0: flags=4163 mtu 1500
inet 162.243.70.109 netmask 255.255.255.0 broadcast 162.243.70.255
inet6 2604:a880:0:1010::12d2:f001 prefixlen 64 scopeid 0x0
inet6 fe80::60ed:caff:fe6d:2573 prefixlen 64 scopeid 0x20
ether 62:ed:ca:6d:25:73 txqueuelen 1000 (Ethernet)
RX packets 275111 bytes 377153866 (359.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119044 bytes 10979851 (10.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1898 bytes 203728 (198.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1898 bytes 203728 (198.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Nov 27, 2016, at 06:48 PM, Eric Broch  
wrote:



At the command line type

# ifconfig

or

# ip addr

and post your output



On 11/27/2016 5:26 PM, David Overman wrote:

Thanks,
It is 7.2 I made the changes, but this did not resolve the error.
I'm not sure how to configure


spamassassin


and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after 
wiping whole os clean.


David

On Nov 27, 2016, at 05:27 PM, Eric Broch  
wrote:


can you change /etc/resolv.conf to what Jamie posted, do the 
spamassassin config change and restart httpd? Also, on CentOS 7, 
not sure about 6, merely changing resolv.conf will not keep 
nameserver changes on restart. They have to be made in the 
/etc/sysconfig/network-scripts/ifcfg-your-active-interface.



On 11/27/2016 3:01 PM, David Overman wrote:

cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner 
 wrote:


Looks to me like he has an ipv6 version of the Google IPs in 
his resolve.conf file...


I think that's why he got the "unparsable nameserver" error 
originally


He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf

search [whatever his mailserver is, i.e. mail.example.com]

nameserver 127.0.0.1

nameserver 8.8.8.8

nameserver 8.8.4.4


From: David Overman mailto:davesp...@me.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Sunday, November 27, 2016 at 3:05 PM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail 
conf new-install


I found this in the archive, and I made the changes to 
squirrelmail like it said.

Now I am getting a different error.
AH00526: Syntax error on line 8 of 
/etc/httpd/conf/squirrelmail.conf:

ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
mailto:c...@yother.com>>
To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration.
Replace this in your squirrelmail.conf file.


Options None
Order allow,deny
allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8
[root@mail network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE='eth0'
TYPE=Ethernet
BOOTPROTO=none
ONBOOT='yes'
HWADDR=62:ed:ca:6d:25:73
IPADDR=162.243.70.109
NETMASK=255.255.255.0
GATEWAY=162.243.70.1
NM_CONTROLLED='yes'
IPADDR2=10.13.0.5
PREFIX2=16
IPV6INIT=yes
IPV6ADDR=2604:A880::1010:::12D2:F001/64
IPV6_DEFAULTGW=2604:A880::1010::::0001
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::
DNS3=8.8.8.8


root@mail network-scripts]# cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::


On Nov 28, 2016, at 12:01 AM, Eric Broch  wrote:

Now dump your  /etc/sysconfig/network-scripts/ifcfg-eth0 file?
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
and 
# cat /etc/resolv.conf

and post them to the list.
I don't think these issues with DNS that you're experiencing have anything to 
do with qmail.
We'll get to the spamassassin issue later.

On 11/27/2016 9:30 PM, David Overman wrote:

eth0: flags=4163 mtu 1500
inet 162.243.70.109 netmask 255.255.255.0 broadcast 162.243.70.255
inet6 2604:a880:0:1010::12d2:f001 prefixlen 64 scopeid 0x0
inet6 fe80::60ed:caff:fe6d:2573 prefixlen 64 scopeid 0x20
ether 62:ed:ca:6d:25:73 txqueuelen 1000 (Ethernet)
RX packets 275111 bytes 377153866 (359.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119044 bytes 10979851 (10.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1898 bytes 203728 (198.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1898 bytes 203728 (198.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Nov 27, 2016, at 06:48 PM, Eric Broch  wrote:

At the command line type
# ifconfig 
or 
# ip addr 
and post your output



On 11/27/2016 5:26 PM, David Overman wrote:
Thanks,
It is 7.2 I made the changes, but this did not resolve the error. 
I'm not sure how to configure
spamassassin
and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping whole os 
clean.

David 

On Nov 27, 2016, at 05:27 PM, Eric Broch  wrote:

can you change /etc/resolv.conf to what Jamie posted, do the spamassassin 
config change and restart httpd? Also, on CentOS 7, not sure about 6, merely 
changing resolv.conf will not keep nameserver changes on restart. They have to 
be made in the /etc/sysconfig/network-scripts/ifcfg-your-active-interface.

On 11/27/2016 3:01 PM, David Overman wrote:
cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner  wrote:

Looks to me like he has an ipv6 version of the Google IPs in his resolve.conf 
file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf 
search [whatever his mailserver is, i.e. mail.example.com]
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

From: David Overman 
Reply-To: 
Date: Sunday, November 27, 2016 at 3:05 PM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";;


You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:



What changes did you make to what File? Or, what documentation were you 
following?




On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:

Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I tried to 
restart http

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

Now dump your  /etc/sysconfig/network-scripts/ifcfg-eth0 file?

# cat /etc/sysconfig/network-scripts/ifcfg-eth0

and

# cat /etc/resolv.conf

and post them to the list.

I don't think these issues with DNS that you're experiencing have 
anything to do with qmail.


We'll get to the spamassassin issue later.


On 11/27/2016 9:30 PM, David Overman wrote:


eth0: flags=4163 mtu 1500
inet 162.243.70.109 netmask 255.255.255.0 broadcast 162.243.70.255
inet6 2604:a880:0:1010::12d2:f001 prefixlen 64 scopeid 0x0
inet6 fe80::60ed:caff:fe6d:2573 prefixlen 64 scopeid 0x20
ether 62:ed:ca:6d:25:73 txqueuelen 1000 (Ethernet)
RX packets 275111 bytes 377153866 (359.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119044 bytes 10979851 (10.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1898 bytes 203728 (198.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1898 bytes 203728 (198.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Nov 27, 2016, at 06:48 PM, Eric Broch  wrote:


At the command line type

# ifconfig

or

# ip addr

and post your output



On 11/27/2016 5:26 PM, David Overman wrote:

Thanks,
It is 7.2 I made the changes, but this did not resolve the error.
I'm not sure how to configure


spamassassin


and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping 
whole os clean.


David

On Nov 27, 2016, at 05:27 PM, Eric Broch  
wrote:


can you change /etc/resolv.conf to what Jamie posted, do the 
spamassassin config change and restart httpd? Also, on CentOS 7, 
not sure about 6, merely changing resolv.conf will not keep 
nameserver changes on restart. They have to be made in the 
/etc/sysconfig/network-scripts/ifcfg-your-active-interface.



On 11/27/2016 3:01 PM, David Overman wrote:

cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner 
 wrote:


Looks to me like he has an ipv6 version of the Google IPs in his 
resolve.conf file...


I think that's why he got the "unparsable nameserver" error 
originally


He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf

search [whatever his mailserver is, i.e. mail.example.com]

nameserver 127.0.0.1

nameserver 8.8.8.8

nameserver 8.8.4.4


From: David Overman mailto:davesp...@me.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Sunday, November 27, 2016 at 3:05 PM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail 
conf new-install


I found this in the archive, and I made the changes to 
squirrelmail like it said.

Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
mailto:c...@yother.com>>
To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration.
Replace this in your squirrelmail.conf file.


Options None
Order allow,deny
allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$https://%{SERVER_NAME}$1 
<https://%25%7Bserver_name%7D%241/>  [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";
<https://your.server.com/webmail/%22>;


You will need to change the your.server.com to your server name.


On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com 
<mailto:ebr...@whitehorsetc.com> wrote:




What changes did you make to what File? Or, what documentation 
were you following?





On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman" 
mailto:davesp...@me.com>> wrote:


Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but
when I tried to restart httpd, I received these errors.

Unregistered Authentication Agent for
unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]:
vchkpw-smtp: vpopmail user not found em...@mydomain.com
<mailto:em...@mydomain.com>:80.82.64.109
After changing back to the default conf for squirrelmail,
httpd restarted without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

eth0: flags=4163 mtu 1500
inet 162.243.70.109 netmask 255.255.255.0 broadcast 162.243.70.255
inet6 2604:a880:0:1010::12d2:f001 prefixlen 64 scopeid 0x0
inet6 fe80::60ed:caff:fe6d:2573 prefixlen 64 scopeid 0x20
ether 62:ed:ca:6d:25:73 txqueuelen 1000 (Ethernet)
RX packets 275111 bytes 377153866 (359.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119044 bytes 10979851 (10.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 1898 bytes 203728 (198.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1898 bytes 203728 (198.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Nov 27, 2016, at 06:48 PM, Eric Broch  wrote:

At the command line type
# ifconfig 
or 
# ip addr 
and post your output



On 11/27/2016 5:26 PM, David Overman wrote:
Thanks,
It is 7.2 I made the changes, but this did not resolve the error. 
I'm not sure how to configure
spamassassin
and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping whole os 
clean.

David 

On Nov 27, 2016, at 05:27 PM, Eric Broch  wrote:

can you change /etc/resolv.conf to what Jamie posted, do the spamassassin 
config change and restart httpd? Also, on CentOS 7, not sure about 6, merely 
changing resolv.conf will not keep nameserver changes on restart. They have to 
be made in the /etc/sysconfig/network-scripts/ifcfg-your-active-interface.

On 11/27/2016 3:01 PM, David Overman wrote:
cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner  wrote:

Looks to me like he has an ipv6 version of the Google IPs in his resolve.conf 
file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf 
search [whatever his mailserver is, i.e. mail.example.com]
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

From: David Overman 
Reply-To: 
Date: Sunday, November 27, 2016 at 3:05 PM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";;


You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:



What changes did you make to what File? Or, what documentation were you 
following?




On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:

Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I tried to 
restart httpd, I received these errors.

Unregistered Authentication Agent for unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user 
not found em...@mydomain.com:80.82.64.109
After changing back to the default conf for squirrelmail, httpd restarted 
without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

At the command line type

# ifconfig

or

# ip addr

and post your output



On 11/27/2016 5:26 PM, David Overman wrote:

Thanks,
It is 7.2 I made the changes, but this did not resolve the error.
I'm not sure how to configure


spamassassin


and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping 
whole os clean.


David

On Nov 27, 2016, at 05:27 PM, Eric Broch  wrote:

can you change /etc/resolv.conf to what Jamie posted, do the 
spamassassin config change and restart httpd? Also, on CentOS 7, not 
sure about 6, merely changing resolv.conf will not keep nameserver 
changes on restart. They have to be made in the 
/etc/sysconfig/network-scripts/ifcfg-your-active-interface.



On 11/27/2016 3:01 PM, David Overman wrote:

cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner 
 wrote:


Looks to me like he has an ipv6 version of the Google IPs in his 
resolve.conf file...


I think that's why he got the "unparsable nameserver" error 
originally


He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf

search [whatever his mailserver is, i.e. mail.example.com]

nameserver 127.0.0.1

nameserver 8.8.8.8

nameserver 8.8.4.4


From: David Overman mailto:davesp...@me.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Sunday, November 27, 2016 at 3:05 PM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail conf 
new-install


I found this in the archive, and I made the changes to squirrelmail 
like it said.

Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" <mailto:c...@yother.com>>
To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace
this in your squirrelmail.conf file.


Options None
Order allow,deny
allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$https://%{SERVER_NAME}$1 
<https://%25%7Bserver_name%7D%241/>  [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";
<https://your.server.com/webmail/%22>;


You will need to change the your.server.com to your server name.


On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com 
<mailto:ebr...@whitehorsetc.com> wrote:




What changes did you make to what File? Or, what documentation 
were you following?





On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman" 
mailto:davesp...@me.com>> wrote:


Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when
I tried to restart httpd, I received these errors.

Unregistered Authentication Agent for
unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp:
vpopmail user not found em...@mydomain.com
<mailto:em...@mydomain.com>:80.82.64.109
After changing back to the default conf for squirrelmail,
httpd restarted without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

Thanks,
It is 7.2 I made the changes, but this did not resolve the error. 
I'm not sure how to configure
spamassassin
and which interface, usually for Centos 7.2?
Sorry, I am a newby at qmail. I have reinstalled twice, after wiping whole os 
clean.

David 

On Nov 27, 2016, at 05:27 PM, Eric Broch  wrote:

can you change /etc/resolv.conf to what Jamie posted, do the spamassassin 
config change and restart httpd? Also, on CentOS 7, not sure about 6, merely 
changing resolv.conf will not keep nameserver changes on restart. They have to 
be made in the /etc/sysconfig/network-scripts/ifcfg-your-active-interface.

On 11/27/2016 3:01 PM, David Overman wrote:
cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner  wrote:

Looks to me like he has an ipv6 version of the Google IPs in his resolve.conf 
file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf 
search [whatever his mailserver is, i.e. mail.example.com]
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

From: David Overman 
Reply-To: 
Date: Sunday, November 27, 2016 at 3:05 PM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";;


You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:



What changes did you make to what File? Or, what documentation were you 
following?




On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:

Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I tried to 
restart httpd, I received these errors.

Unregistered Authentication Agent for unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user 
not found em...@mydomain.com:80.82.64.109
After changing back to the default conf for squirrelmail, httpd restarted 
without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Eric Broch]

can you change /etc/resolv.conf to what Jamie posted, do the 
spamassassin config change and restart httpd? Also, on CentOS 7, not 
sure about 6, merely changing resolv.conf will not keep nameserver 
changes on restart. They have to be made in the 
/etc/sysconfig/network-scripts/ifcfg-your-active-interface.



On 11/27/2016 3:01 PM, David Overman wrote:

cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner 
 wrote:


Looks to me like he has an ipv6 version of the Google IPs in his 
resolve.conf file...


I think that's why he got the "unparsable nameserver" error 
originally


He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf

search [whatever his mailserver is, i.e. mail.example.com]

nameserver 127.0.0.1

nameserver 8.8.8.8

nameserver 8.8.4.4


From: David Overman mailto:davesp...@me.com>>
Reply-To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Date: Sunday, November 27, 2016 at 3:05 PM
To: <mailto:qmailtoaster-list@qmailtoaster.com>>
Subject: Re: [qmailtoaster] error after changing squirrelmail conf 
new-install


I found this in the archive, and I made the changes to squirrelmail 
like it said.

Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" <mailto:c...@yother.com>>
To: <mailto:qmailtoaster-list@qmailtoaster.com>>

Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace
this in your squirrelmail.conf file.


Options None
Order allow,deny
allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$https://%{SERVER_NAME}$1 
<https://%25%7Bserver_name%7D%241/>  [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";
<https://your.server.com/webmail/%22>;


You will need to change the your.server.com to your server name.


On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com 
<mailto:ebr...@whitehorsetc.com> wrote:




What changes did you make to what File? Or, what documentation were 
you following?





On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman" 
mailto:davesp...@me.com>> wrote:


Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I
tried to restart httpd, I received these errors.

Unregistered Authentication Agent for unix-process:12902:1473656
(system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR:
invalid/unparsable nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp:
vpopmail user not found em...@mydomain.com
<mailto:em...@mydomain.com>:80.82.64.109
After changing back to the default conf for squirrelmail, httpd
restarted without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

cat /etc/resolv.conf
nameserver 2001:4860:4860::8844
nameserver 2001:4860:4860::

On Nov 27, 2016, at 02:13 PM, Jaime Lerner  wrote:

Looks to me like he has an ipv6 version of the Google IPs in his resolve.conf 
file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf 
search [whatever his mailserver is, i.e. mail.example.com]
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

From: David Overman 
Reply-To: 
Date: Sunday, November 27, 2016 at 3:05 PM
To: 
Subject: Re: [qmailtoaster] error after changing squirrelmail conf new-install

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";;


You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:



What changes did you make to what File? Or, what documentation were you 
following?




On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:

Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I tried to 
restart httpd, I received these errors.

Unregistered Authentication Agent for unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user 
not found em...@mydomain.com:80.82.64.109
After changing back to the default conf for squirrelmail, httpd restarted 
without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[Jaime Lerner]

Looks to me like he has an ipv6 version of the Google IPs in his
resolve.conf file...

I think that's why he got the "unparsable nameserver" error originally

He should change the IPs to ipv4

[root@mail ~]# cat /etc/resolv.conf

search [whatever his mailserver is, i.e. mail.example.com]

nameserver 127.0.0.1

nameserver 8.8.8.8

nameserver 8.8.4.4


From:  David Overman 
Reply-To:  
Date:  Sunday, November 27, 2016 at 3:05 PM
To:  
Subject:  Re: [qmailtoaster] error after changing squirrelmail conf
new-install

I found this in the archive, and I made the changes to squirrelmail like it
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
 ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


> It appears as though you have a default configuration. Replace this in your
> squirrelmail.conf file.
> 
>Options None
>Order allow,deny
>allow from all
> 
> 
> with this
> 
> 
> RewriteEngine on
> RewriteCond %{SERVER_PORT} !^443$
> RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1
> <https://%25%7Bserver_name%7D%241/>  [L,R]
> allow from all
> Options
> SSLRequireSSL
> ErrorDocument 403 "https://your.server.com/webmail/";
> <https://your.server.com/webmail/%22> ;
> 
> 
> You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:

> 
> 
> What changes did you make to what File? Or, what documentation were you
> following?
> 
> 
> 
> On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman" 
> wrote:
>  
>> Greetings,
>> I just got this server up Centos 6.2
>> I updated squirrelmail.conf to activate squirellmail, but when I tried to
>> restart httpd, I received these errors.
>> 
>> Unregistered Authentication Agent for unix-process:12902:1473656 (system bus
>> nam
>> Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable
>> nameserver found: 2001:4860:4860::8844
>> Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable
>> nameserver found: 2001:4860:4860::
>> Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user
>> not found em...@mydomain.com:80.82.64.109
>> After changing back to the default conf for squirrelmail, httpd restarted
>> without complaint.
>> 
>> thanks in advance,
>> David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[David Overman]

I found this in the archive, and I made the changes to squirrelmail like it 
said.
Now I am getting a different error.
AH00526: Syntax error on line 8 of /etc/httpd/conf/squirrelmail.conf:
ErrorDocument takes two arguments, Change responses for HTTP errors


- Original Message - From: "Maxwell Smart" 
To: 
Sent: Thursday, June 03, 2010 12:46 PM
Subject: Re: [qmailtoaster] Re: Webmail SSL


It appears as though you have a default configuration. Replace this in your 
squirrelmail.conf file.

  Options None
  Order allow,deny
  allow from all


with this


RewriteEngine on
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*/webmail*)$ https://%{SERVER_NAME}$1 [L,R]
allow from all
Options
SSLRequireSSL
ErrorDocument 403 "https://your.server.com/webmail/";;


You will need to change the your.server.com to your server name.

On Nov 27, 2016, at 01:55 PM, ebr...@whitehorsetc.com wrote:



What changes did you make to what File? Or, what documentation were you 
following?




On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:

Greetings,
I just got this server up Centos 6.2
I updated squirrelmail.conf to activate squirellmail, but when I tried to 
restart httpd, I received these errors.

Unregistered Authentication Agent for unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user 
not found em...@mydomain.com:80.82.64.109
After changing back to the default conf for squirrelmail, httpd restarted 
without complaint.

thanks in advance,
David

Re: [qmailtoaster] error after changing squirrelmail conf new-install

[ebroch]

What changes did you make to what File? Or, what documentation were you 
following?






On Sun, Nov 27, 2016 at 11:05 AM -0700, "David Overman"  
wrote:










Greetings,I just got this server up Centos 6.2I updated squirrelmail.conf to 
activate squirellmail, but when I tried to restart httpd, I received these 
errors.
Unregistered Authentication Agent for unix-process:12902:1473656 (system bus nam
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::8844
Nov 27 17:32:36 mail.mydomain.com spamdyke[12929]: ERROR: invalid/unparsable 
nameserver found: 2001:4860:4860::
Nov 27 17:32:37 mail.mydomaincom vpopmail[12933]: vchkpw-smtp: vpopmail user 
not found em...@mydomain.com:80.82.64.109
After changing back to the default conf for squirrelmail, httpd restarted 
without complaint.
thanks in advance,David

Re: [qmailtoaster] error while installing dovecot-2.2.25-12.qt.src.rpm

[Eric Broch]

Rajesh,

This is good to know. What was the old version of ssl you had installed, 
I'll put a minimum version of ssl in the spec file.


Eric

On 11/5/2016 10:05 PM, Rajesh M wrote:

eric

this got resolved after i updated openssl.

thanks
rajesh

- Original Message -
From: Rajesh M [mailto:24x7ser...@24x7server.net]
To: qmailtoaster-list@qmailtoaster.com
Sent: Sun, 6 Nov 2016 08:45:36 +0530
Subject:

hi eric

i am getting an error while installing the latest version dovecot
i am receiving the same error on 3 of my servers

this is what i am doing
wget 
ftp://ftp.whitehorsetc.com/pub/qmail/CentOS6/qmt/srpms/updates/dovecot-2.2.25-12.qt.src.rpm
rpmbuild --rebuild --define "dist .qt.el6"  dovecot-2.2.25-12.qt.src.rpm

during make i get the error

make  check-am
make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
Making check in lib-settings
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-settings'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-settings'
Making check in lib-auth
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-auth'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-auth'
Making check in lib-master
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-master'
for bin in test-master-service-settings-cache; do \
 if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
   done
0 / 0 tests failed
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-master'
Making check in lib-charset
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-charset'
for bin in test-charset; do \
 if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
   done
charset_is_utf8 .. : ok
charset utf8 . : ok
charset iconv  : ok
charset iconv crashes  : ok
charset iconv utf7 state . : ok
0 / 5 tests failed
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-charset'
Making check in lib-ssl-iostream
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-ssl-iostream'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-ssl-iostream'
Making check in lib-dcrypt
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt'
for bin in test-crypto test-stream; do \
 if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
   done
test_cipher_test_vectors . : ok
test_cipher_aead_test_vectors  : ok
test_hmac_test_vectors ... : ok
test-crypto.c:269: Assert failed: ret == TRUE
test-crypto.c:270: Assert failed: error == NULL
Panic: file dcrypt-openssl.c: line 880 
(dcrypt_openssl_load_private_key_dovecot_v1): assertion failed: (dec_key != 
NULL)
test: random seed #2 was 1478388283
Error: Raw backtrace: ./test-crypto() [0x412e7a] -> ./test-crypto(default_fatal_handler+0x32) [0x4136b2] 
-> ./test-crypto() [0x40a90a] -> .libs/libdcrypt_openssl.so(+0x1ca0b) [0x503ca0b] -> 
.libs/libdcrypt_openssl.so(+0x1ccf7) [0x503ccf7] -> ./test-crypto() [0x40ebee] -> ./test-crypto() 
[0x4102b1] -> ./test-crypto(test_run+0x11) [0x4103b1] -> ./test-crypto(main+0x1e) [0x40e24e] -> 
/lib64/libc.so.6(__libc_start_main+0xfd) [0x342001ed5d] -> ./test-crypto() [0x40a935]
../../run-test.sh: line 21: 22465 Aborted (core dumped) valgrind -q 
--trace-children=yes --leak-check=full --suppressions="$supp_path" 
--log-file=test.out.$$ $*
==22465== 96 (24 direct, 72 indirect) bytes in 1 blocks are definitely lost in 
loss record 541 of 611
==22465==at 0x4A069EE: malloc (vg_replace_malloc.c:270)
==22465==by 0x503DA78: dovecot_openssl_malloc (dovecot-openssl-common.c:17)
==22465==by 0x3428068B2D: CRYPTO_malloc (in /usr/lib64/libcrypto.so.1.0.1e)
==22465==by 0x34280A5229: BN_new (in /usr/lib64/libcrypto.so.1.0.1e)
==22465==by 0x503C684: dcrypt_openssl_load_private_key_dovecot_v1 
(dcrypt-openssl.c:864)
==22465==by 0x503CCF6: dcrypt_openssl_load_private_key 
(dcrypt-openssl.c:1212)
==22465==by 0x40EBA9: test_load_v1_keys (test-crypto.c:268)
==22465==by 0x4102B0: test_run_funcs (test-common.c:354)
==22465==by 0x4103B0: test_run (test-common.c:404)
==22465==by 0x40E24D: main (test-crypto.c:554)
==22465==
Failed to run: ./test-crypto
make[2]: 

RE: [qmailtoaster] error while installing dovecot-2.2.25-12.qt.src.rpm

[Rajesh M]

eric

this got resolved after i updated openssl.

thanks
rajesh

- Original Message -
From: Rajesh M [mailto:24x7ser...@24x7server.net]
To: qmailtoaster-list@qmailtoaster.com
Sent: Sun, 6 Nov 2016 08:45:36 +0530
Subject:

hi eric

i am getting an error while installing the latest version dovecot
i am receiving the same error on 3 of my servers

this is what i am doing
wget 
ftp://ftp.whitehorsetc.com/pub/qmail/CentOS6/qmt/srpms/updates/dovecot-2.2.25-12.qt.src.rpm
rpmbuild --rebuild --define "dist .qt.el6"  dovecot-2.2.25-12.qt.src.rpm

during make i get the error

make  check-am
make[3]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
make[3]: Nothing to be done for `check-am'.
make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib'
Making check in lib-settings
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-settings'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-settings'
Making check in lib-auth
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-auth'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-auth'
Making check in lib-master
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-master'
for bin in test-master-service-settings-cache; do \
if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
  done
0 / 0 tests failed
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-master'
Making check in lib-charset
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-charset'
for bin in test-charset; do \
if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
  done
charset_is_utf8 .. : ok
charset utf8 . : ok
charset iconv  : ok
charset iconv crashes  : ok
charset iconv utf7 state . : ok
0 / 5 tests failed
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-charset'
Making check in lib-ssl-iostream
make[2]: Entering directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-ssl-iostream'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory 
`/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-ssl-iostream'
Making check in lib-dcrypt
make[2]: Entering directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt'
for bin in test-crypto test-stream; do \
if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \
  done
test_cipher_test_vectors . : ok
test_cipher_aead_test_vectors  : ok
test_hmac_test_vectors ... : ok
test-crypto.c:269: Assert failed: ret == TRUE
test-crypto.c:270: Assert failed: error == NULL
Panic: file dcrypt-openssl.c: line 880 
(dcrypt_openssl_load_private_key_dovecot_v1): assertion failed: (dec_key != 
NULL)
test: random seed #2 was 1478388283
Error: Raw backtrace: ./test-crypto() [0x412e7a] -> 
./test-crypto(default_fatal_handler+0x32) [0x4136b2] -> ./test-crypto() 
[0x40a90a] -> .libs/libdcrypt_openssl.so(+0x1ca0b) [0x503ca0b] -> 
.libs/libdcrypt_openssl.so(+0x1ccf7) [0x503ccf7] -> ./test-crypto() [0x40ebee] 
-> ./test-crypto() [0x4102b1] -> ./test-crypto(test_run+0x11) [0x4103b1] -> 
./test-crypto(main+0x1e) [0x40e24e] -> /lib64/libc.so.6(__libc_start_main+0xfd) 
[0x342001ed5d] -> ./test-crypto() [0x40a935]
../../run-test.sh: line 21: 22465 Aborted (core dumped) 
valgrind -q --trace-children=yes --leak-check=full --suppressions="$supp_path" 
--log-file=test.out.$$ $*
==22465== 96 (24 direct, 72 indirect) bytes in 1 blocks are definitely lost in 
loss record 541 of 611
==22465==at 0x4A069EE: malloc (vg_replace_malloc.c:270)
==22465==by 0x503DA78: dovecot_openssl_malloc (dovecot-openssl-common.c:17)
==22465==by 0x3428068B2D: CRYPTO_malloc (in /usr/lib64/libcrypto.so.1.0.1e)
==22465==by 0x34280A5229: BN_new (in /usr/lib64/libcrypto.so.1.0.1e)
==22465==by 0x503C684: dcrypt_openssl_load_private_key_dovecot_v1 
(dcrypt-openssl.c:864)
==22465==by 0x503CCF6: dcrypt_openssl_load_private_key 
(dcrypt-openssl.c:1212)
==22465==by 0x40EBA9: test_load_v1_keys (test-crypto.c:268)
==22465==by 0x4102B0: test_run_funcs (test-common.c:354)
==22465==by 0x4103B0: test_run (test-common.c:404)
==22465==by 0x40E24D: main (test-crypto.c:554)
==22465==
Failed to run: ./test-crypto
make[2]: *** [check-test] Error 1
make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/root/rpmbuild/B

Re: [qmailtoaster] error 256

[Madd Macc]

Hi Eric, thanks for the reply
No, the emails are not being delivered at all.

On Sat, Nov 14, 2015 at 12:45 AM, Eric Broch 
wrote:

> On 11/13/2015 9:49 PM, Madd Macc wrote:
> > tcpserver: end (number here changes) status 256
> I've read that this is a bad termination of the connection by the client
> or a network problem. Is the mail delivered successfully?
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] error 256

[Eric Broch]

On 11/13/2015 9:49 PM, Madd Macc wrote:
> tcpserver: end (number here changes) status 256
I've read that this is a bad termination of the connection by the client
or a network problem. Is the mail delivered successfully?

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error

[Sree Raj]

Hi Eric,

Thanks for your prompt response. Issue caused due to old domain
existence. So that mail has been tried to deliver in internal server. Once
removed that and refreshed qmail,, Issue got solved.

Regards
Sree

Regards
Sreeraj R S

On Fri, Nov 6, 2015 at 7:22 PM, Eric Broch  wrote:

> On 11/6/2015 3:18 AM, Sree Raj wrote:
>
> 550 5.1.1 sorry, no mailbox here by that name (chkuser)
>
> Sree,
>
> Have a look at this thread:
> http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg17852.html
>
> EricB
>

Re: [qmailtoaster] error

[Eric Broch]

On 11/6/2015 3:18 AM, Sree Raj wrote:
> 550 5.1.1 sorry, no mailbox here by that name (chkuser)
Sree,

Have a look at this thread:
http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg17852.html

EricB

Re: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

[Linux]

Interestingly, in theory which has an old version of openssl you are having
problems with the size of the certificate ... or we who have to date? You
know how is the procedure for updating the keys Difie Helmann or updated to
perform the upgrade of openssl?

Paul

2015-07-30 3:13 GMT-03:00 Sebastian Grewe :

> Great guide! I was also not a fan of downgrading OpenSSL especially with
> the last upgrades required.
>
> It seems this is a remote issue then where mail servers have Diffie
> Helmann keys in a smaller size than required by newer OpenSSL versions. It
> may be a good idea to notify those domains with a quick mail to postmaster
> at least. Upgrading those keys isn't hard and takes seconds.
>
> Thanks for the workaround! I am sure others will find it useful!
>
> Sent from my iPhone
>
> On 30 Jul 2015, at 08:00, Linux  wrote:
>
> Thanks guys, I supposed that one option was to return to my old version of
> openssl but this contains some security problems, the solution I found was
> to share them if they occur:
>
>
> To resolve the issue I made an exception ssl check for these remote hots.
>
> I leave the steps in case help someone:
>
> mkdir /var/qmail/control/notlshosts
> touch /var/qmail/control/notlshosts/domain.com
>
> (If you do not know the mx record of the domain you can use: "dig mx
> domain.com")
>
> touch /var/qmail/control/notlshosts/mail.domain.com
>
> qmailctl restart
>
> Done! --> @400055943b8f3a664b64 delivery 1: success: 
> IP_accepted_message./Remote_host_said:_250_2.0.0_t61JC5iW004986_Message_accepted_for_delivery/
>
> Best regards,
>
>
> Paul
>
>
>
>
> 2015-07-25 1:31 GMT-03:00 Nicholas Chua :
>
>> Hi,
>>
>> Try
>>
>> yum downgrade openssl-devel openssl
>>
>> You might need to downgrade a second time which will allow this issue to
>> solve
>>
>> Regards
>> nic
>>
>>
>> --
>> From: distribucionli...@gmail.com
>> Date: Tue, 21 Jul 2015 17:58:17 -0300
>> To: qmailtoaster-list@qmailtoaster.com
>> Subject: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh
>> key too small
>>
>>
>> Hello friends, I have QmailToaster + centos 5.9 and sending emails I've
>> been getting some failure notice:
>>
>>
>> --
>>
>> mailer-dae...@dominio.com"
>>  escribió:
>>
>> Hi. This is the qmail-send program at dominio.com
>>
>> I'm afraid I wasn't able to deliver your message to the following
>>
>> addresses.
>>
>> This is a permanent error; I've given up. Sorry it didn't work out.
>>
>>
>> :
>>
>> TLS connect failed: error:14082174:SSL
>>
>> routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small; connected to
>> 191.8.4.132.
>>
>> I'm not going to try again; this message has been in the queue too long.
>>
>> ---
>>
>>
>> anyone knows of that is?
>>
>> Best regards,
>>
>> Paul
>>
>>
>>
>

Re: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

[Sebastian Grewe]

Great guide! I was also not a fan of downgrading OpenSSL especially with the 
last upgrades required. 

It seems this is a remote issue then where mail servers have Diffie Helmann 
keys in a smaller size than required by newer OpenSSL versions. It may be a 
good idea to notify those domains with a quick mail to postmaster at least. 
Upgrading those keys isn't hard and takes seconds.

Thanks for the workaround! I am sure others will find it useful!

Sent from my iPhone

> On 30 Jul 2015, at 08:00, Linux  wrote:
> 
> Thanks guys, I supposed that one option was to return to my old version of 
> openssl but this contains some security problems, the solution I found was to 
> share them if they occur:
> 
> 
> To resolve the issue I made an exception ssl check for these remote hots.
> 
> I leave the steps in case help someone:
> 
> mkdir /var/qmail/control/notlshosts
> touch /var/qmail/control/notlshosts/domain.com
> (If you do not know the mx record of the domain you can use: "dig mx 
> domain.com")
> 
> touch /var/qmail/control/notlshosts/mail.domain.com
> 
> qmailctl restart
> 
> Done! --> @400055943b8f3a664b64 delivery 1: success: 
> IP_accepted_message./Remote_host_said:_250_2.0.0_t61JC5iW004986_Message_accepted_for_delivery/
> Best regards,
> 
> Paul
> 
> 
> 
> 2015-07-25 1:31 GMT-03:00 Nicholas Chua :
>> Hi,
>> 
>> Try 
>> 
>> yum downgrade openssl-devel openssl 
>> 
>> You might need to downgrade a second time which will allow this issue to 
>> solve
>> 
>> Regards
>> nic
>> 
>> 
>> From: distribucionli...@gmail.com
>> Date: Tue, 21 Jul 2015 17:58:17 -0300
>> To: qmailtoaster-list@qmailtoaster.com
>> Subject: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key 
>> too small
>> 
>> 
>> Hello friends, I have QmailToaster + centos 5.9 and sending emails I've been 
>> getting some failure notice:
>> 
>> 
>> --
>> mailer-dae...@dominio.com"
>>  escribió:
>> 
>> Hi. This is the qmail-send program at dominio.com
>> I'm afraid I wasn't able to deliver your message to the following
>> addresses.
>> This is a permanent error; I've given up. Sorry it didn't work out.
>> 
>> :
>> TLS connect failed: error:14082174:SSL
>> routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small; connected to 
>> 191.8.4.132.
>> I'm not going to try again; this message has been in the queue too long.
>> ---
>> 
>> 
>> anyone knows of that is?
>> 
>> Best regards,
>> 
>> Paul
> 

Re: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

[Linux]

Thanks guys, I supposed that one option was to return to my old version of
openssl but this contains some security problems, the solution I found was
to share them if they occur:


To resolve the issue I made an exception ssl check for these remote hots.

I leave the steps in case help someone:

mkdir /var/qmail/control/notlshosts
touch /var/qmail/control/notlshosts/domain.com

(If you do not know the mx record of the domain you can use: "dig mx
domain.com")

touch /var/qmail/control/notlshosts/mail.domain.com

qmailctl restart

Done! --> @400055943b8f3a664b64 delivery 1: success:
IP_accepted_message./Remote_host_said:_250_2.0.0_t61JC5iW004986_Message_accepted_for_delivery/

Best regards,


Paul




2015-07-25 1:31 GMT-03:00 Nicholas Chua :

> Hi,
>
> Try
>
> yum downgrade openssl-devel openssl
>
> You might need to downgrade a second time which will allow this issue to
> solve
>
> Regards
> nic
>
>
> --
> From: distribucionli...@gmail.com
> Date: Tue, 21 Jul 2015 17:58:17 -0300
> To: qmailtoaster-list@qmailtoaster.com
> Subject: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh
> key too small
>
>
> Hello friends, I have QmailToaster + centos 5.9 and sending emails I've
> been getting some failure notice:
>
>
> --
>
> mailer-dae...@dominio.com"
>  escribió:
>
> Hi. This is the qmail-send program at dominio.com
>
> I'm afraid I wasn't able to deliver your message to the following
>
> addresses.
>
> This is a permanent error; I've given up. Sorry it didn't work out.
>
>
> :
>
> TLS connect failed: error:14082174:SSL
>
> routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small; connected to
> 191.8.4.132.
>
> I'm not going to try again; this message has been in the queue too long.
>
> ---
>
>
> anyone knows of that is?
>
> Best regards,
>
> Paul
>
>
>

RE: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

[Nicholas Chua]

Hi,

Try 

yum downgrade openssl-devel openssl 

You might need to downgrade a second time which will allow this issue to solve

Regards
nic


From: distribucionli...@gmail.com
Date: Tue, 21 Jul 2015 17:58:17 -0300
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key 
too small

Hello friends, I have QmailToaster + centos 5.9 and sending emails I've been 
getting some failure notice:


--mailer-dae...@dominio.com"
 escribió:

Hi. This is the qmail-send program at dominio.com
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
TLS connect failed: error:14082174:SSL
routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small; connected to 
191.8.4.132.I'm not going to try again; this message has been in the queue too 
long.
---


anyone knows of that is?
Best regards,
Paul

  

Re: [qmailtoaster] error sending : SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small

[Dan McAllister]

It appears you are attempting to send your mail with TLS and your local 
certificate is not valid (DH KEY TOO SMALL).


I usually recommend getting a REAL SSL certificate (vs. self-signed) if 
you're going to be using SSL/TLS security on your systems permanently. 
Its not THAT expensive (see Godaddy.com or most other registrars for deals).


Dan McAllister
IT4SOHO

On 7/21/2015 4:58 PM, Linux wrote:
Hello friends, I have QmailToaster + centos 5.9 and sending emails 
I've been getting some failure notice:



--

mailer-dae...@dominio.com "
mailto:mailer-dae...@dominio.com>> escribió:


Hi. This is the qmail-send program at dominio.com 
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

mailto:jos...@otherdomain.com>>:
TLS connect failed: error:14082174:SSL
routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small; connected 
to 191.8.4.132.

I'm not going to try again; this message has been in the queue too long.

---



anyone knows of that is?

Best regards,

Paul

Re: [qmailtoaster] error

[Dave M]

Ya, I see that now
( Bigger Grin : )

Cheers


On 3/30/2015 12:41 PM, Dan McAllister wrote:

Dave:

The reboot was overkill, but I'm glad its working again. (By overkill, 
I mean the doing the pkill -9 would force the "hung" process to stop 
(as well as any other qmail-smtp processes), then the *supervise 
*program would immediately re-spawn a new one (or new ones) -- 
rebooting essentially killed ALL of the processes... so you fixed it, 
then rebooted which fixed it again )


Dan

On 3/30/2015 3:11 PM, Dave M wrote:

Thanks Dan
it was stuck on port 587
killed the process _*pkill -9 qmail-smtp

did reboot all is well again.

Thanks

On 3/30/2015 8:50 AM, Dan McAllister wrote:

Dave:

It appears there is a "stuck" qmail-smtp process that is bound to 
port (25 since this is the smtp log file -- but this issue can arise 
in submission [port 587], or smtp-ssl [port 465] if that is enabled 
as well).


issue a _*pkill -9 qmail-smtp *_command, as that will force-stop all 
current smtp services (on all ports)... the supervise routines will 
make sure that a new qmail-smtp process is started on all of your ports.


Dan
IT4SOHO


On 3/30/2015 11:38 AM, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
   877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!






--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
   877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!

Re: [qmailtoaster] error

[Dan McAllister]

Dave:

The reboot was overkill, but I'm glad its working again. (By overkill, I 
mean the doing the pkill -9 would force the "hung" process to stop (as 
well as any other qmail-smtp processes), then the *supervise *program 
would immediately re-spawn a new one (or new ones) -- rebooting 
essentially killed ALL of the processes... so you fixed it, then 
rebooted which fixed it again )


Dan

On 3/30/2015 3:11 PM, Dave M wrote:

Thanks Dan
it was stuck on port 587
killed the process _*pkill -9 qmail-smtp

did reboot all is well again.

Thanks

On 3/30/2015 8:50 AM, Dan McAllister wrote:

Dave:

It appears there is a "stuck" qmail-smtp process that is bound to 
port (25 since this is the smtp log file -- but this issue can arise 
in submission [port 587], or smtp-ssl [port 465] if that is enabled 
as well).


issue a _*pkill -9 qmail-smtp *_command, as that will force-stop all 
current smtp services (on all ports)... the supervise routines will 
make sure that a new qmail-smtp process is started on all of your ports.


Dan
IT4SOHO


On 3/30/2015 11:38 AM, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
   877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!






--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
  877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!

Re: [qmailtoaster] error

[Dave M]

Thanks Dan
it was stuck on port 587
killed the process _*pkill -9 qmail-smtp

did reboot all is well again.

Thanks

On 3/30/2015 8:50 AM, Dan McAllister wrote:

Dave:

It appears there is a "stuck" qmail-smtp process that is bound to port 
(25 since this is the smtp log file -- but this issue can arise in 
submission [port 587], or smtp-ssl [port 465] if that is enabled as well).


issue a _*pkill -9 qmail-smtp *_command, as that will force-stop all 
current smtp services (on all ports)... the supervise routines will 
make sure that a new qmail-smtp process is started on all of your ports.


Dan
IT4SOHO


On 3/30/2015 11:38 AM, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
   877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!

Re: [qmailtoaster] error

[Dave M]

Hi Tony,

It was stuck on port 587
ran the kill command as pro Dan`s suggestion, then did reboot

All is well again

Thanks

On 3/30/2015 8:52 AM, Tony White wrote:

Hi Dave,
  What port is the binding error on?
If you know the port you could netstat to find the process taking the 
port.



best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 31/03/2015 02:38, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error

[Dave M]

HI Tony,

It was stuck on port 587
ran the kill command as pro Dan`s suggestion, then did reboot

All is well again

Thanks


On 3/30/2015 8:52 AM, Tony White wrote:

Hi Dave,
  What port is the binding error on?
If you know the port you could netstat to find the process taking the 
port.



best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 31/03/2015 02:38, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error

[Tony White]

Hi Dave,
  What port is the binding error on?
If you know the port you could netstat to find the process taking the port.


best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 31/03/2015 02:38, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error

[Dan McAllister]

Dave:

It appears there is a "stuck" qmail-smtp process that is bound to port 
(25 since this is the smtp log file -- but this issue can arise in 
submission [port 587], or smtp-ssl [port 465] if that is enabled as well).


issue a _*pkill -9 qmail-smtp *_command, as that will force-stop all 
current smtp services (on all ports)... the supervise routines will make 
sure that a new qmail-smtp process is started on all of your ports.


Dan
IT4SOHO


On 3/30/2015 11:38 AM, Dave M wrote:

All of a sudden getting this error in smtp logs

tcpserver: fatal: unable to bind: address already used

Anyone seen before

Thanks


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




--
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
  877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!

Re: [qmailtoaster] Error - message "451 qq write error or disk full (#4.3.0)"

[Madd Macc]

is the /home on a different partition,
please show df -h


On Wed, Dec 31, 2014 at 4:00 AM, Jaime Ventura 
wrote:

> Have you tried reverting the change?
>
> On Wed, Dec 31, 2014 at 4:33 AM, Tony White 
> wrote:
>
>> Hi all,
>>   Desperate here please.
>> Tried to remove domainkeys from the server following this page
>>
>> http://wiki.qmailtoaster.com/index.php/Disabling_Domain_Keys
>>
>> Since doing it I have not been able to store any emails for anyone.
>>
>> Have replace DK but still not joy.
>>
>> There is 459GB free on the drive and all the permissions seem fine.
>>
>> Any help greatly appreciated.
>>
>> Tony White
>> PS sending email from Yahoo as email server will not do it.
>>
>> Thanks in advance.
>>
>
>

Re: [qmailtoaster] Error - message "451 qq write error or disk full (#4.3.0)"

[Jaime Ventura]

Have you tried reverting the change?

On Wed, Dec 31, 2014 at 4:33 AM, Tony White  wrote:

> Hi all,
>   Desperate here please.
> Tried to remove domainkeys from the server following this page
>
> http://wiki.qmailtoaster.com/index.php/Disabling_Domain_Keys
>
> Since doing it I have not been able to store any emails for anyone.
>
> Have replace DK but still not joy.
>
> There is 459GB free on the drive and all the permissions seem fine.
>
> Any help greatly appreciated.
>
> Tony White
> PS sending email from Yahoo as email server will not do it.
>
> Thanks in advance.
>

[qmailtoaster] Re: qmailtoaster error with fresh install

[Eric Shubert]

Hmmm. I don't understand how the lack of that module could have caused 
that error.


In any case, the module *is* required. It's included in the 
qtp-dependencies script, which qtp-newmodel uses. qtp-newmodel is the 
preferred method of installing these days, as the other scripts have not 
been maintained for some time, nor will be in the future.


Sorry for the confusion, Rajesh. I know that there is still some 
obsolete stuff out there which needs to be brought up to date. I hope 
that we'll make significant progress on this soon.


Thanks.

--
-Eric 'shubes'

On 05/08/2013 01:13 PM, Rajesh M wrote:

hi eric

the reason was

REQUIRED module missing: NetAddr::IP

i manually installed this perl module and spamassassin install was
successful.

i believe the centos install script ie the perl module part of this shud
include the above.

rajesh



On 05/07/2013 10:57 AM, Rajesh M wrote:

hi

centos 5 32 bit latest version

machine is a dual core xeon

i am getting the following error in the installation spamassassin rpm
latest version from qmail-toaster.com website

bad exit status from /var/tmp/rpm-tmp.1.4633(%build)
error : file not found by glob :
/usr/src/redhat/SRPMS/i386/spamassassin-toaster*.rpm

what is the solution please

rajesh

-


Apparently that file didn't download. Download it manually?


--
-Eric 'shubes'


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com









-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com







-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: qmailtoaster error with fresh install

[Rajesh M]

hi eric

the reason was

REQUIRED module missing: NetAddr::IP

i manually installed this perl module and spamassassin install was
successful.

i believe the centos install script ie the perl module part of this shud
include the above.

rajesh


> On 05/07/2013 10:57 AM, Rajesh M wrote:
>> hi
>>
>> centos 5 32 bit latest version
>>
>> machine is a dual core xeon
>>
>> i am getting the following error in the installation spamassassin rpm
>> latest version from qmail-toaster.com website
>>
>> bad exit status from /var/tmp/rpm-tmp.1.4633(%build)
>> error : file not found by glob :
>> /usr/src/redhat/SRPMS/i386/spamassassin-toaster*.rpm
>>
>> what is the solution please
>>
>> rajesh
>>
>> -
>
> Apparently that file didn't download. Download it manually?
>
>
> --
> -Eric 'shubes'
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: qmailtoaster error with fresh install

[Eric Shubert]

On 05/07/2013 10:57 AM, Rajesh M wrote:

hi

centos 5 32 bit latest version

machine is a dual core xeon

i am getting the following error in the installation spamassassin rpm
latest version from qmail-toaster.com website

bad exit status from /var/tmp/rpm-tmp.1.4633(%build)
error : file not found by glob :
/usr/src/redhat/SRPMS/i386/spamassassin-toaster*.rpm

what is the solution please

rajesh

-


Apparently that file didn't download. Download it manually?


--
-Eric 'shubes'


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] error

[Edward Finlayson]

HI dave,
You are perfectly correct that this is indeed a rDNS issue. If you are host all 
your own dns then you need to get your hosting company to delegate the IP to 
your server, if not then you may be able to create the entry in your hosting 
providers interface. 

I hope this helps. But if you require further information, particularly with 
DJBDNS then please feel free to email.

Fin
Sent from my  BlackBerry®

-Original Message-
From: Dave MacDonald 
Date: Mon, 29 Oct 2012 08:25:54 
To: 
Reply-To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] error

Hi Guys,
Just recently I am getting rejections from this list.

Remote host said: 421 Refused. Your reverse DNS entry does not resolve.
Giving up on 80.254.129.244.
I'm not going to try again; this message has been in the queue too long.


an anyone contact me , off List please as this is not a qmail issue, but
seems to be reverse dns,

Thanks
dmacd6...@gmail.com

Re: [qmailtoaster] Error while receiving mail

[Dan McAllister]

  
  
Amit,
  
  I suspect chkuser is choking on the presence of the = characters
  in the mail address...
  
  Dan
  
  On 7/27/2012 3:23 AM, Amit wrote:


  
  
  
  
  
Hi,
 
I’m using QMT to scan and forward mail to
  internal Exchange server at 1 of my client location.
  Everything is working fine, but yesterday my client complaint
  that he is not receiving mail from 1 of the sender and sender
  is getting bounce message. Below is the bounce message:
 
Connected
to 192.168.1.6 but sender was rejected.
Remote
host said: 501 5.5.4 Invalid arguments 
---
Below this line is a copy of the message. 
Return-Path:

Here, 192.168.1.6 is my exchange server IP.
  When I remove QMT, then I receive the email. Do I follow same
  process which we do for blackberry characters.
 
Regards,
 

  Amit |   Mobile : +91 -
866101 

  

  

  


  

  
  

  
  
 
  
  
I Knowledge
  Factory Pvt. Ltd.
  Manohar,
Plot No. 2, S.No : 47/1B- 1/2, 
3rd Floor, Taware Colony, Near Muktangan School,
Aranyeshwar Road. Pune - 411009
  Tel
: +91-20-2422-786-1 / 2 / 3 / 4 Extn - 204
  


  

  

  

 

  

  

  
  

  

  

 
 
  



-- 

IT4SOHO, LLC
PO Box 507
St. Petersburg, FL 33731-0507

CALL TOLL FREE:
  877-IT4SOHO

We have support plans for QMail!


  

Re: [qmailtoaster] Error receiving mail from 1 domain

[Bharath Chari]

On Tuesday 07 February 2012 10:29 PM, Dan McAllister wrote:
My only comment is to say that, despite the fact that you might really 
WANT that marketing e-mail, the fact is that if they're doing what 
clam says they're doing (like the example below), then at best they're 
being deceitful... it may be a benign deceit, but it is deceit never 
the less.


I have seen some really ironical ones. My bank periodically sends me 
mail warning me against Phishing - Unfortunately the people who design 
the mail, have not the faintest idea what it means - so happily create 
spoofed links in the mail (ostensibly to make it prettier). And needless 
to say, ClamAV spits the mail out :).


Bharath


Remember, about 20% of virus infections occur because the AV program 
pops up and says "Danger Will Robinson" and good old Will says "Shut 
up, Robot"... just before the alien takes him hostage.


That is, they're told it's dangerous, but they click "install anyway" 
or "allow" or whatever... and then they get mad that their AV didn't 
protect them... sigh


Really people, if we assume that every "hit" on a SPAM blocker or 
AntiVirus is a false positive, then why run one at all?


Dan McAllister
IT4SOHO