slamp slamp wrote:
According to the rpm's the file belongs to qmail-toaster.

# rpm -q --whatprovides /etc/tcprules.d/tcp.smtp
qmail-toaster-1.03-1.3.15


the only package i updated was simscan-toaster to the latest 1.4.0
which doesn't know anything about this file (its probably part of the
spec file)

# rpm -ql simscan-toaster
/usr/share/doc/simscan-1.4.0/AUTHORS
/usr/share/doc/simscan-1.4.0/ChangeLog
/usr/share/doc/simscan-1.4.0/INSTALL
/usr/share/doc/simscan-1.4.0/README
/usr/share/doc/simscan-1.4.0/TODO
/usr/share/doc/simscan-1.4.0/ssattach.example
/var/qmail/bin/simscan
/var/qmail/bin/simscanmk
/var/qmail/control/simcontrol
/var/qmail/simscan


is there a reason why tcp.smtp was updated by this package (even if it
is in the spec file, shouldn't the qmail-toaster be doing the
updates?)

It is changed in the simscan spec file. qmail-toaster writes an initial tcp.smtp file but it does not understand options like NOP0FCHECK="1". Those options cannot be understood until simscan is installed, since they're in simscan, not qmail-toaster. Because of that the simscan package rewrites the tcp.smtp file when it will understand options like the above. If the qmail-toaster package made the changes the daemon would fail at that point and those that do not wish to install simscan-toaster would be left with a system that didn't work. I'll look into changing the spec file in the future so it does not overwrite existing tcp.smtp, until this become a problem.

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
     If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
    Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to