My apologies to anyone looking at this in the archives and wondering why I seem to be responding to a non-existent email. Howard didn't feel that his email was worth archiving, even thous the replies are going to be archived.
On 13/06/07, Howard Lowndes <[EMAIL PROTECTED]> wrote:
I have a Linux/Postfix server that accepts email from the Internet, performs filtering checks on the email and then forwards acceptable emails onto a Linux/Domino server on the local intranet. The Postfix checks are all being done by LDAP so I am able to see what is happening on the Linux/Postfix server. Postfix has the relayhost parameter set in main.cf to point to the Linux/Domino server so that emails are correctly forwarded on. I can see the Linux/Postfix server doing all the checks that I have specified in main.cf. These include: smtpd_client_restrictions smtpd_helo_restrictions smtpd_sender_restrictions smtpd_recipient_restrictions However, the smtpd_recipient_restrictions appear to be failing safe with a default DUNNO result rather than a default REJECT result. The same checks, when not used in conjunction with a relayhost setting appear to default fail as REJECT rather than DUNNO. Am I right in assuming that the use of the relayhost parameter is causing this change in default behaviour, and how is the best way to fix it?
The Domino machine, being the real MTA, obviously knows what addresses it's going to accept mail for (the ones that are defined as valid addresses) and which it's going to reject (the rest - unless it has a catchall, in which case, there aren't any that it will reject). Does the Postfix machine have some way of knowing this same information, or is it just left knowing that "all mail for that domain gets forwarded to 1.2.3.4"? -- There is nothing more worthy of contempt than a man who quotes himself - Zhasper, 2004 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
