The group was the issue. When I set the client to 587 with STARTTLS, it
sent just fine.
Thanks Eric.
Scott
On 5/31/10 6:50 PM, Eric Shubert wrote:
Hmmmm. That should work.
Have you generated and signed a certificate, or are you using what QMT
generated in /var/qmail/control/servercert.pem? Are it's permissions
what they should be?
-rw-r----- 1 root vchkpw 2416 Feb 25 18:52 servercert.pem
Scott Hughes wrote:
Another piece to this puzzle is that I seem to be getting into the
server, but not authenticating / sending:
@400000004c043a01028b543c tcpserver: status: 1/100
@400000004c043a01028de47c tcpserver: pid 25602 from 77.141.113.41
@400000004c043a01028fa5b4 tcpserver: ok 25602
mail.SERVERNAME.net:69.255.214.146:587 :77.141.113.41::49833
@400000004c043a4717477edc tcpserver: end 25602 status 256
@400000004c043a471747f024 tcpserver: status: 0/100
The last two lines pop in after I cancel the attempted send from the
email client.
Here is my submission run script. I have not edited this file:
#!/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 REQUIRE_AUTH=1
exec /usr/bin/softlimit -m 12000000 \
/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
Thanks,
Scott
On 5/31/10 4:31 PM, Eric Shubert wrote:
Which client are you trying to use SSL from?
You can use TLS on port 587, but not SSL.
SMTPS (SMTP over SSL) is deprecated, so you shouldn't use it unless
you have too (Outlook'03 being the only case I'm aware of). If you
need to use SSL with Outlook'03, you should set up port 465 for
using SMTPS the old fashioned way. If you're using Outlook'03 only
on a local network, I wouldn't bother.
