Hello
Thanks for your answer.
So I understand it can not be done to reject invalid senders simply by
using Declude/Imail?
I really need another product?
Also another question: I use per domain configuration for Junkmail - can
it be configured so that it only performs the tests on mails that go to
a domain that has been set up with a configuration folder?
It seems like declude is doing the tests on all mails which uses more
ressources than doing the tests only when required (as defined in per
domain config)
Thanks
Andy Schmidt schrieb:
Hi,
Basically, you should put a mail gateway in front of your mail server that
can integrate your list of valid email recipients and that can refuse most
of your messages based on your anti-spam and anti-virus policies.
One option would be to run Declude's own gateway product.
However, to me a crucial element of a gateway is that it MUST reject
messages DURING the SMTP envelope (e.g., after the data is received but
before the receipt is confirmed with a 2xx.). This way, the gateway can
refuse unwanted messages with a 5xx (or 4xx) return code and the SENDING
SMTP server will inform its user.
It is an absolute must in case of the occasional false positive. At least a
"good" sender will be notified that there's a problem with their email.
If a gateway first accepts messages and THEN scans them, it would need to
generate "bounce" messages AFTER the fact. The result is a very high
likelihood that your system will be spamming innocent email users whose
address had been faked.
I simply can't consider any gateway product that doesn't do spam/virus
rejection DURING the SMTP envelope!
One alternative could be to set up IIS SMTP on one of your machines, point
your MX there, purchase ORF and then integrate it with Sniffer so that it
can reject the vast majority of your spam.
If you also bring your list of valid email recipients over to that
IIS/ORF/Sniffer gateway, then you can reject invalid recipients (e.g.,
dictionary attacks) at that machine, instead of tying up Imail with that.
Best Regards
Andy Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax: +1 201 934-9206
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
netsolution webmaster
Sent: Tuesday, November 14, 2006 09:59 AM
To: declude.junkmail@declude.com
Subject: [Declude.JunkMail] delete mails before processing / 100% CPU
With the massive amount of spam mail our server has difficulties to process
everything in time, since two days we are on 100% CPU and customers have
difficulties with pop/imap speed (before everything was ok).
What ways are there to
- refuse mails that have no valid recipient on the mailserver (not bounce,
just refuse/drop) so they need no more processing?
- refuse/drop mails that don't pass certain tests (eg. spamcop or sniffer)?
OR what other methods could speed up things?
We have older versions of declude /imail server (8.15)
Thanks
---
This E-mail came from the Declude.JunkMail mailing list. To unsubscribe,
just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe
Declude.JunkMail". The archives can be found at
http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
