All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gustav gundacker" <gg0815@gmx.net>
To: aellis@saberlogic.com
Cc: netfilter@lists.netfilter.org
Subject: Re: SMTP Routing Based On Recipient
Date: Tue, 23 Dec 2003 22:57:18 +0100 (MET)	[thread overview]
Message-ID: <30807.1072216638@www24.gmx.net> (raw)
In-Reply-To: 1072121282.10935.12.camel@localhost.localdomain

a solution is smtpd/smtpfwdd from juniper see
http://www.obtuse.com/smtpd.html

gunnar

> I am running a MS Exchange 5.5 server and am getting hit with the NDR
> (non-delivery report) Reverse Spam Attack as described here:
>  
> http://www.tek-tips.com/gviewthread.cfm/lev2/3/lev3/15/pid/10/qid/725829
> 
> As the thread describes, there is no way to just turn off NDRs in
> Exchange 5.5 - Microsoft is recommending third party utilities.  What I
> am wondering is this - would it be possible to redirect SMTP to my Linux
> server, use iptables to check that the recipient matches a valid user
> >from a list I'd supply, and, if so, route the message to the Exchange
> server?  And, if no valid recipient is found, the message is simply
> dropped.  Is this even a logical way to handle this situation?  Should I
> be looking at something like snort instead?  I'm all ears!
> 
> Thanks,
> -- 
> Adam Ellis <aellis@saberlogic.com>
> SaberLogic
> 

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net




      parent reply	other threads:[~2003-12-23 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 19:28 SMTP Routing Based On Recipient Adam Ellis
2003-12-22 19:39 ` Antony Stone
2003-12-23 11:37 ` Chris Brenton
2003-12-23 13:00   ` Adam Ellis
2003-12-23 13:14     ` Antony Stone
2003-12-23 15:36       ` Michael Gale
2003-12-23 15:52         ` Antony Stone
2003-12-23 19:20       ` Mark E. Donaldson
2003-12-23 21:57 ` gustav gundacker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30807.1072216638@www24.gmx.net \
    --to=gg0815@gmx.net \
    --cc=aellis@saberlogic.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.