> Similar but more sane idea is SPF, but it also breaks many things like
> forwarding messages.
Uh... "breaks forwarding" ?!? Yes, it does, but only if you implement
SPF and don't implement SRS, otherwise it won't break anything
--
> Does ASSP have the ability to 'check' an SMTP connection is actually
> coming from a real server and not a botnetted PC? By this I mean to
> suspend processing an incoming connection and call back to the
> originating IP address on port 25 seeing if a real server answers?
BAD idea; a lot of
You can't expect IP used for outbound delivery to also be used for
incoming mail - those are defined by MX records under senders domain.
Large mail servers hame many mx-es and many mta-smtps for outgoing
mail.
Similar but more sane idea is SPF, but it also breaks many things like
forwarding message
Hi
Does ASSP have the ability to 'check' an SMTP connection is actually
coming from a real server and not a botnetted PC? By this I mean to
suspend processing an incoming connection and call back to the
originating IP address on port 25 seeing if a real server answers?
I'd imagine that a spamm
AutoUpdate will fix this.
--
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
For Users of ASSP schreibt:
>(although it cant contain valid file:).
? I do not understand.
A valid file would also do.
--
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with
Yes, this seem to work (although it cant contain valid file:).
--
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.
