Hi Stuart,
> If you run spamd -M then you must have more than one IP address
> that is handled by spamd.
> e.g.
> MX 0 mailhost
> MX 10 spamd
> MX 20 spamd (-M address)
Sorry. I forgot to explain. My spamd box is running as a bridge.
So it is not an MX. The correct setup is:
MX 0 mailhost
MX
On 2008-04-03, Jose Fragoso <[EMAIL PROTECTED]> wrote:
>> The real MTA is not involved here. What's important is that "spamd with
> the
>> low priority MX address active must see all the greylist changes for a
>> higher priority MX host for the same domains, either by being synchro-
>> nised with
Hi, Martin!
Thanks for your reply.
> The real MTA is not involved here. What's important is that "spamd with
the
> low priority MX address active must see all the greylist changes for a
> higher priority MX host for the same domains, either by being synchro-
> nised with it, or by receiving the
Hi,
The real MTA is not involved here. What's important is that "spamd
with the
low priority MX address active must see all the greylist changes for a
higher priority MX host for the same domains, either by being synchro-
nised with it, or by receiving the connections itself". (from the man
Hi,
Since I am not able to test this now in the real world, I
would like to know how would spamd behave when it
received SMTP connections to a fake low priority MX
address and the real MTA was unavailable at the time.
I mean, would the connection be rejected with error 450?
Would there be any in
5 matches
Mail list logo
