On Wed, 22 Aug 2007, Rense Buijen wrote:
> I didn't know that a backup MX can lead to more trouble then
> having just one, gee, I thought it was a good thing but it turned
> out to be a quite bad one :)
It *is* a good idea. You just can't cheap out on configuring it.
Ideally, your backup MXs sh
On 8/22/07, Rense Buijen <[EMAIL PROTECTED]> wrote:
>
> Thanks a lot all, it's all clear to me now!
> I though that the trusted networks mean that the message will just be
> passed it it came from that source.
> I didnt know it will skip to the next "Received" IP. Thanks a lot.
>
> One question abo
Rense Buijen wrote on Wed, 22 Aug 2007 16:43:19 +0200:
> I didn't know that a backup MX can lead to more trouble then having just
> one
Unfortunately, backup MXes attract spammers :-(. You could at least add
some more backup MXs (that don't exist) on top of that, that may help to
reduce the in
Rense Buijen wrote:
> Thanks a lot all, it's all clear to me now!
> I though that the trusted networks mean that the message will just be
> passed it it came from that source.
> I didnt know it will skip to the next "Received" IP. Thanks a lot.
>
> One question about the "backscatter" problem thou
Hi Kai,
I didn't know that a backup MX can lead to more trouble then having just
one, gee, I thought it was a good thing but it turned out to be a quite
bad one :)
I'll go and use LDAP on the second MX to make sure the remote user
exists, otherwise drop it silently.
It's indeed getting a bit o
Rense Buijen wrote on Wed, 22 Aug 2007 16:01:09 +0200:
> I think Exchange is configured the right way
> in such a way that it knows what users it has on the system..
But your backup MX doesn't. As you say you are taking in all mail, forward
it to primary and then bounce it back to the sender. B
Thanks a lot all, it's all clear to me now!
I though that the trusted networks mean that the message will just be
passed it it came from that source.
I didnt know it will skip to the next "Received" IP. Thanks a lot.
One question about the "backscatter" problem though, if I understand
correctl
Rense Buijen wrote:
> Mathhias,
>
> The problem is that when the mail enters the backup MX, we dont know
> if that mail is blacklisted at for instance spamcop.
> So if the backup mx accepts the mail (because it's dumb and it will
> accept it), and my primary mx (SA) has set the backup mx as truste
Thats the one
Ben
On 8/22/07, Rense Buijen <[EMAIL PROTECTED]> wrote:
>
> ...thats it? So it will skip the IP of the second MX and do an RBL check
> against the IP who'm delivered it to the second MX? COOL! I thought it
> would just ignore everything and pass on the mail Thanks!
>
> Ben O'Har
Mathhias,
The problem is that when the mail enters the backup MX, we dont know if
that mail is blacklisted at for instance spamcop.
So if the backup mx accepts the mail (because it's dumb and it will
accept it), and my primary mx (SA) has set the backup mx as trusted
network/source, the mail w
Hi Pawel,
I dont think I can check the recipient, if it doesnt exist the
mailserver should send a normal bounce like every mailserver does,
right? So does the primary machine (Exchange) I dont see a problem with
that.
Do you know if there is another good setup without having to sync all my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rense Buijen schrieb:
> Thank you for your (quick) reply.
> I cannot utilize the trusted_networks settings because I cannot trust
> the mail that my backup MX sends to me.
But your backup MX is "trusted" in the sense that it will not forge
sender a
Hi Matthias,
Thank you for your (quick) reply.
I cannot utilize the trusted_networks settings because I cannot trust
the mail that my backup MX sends to me.
The backup MX does NO filtering at all, it just accepts ALL mail that
has a certain destination domain and then forwards it to the Prima
Hi
I cannot utilize the trusted_networks settings because I cannot trust
the mail that my backup MX sends to me.
The backup MX does NO filtering at all, it just accepts ALL mail that
has a certain destination domain and then forwards it to the Primary
MX where SA is running, SA is doing all t
Hi Matthias,
Thank you for your (quick) reply.
I cannot utilize the trusted_networks settings because I cannot trust
the mail that my backup MX sends to me.
The backup MX does NO filtering at all, it just accepts ALL mail that
has a certain destination domain and then forwards it to the Prima
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rense Buijen schrieb:
> The problem now lies with the RBL's, when the SA box dies, the mail will
> be queued on my Exim box and when service is restored, it will forward
> it again BUT the last "Received from:" path will be of course the Exim
> host
16 matches
Mail list logo
