I vote to leave it alone. Let the configuring individual invoke
/bin/sh in QMAILQUEUE herself if she understands and still wants to
make that particular convenience vs. overhead tradeoff.
Valued at $0.02,
JS
On Sun, Jun 10, 2001 at 10:26:28PM -0600, Bruce Guenter wrote:
I've been
FWIW, this is a tactic I have recommended on many occasions when an
Outlook or Outlook Express user reports seemingly inexplicable
behavior. It repairs such problems remarkably often.
Respectfully,
JS
On Mon, May 21, 2001 at 10:37:17AM -0700, Isaac Chapman wrote:
To fix my Outlook problem,
Check out badrcptto from the SPAMCONTROL patch set.
JS
On Mon, May 21, 2001 at 02:54:18PM -0500, Brian Moon wrote:
I have a need to set up a file like badmailfrom that filters for recipients
in incoming emails.
I have tried qtools but cannot find the right combo.
What I have is a file
-0400, Jim Steele wrote:
Does anyone have a qmail-remote.c that has been patched for qmtp AND
outgoingip? I must have botched the patch combination, since I now get:
qmail-remote2001-05-18 17:21:26.339297500 delivery 1: deferral:
qmail-remote_crashed./
Thank goodness I backed up
Does anyone have a qmail-remote.c that has been patched for qmtp AND
outgoingip? I must have botched the patch combination, since I now get:
qmail-remote2001-05-18 17:21:26.339297500 delivery 1: deferral: qmail-remote_crashed./
Thank goodness I backed up the binaries and use RCS on the source.
This is not spam. This is the W32/Hybris worm. Your user is infected.
Check the logs for the email message immediately preceding this one.
That's probably your infected user, since Hybris attaches itself to
the wsock2.dll library and sends out an email message immediately
after a valid one is
On Mon, May 14, 2001 at 12:35:32PM +, Mark Delany wrote:
=.:allow
:deny
Close. To achieve this, the tcp.smtp file should actually contain:
=:allow
:deny
I just experimented with both forms. With the dot, nothing matched,
including hosts with good forward/reverse resolvability.
