Awesome!!!
On 2/21/2017 2:47 PM, CarlC Internet Services Service Desk wrote:
Found the slowness...
In the "run" file for smtp-ssl, I have:
BLACKLIST=`cat /var/qmail/control/blacklists-ssl`
Well, That file does not exist, so that plays havoc with:
exec /usr/bin/softlimit -m 128000 \
Found the slowness...
In the "run" file for smtp-ssl, I have:
BLACKLIST=`cat /var/qmail/control/blacklists-ssl`
Well, That file does not exist, so that plays havoc with:
exec /usr/bin/softlimit -m 128000 \
/usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \
-u "$QM
I use bind and djbdns. Others use pdns all with /etc/resolv.conf set to
127.0.0.1
Here's my install script:
https://raw.githubusercontent.com/qmtoaster/scripts/master/chg_dns.sh
Not sure if it will help.
Can you send me your run script for smtp 465 so I can test it here and
determine if it's
-Original Message-
From: Tonix -
>Check your dns. It looks like it takes time to solve client reverse ip.
I'm using 8.8.4.4, 4.2.2.1 and 8.8.8.8... They do run pretty fast. That's in
/etc/resolv.conf. It's the same setting as the old Email server had.
Does QMail use a different place t
Check your dns. It looks like it takes time to solve client reverse ip.
Regards,
Tonino
Il 19/02/2017 17:59, CarlC Internet Services Service Desk ha scritto:
-Original Message-
From: Eric Broch
does this happen in your webmail, squirrelmail and roundcube?
Nope... Only with anythin
-Original Message-
From: Eric Broch
>does this happen in your webmail, squirrelmail and roundcube?
Nope... Only with anything using smtp-ssl (port 465)...
Carl
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr..
does this happen in your webmail, squirrelmail and roundcube?
On 2/19/2017 6:17 AM, CarlC Internet Services Service Desk wrote:
With a newly installed QMT, when we send emails, it works... But it takes
about 10 seconds.. It just sits at sending on the client side waiting for
the server to compl
With a newly installed QMT, when we send emails, it works... But it takes
about 10 seconds.. It just sits at sending on the client side waiting for
the server to complete. Before I go digging into this, has anyone else seen
this? Or is it some simple setting I've missed :)
Thanks,
Carl