On 08/20/2012 07:05 PM, Kelly Cobean wrote:
On 08/20/2012 06:29 PM, Kelly Cobean wrote:
Just out of curiosity, I did pretty much a
textbook QT/QTP install...any idea how/why this text was missing from
the
tcp.smtp file?  I had not edited this file prior to today.

I've no idea. I'll be doing a scratch install in a few days though, and
try to keep my eye on it.

Here's what I have as /etc/tcprules.d/tcp.smtp in the present pkg (2
lines):
127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1"
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"

TTBOMK, this file is coded as "noreplace", which means that an
install/upgrade will never change it if one exists. If there existed one
from a previous install of some kind, that would persist. Out of
curiosity, what does:
# ls -ltr /etc/tcprules.d/tcp.smtp*
show on the host?

--
-Eric 'shubes'



root@www ~]# ls -ltr /etc/tcprules.d/tcp.smtp*
-rw-r--r-- 1 root root  293 Aug 20 16:50 /etc/tcprules.d/tcp.smtp.new
-rw-r--r-- 1 root root  251 Aug 20 17:01 /etc/tcprules.d/tcp.smtp
-rw-r--r-- 1 root root 2325 Aug 20 17:02 /etc/tcprules.d/tcp.smtp.cdb




---------------------------------------------------------------------

I think that tcp.smtp.new would be the original stock version from the qmail-toaster package.

I wonder if maybe one of the subsequent packages (simscan perhaps) has a tcp.smtp file that needs to be updated. Could be that's where it came from. Simscan hadn't been updated in a while before the recent one. rpm shows qmail-toaster as owning file file though. Hmmmm. Seems to me that qmail-toaster should be dependent upon simscan, but that's not how things are presently set up. I need to look into this in a bit more detail.

Thanks for pointing this out, Kelly.

--
-Eric 'shubes'




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to