so nobody knows what would cause qmail-scanner to complain like so?
A problem was found in an Email message you sent.
This Email scanner intercepted it and stopped the entire message
reaching its destination.
The problem was reported to be:
Disallowed MIME characters found in headers
Please c
But wouldn't that forward all mail that was considered "everything else" to
"[EMAIL PROTECTED]"? Which is all essentially legitimate mail?
--Jeremy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Doug Monroe
Sent: Friday, August 30, 2002 8:37 PM
To: [EM
Jeremy Olmen wrote:
>
> Only problem is that I'm not trying to do any local delivery, this is simply
> a spam-and-virus filtering front end for the destination (sadly, exchange).
> My job would be so much easier if I could've just used maildrop or procmail!
> (although it appears maildrop only wo
Only problem is that I'm not trying to do any local delivery, this is simply
a spam-and-virus filtering front end for the destination (sadly, exchange).
My job would be so much easier if I could've just used maildrop or procmail!
(although it appears maildrop only works with sendmail).
-Origi
I recently removed the QMAILQUEUE variable from the qmail-smtpd/run file
and am now just using tcpserver to invoke qmail-scanner. It is working
great. I can now allow mail from my unix systems and have bypass the
scanner.
I am noticing one thing that I can't figure out though... Ever since I
made
This is a belated follow up to my postings and other people's responses last
week.
By way of summary, I was having a problem where the email headers of
locally-relayed outbound mail were getting mangled, resulting in remote
hosts not being able to recognize the sender and therefore "Reply" wouldn
Doug Monroe wrote:
[snip]
> MAILDIR=$HOME/Maildir/
> DEFAULT=$MAILDIR
[snip]
> ## WHAT TO DO
> # options: -delete- or -hold- or -forward- spam
> # to delete
> /dev/null
> # to hold:
> #spam <-- SEE NOTE BELOW
> # or...
> # to forward:
> # ! [EMAIL PROTECTED]
I should men
Jeremy Olmen wrote:
>
> I am trying to use qmail-scanner in conjunction with spamassassin as well as
> a small script to determine the score of the message, and if it's above my
> defined threshold to send it to another mailbox. If the conditions are met
> and the message is to be sent to another
I am trying to use qmail-scanner in conjunction with spamassassin as well as
a small script to determine the score of the message, and if it's above my
defined threshold to send it to another mailbox. If the conditions are met
and the message is to be sent to another mailbox, all I'm doing is
re-w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
In message <[EMAIL PROTECTED]>, Greg Wildman writes:
>On Thu, 2002-08-29 at 19:23, Ron Culler wrote:
>> Just shooting this out to see what responses I get. I was interested in
>> looking at what it would ta
I just added the mime version and still got the same thing..
The problem was reported to be:
Disallowed MIME characters found in headers
Please contact your I.T support personnel with any queries regarding this
policy.
Your message was sent with the following envelope:
MAIL FROM: [EMAIL PRO
On Fri, 30 Aug 2002 11:03:38 -0400 (EDT) jason <[EMAIL PROTECTED]> wrote:
> qmail-scanner folks,
> Im trying to use dragonfly mail 1.1.13
> http://www.dflytech.com/products/dragonflymail/
> to send an email to my account on monsterjam.org (as a test) and the
> dragonfly mail works fine, but my qm
qmail-scanner folks,
Im trying to use dragonfly mail 1.1.13
http://www.dflytech.com/products/dragonflymail/
to send an email to my account on monsterjam.org (as a test) and the
dragonfly mail works fine, but my qmail-scanner keeps complaining about
disallowed mime characters. Exactly what is it co
13 matches
Mail list logo
