Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-07 Thread Eric Broch

I should put it into the RPM, my bad.

On 8/7/2020 7:04 PM, Eric Broch wrote:


It's part of the CentOS 8/QMT, but I only added to the most recent 
CentOS 7/QMT install script maybe a month or so ago. So if you 
installed earlier than the past month or so it wasn't in the script. 
There were, however, instructions on the main web page.



On 8/7/2020 6:38 PM, Chris wrote:
Thanks.  Is that not part of the toaster setup script, or did I 
somehow wipe my man_db.conf at some point?


On Sat, Aug 8, 2020 at 12:17 PM Eric Broch > wrote:


echo "MANDATORY_MANPATH /var/qmail/man" >> /etc/man_db.conf

On 8/7/2020 6:15 PM, Chris wrote:

Erk...

# man qmail-smtpd
No manual entry for qmail-smtpd


On Fri, Aug 7, 2020 at 9:06 AM Eric Broch
mailto:ebr...@whitehorsetc.com>> wrote:

#!/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="!+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 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


for other settings type

# man qmail-smtpd

and scroll to the bottom



On 8/6/2020 3:02 PM, Chris wrote:

What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch
mailto:ebr...@whitehorsetc.com>>
wrote:

Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to 
the version of email in the testing repo. Now email can only be sent on 587 
with plain passwords. Since I have everyone using TLS that’s still secure, but 
it’s causing a headache for existing non-technical users who’s settings 
suddenly don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely 
removed?

-Sent from my Pip-Boy 3000

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

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




Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-07 Thread Eric Broch
It's part of the CentOS 8/QMT, but I only added to the most recent 
CentOS 7/QMT install script maybe a month or so ago. So if you installed 
earlier than the past month or so it wasn't in the script. There were, 
however, instructions on the main web page.



On 8/7/2020 6:38 PM, Chris wrote:
Thanks.  Is that not part of the toaster setup script, or did I 
somehow wipe my man_db.conf at some point?


On Sat, Aug 8, 2020 at 12:17 PM Eric Broch > wrote:


echo "MANDATORY_MANPATH /var/qmail/man" >> /etc/man_db.conf

On 8/7/2020 6:15 PM, Chris wrote:

Erk...

# man qmail-smtpd
No manual entry for qmail-smtpd


On Fri, Aug 7, 2020 at 9:06 AM Eric Broch
mailto:ebr...@whitehorsetc.com>> wrote:

#!/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="!+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 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


for other settings type

# man qmail-smtpd

and scroll to the bottom



On 8/6/2020 3:02 PM, Chris wrote:

What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch
mailto:ebr...@whitehorsetc.com>>
wrote:

Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to 
the version of email in the testing repo. Now email can only be sent on 587 
with plain passwords. Since I have everyone using TLS that’s still secure, but 
it’s causing a headache for existing non-technical users who’s settings 
suddenly don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely 
removed?

-Sent from my Pip-Boy 3000

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

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




Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-07 Thread Chris
Thanks.  Is that not part of the toaster setup script, or did I somehow
wipe my man_db.conf at some point?

On Sat, Aug 8, 2020 at 12:17 PM Eric Broch  wrote:

> echo "MANDATORY_MANPATH /var/qmail/man" >> /etc/man_db.conf
>
> On 8/7/2020 6:15 PM, Chris wrote:
>
> Erk...
>
> # man qmail-smtpd
> No manual entry for qmail-smtpd
>
>
> On Fri, Aug 7, 2020 at 9:06 AM Eric Broch  wrote:
>
>> #!/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="!+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 587 \
>> $SMTPD $VCHKPW /bin/true 2>&1
>>
>>
>> for other settings type
>>
>> # man qmail-smtpd
>>
>> and scroll to the bottom
>>
>>
>>
>> On 8/6/2020 3:02 PM, Chris wrote:
>>
>> What should submission/run look like?
>>
>> On Fri, Aug 7, 2020 at 8:10 AM Eric Broch 
>> wrote:
>>
>>> Yes, the new SMTPS looks like this
>>>
>>> #!/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
>>>
>>>
>>>
>>> On 8/6/2020 1:50 PM, Philip Nix Guru wrote:
>>>
>>> Hello
>>>
>>> check your run file
>>>
>>> for smtp and smtps
>>>
>>>
>>> post it here
>>>
>>>
>>> Regards
>>>
>>> -P
>>>
>>>
>>> On 8/6/20 9:33 PM, Boheme wrote:
>>>
>>> In an attempt to resolve my duplicate email issues, I upgraded to the 
>>> version of email in the testing repo. Now email can only be sent on 587 
>>> with plain passwords. Since I have everyone using TLS that’s still secure, 
>>> but it’s causing a headache for existing non-technical users who’s settings 
>>> suddenly don’t work.
>>>
>>> Was this an expected change?
>>> Is it reversible, or has the md5 challenge response been completely removed?
>>>
>>> -Sent from my Pip-Boy 3000
>>> -
>>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>>
>>>


Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-07 Thread Eric Broch

echo "MANDATORY_MANPATH /var/qmail/man" >> /etc/man_db.conf

On 8/7/2020 6:15 PM, Chris wrote:

Erk...

# man qmail-smtpd
No manual entry for qmail-smtpd


On Fri, Aug 7, 2020 at 9:06 AM Eric Broch > wrote:


#!/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="!+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 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


for other settings type

# man qmail-smtpd

and scroll to the bottom



On 8/6/2020 3:02 PM, Chris wrote:

What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch
mailto:ebr...@whitehorsetc.com>> wrote:

Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the 
version of email in the testing repo. Now email can only be sent on 587 with 
plain passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely 
removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com  

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




Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-07 Thread Chris
Erk...

# man qmail-smtpd
No manual entry for qmail-smtpd


On Fri, Aug 7, 2020 at 9:06 AM Eric Broch  wrote:

> #!/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="!+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 587 \
> $SMTPD $VCHKPW /bin/true 2>&1
>
>
> for other settings type
>
> # man qmail-smtpd
>
> and scroll to the bottom
>
>
>
> On 8/6/2020 3:02 PM, Chris wrote:
>
> What should submission/run look like?
>
> On Fri, Aug 7, 2020 at 8:10 AM Eric Broch  wrote:
>
>> Yes, the new SMTPS looks like this
>>
>> #!/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
>>
>>
>>
>> On 8/6/2020 1:50 PM, Philip Nix Guru wrote:
>>
>> Hello
>>
>> check your run file
>>
>> for smtp and smtps
>>
>>
>> post it here
>>
>>
>> Regards
>>
>> -P
>>
>>
>> On 8/6/20 9:33 PM, Boheme wrote:
>>
>> In an attempt to resolve my duplicate email issues, I upgraded to the 
>> version of email in the testing repo. Now email can only be sent on 587 with 
>> plain passwords. Since I have everyone using TLS that’s still secure, but 
>> it’s causing a headache for existing non-technical users who’s settings 
>> suddenly don’t work.
>>
>> Was this an expected change?
>> Is it reversible, or has the md5 challenge response been completely removed?
>>
>> -Sent from my Pip-Boy 3000
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>>


Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Eric Broch

remember to stop and start qmail

# qmailctl stop

# qmailctl start

On 8/6/2020 3:06 PM, Eric Broch wrote:


#!/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="!+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 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


for other settings type

# man qmail-smtpd

and scroll to the bottom



On 8/6/2020 3:02 PM, Chris wrote:

What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch > wrote:


Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the 
version of email in the testing repo. Now email can only be sent on 587 with 
plain passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com  

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




Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread 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="!+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 587 \
    $SMTPD $VCHKPW /bin/true 2>&1


for other settings type

# man qmail-smtpd

and scroll to the bottom



On 8/6/2020 3:02 PM, Chris wrote:

What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch > wrote:


Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the 
version of email in the testing repo. Now email can only be sent on 587 with 
plain passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com  

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




Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Chris
What should submission/run look like?

On Fri, Aug 7, 2020 at 8:10 AM Eric Broch  wrote:

> Yes, the new SMTPS looks like this
>
> #!/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
>
>
>
> On 8/6/2020 1:50 PM, Philip Nix Guru wrote:
>
> Hello
>
> check your run file
>
> for smtp and smtps
>
>
> post it here
>
>
> Regards
>
> -P
>
>
> On 8/6/20 9:33 PM, Boheme wrote:
>
> In an attempt to resolve my duplicate email issues, I upgraded to the version 
> of email in the testing repo. Now email can only be sent on 587 with plain 
> passwords. Since I have everyone using TLS that’s still secure, but it’s 
> causing a headache for existing non-technical users who’s settings suddenly 
> don’t work.
>
> Was this an expected change?
> Is it reversible, or has the md5 challenge response been completely removed?
>
> -Sent from my Pip-Boy 3000
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>


Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Chris
Thank you.  There are a few exported variables that were not present in the
version installed by qmail-1.03-3.2.qt.el7.x86_64

Giving it a try now.

On Fri, Aug 7, 2020 at 8:43 AM Philip Nix Guru  wrote:

>
> Hello
>
> ok that's correct
>
>
>
> On 8/6/20 10:09 PM, Eric Broch wrote:
>
> Yes, the new SMTPS looks like this
>
> #!/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
>
>
>
> On 8/6/2020 1:50 PM, Philip Nix Guru wrote:
>
> Hello
>
> check your run file
>
> for smtp and smtps
>
>
> post it here
>
>
> Regards
>
> -P
>
>
> On 8/6/20 9:33 PM, Boheme wrote:
>
> In an attempt to resolve my duplicate email issues, I upgraded to the version 
> of email in the testing repo. Now email can only be sent on 587 with plain 
> passwords. Since I have everyone using TLS that’s still secure, but it’s 
> causing a headache for existing non-technical users who’s settings suddenly 
> don’t work.
>
> Was this an expected change?
> Is it reversible, or has the md5 challenge response been completely removed?
>
> -Sent from my Pip-Boy 3000
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>


Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Philip Nix Guru


Hello

ok that's correct



On 8/6/20 10:09 PM, Eric Broch wrote:


Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the version 
of email in the testing repo. Now email can only be sent on 587 with plain 
passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com



Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Eric Broch

Yes, the new SMTPS looks like this

#!/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



On 8/6/2020 1:50 PM, Philip Nix Guru wrote:


Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the version 
of email in the testing repo. Now email can only be sent on 587 with plain 
passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail:qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:qmailtoaster-list-h...@qmailtoaster.com



Re: [qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

2020-08-06 Thread Philip Nix Guru

Hello

check your run file

for smtp and smtps


post it here


Regards

-P


On 8/6/20 9:33 PM, Boheme wrote:

In an attempt to resolve my duplicate email issues, I upgraded to the version 
of email in the testing repo. Now email can only be sent on 587 with plain 
passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work.

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com