Re: spamd -M behaviour when real MX is down

2008-04-03 Thread Martin Hedenfalk
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

Re: spamd -M behaviour when real MX is down

2008-04-03 Thread Jose Fragoso
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

Re: spamd -M behaviour when real MX is down

2008-04-03 Thread Stuart Henderson
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 it, or by

Re: spamd -M behaviour when real MX is down

2008-04-03 Thread Jose Fragoso
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 10