Re: spamd -M behaviour when real MX is down
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 page). If this fails, the connection will be greytrapped. -martin 2 apr 2008 kl. 18.45 skrev Jose Fragoso: 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 initial stuttering (like in -S)? Thanks in advance. Regards, Jose -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
Re: spamd -M behaviour when real MX is down
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 connections itself. (from the man page). Yes. But the man page does not say how SPAMD would behave if the real MTA (high priority MX) is down. In such a situation, a remote host trying to deliver a message to a given domain, will try the real MTA first (and SPAMD will see this pass through). Since it is down, the host will next try to make an SMTP connection to the low-pri MX address, which is controlled by SPAMD, right? This is what my question is about. How will SPAMD react to this connection? Regards, Jose -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
Re: spamd -M behaviour when real MX is down
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 receiving the connections itself. (from the man page). Yes. But the man page does not say how SPAMD would behave if the real MTA (high priority MX) is down. In such a situation, a remote host trying to deliver a message to a given domain, will try the real MTA first (and SPAMD will see this pass through). Since it is down, the host will next try to make an SMTP connection to the low-pri MX address, which is controlled by SPAMD, right? 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) This is what my question is about. How will SPAMD react to this connection? If you don't have the other address (MX 10 in my example) it will just block the sender straight away.
Re: spamd -M behaviour when real MX is down
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 spamd (-M address) Now what happens when the mailhost is down? Will spamd politely drop the SMTP connection to its fake IP address? Will it delay the first 10 secs (-s)? Regards, Jose -- Want an e-mail address like mine? Get a free e-mail account today at www.mail.com!
