its excelent !
best practice to me seems SMTPCONF=reject:nohelo+notmxhelo.
greetz from germany ...
Yutaka Sato schrieb:
> I uploaded 9.2.4-pre14 including SMTP extension as follows which may be
> useful in your case:
>> SMTPCONF parameter* == SMTPCONF=what:conf
>> -- default: SMTPCONF=bgdatasize:64K
>> Reject the DATA or the session if a specified condition is true.
>> "nohelo" -- the client does not say "HELO"
>> "nofrom" -- the client does not say "MAIL FROM"
>> "pipeline" -- the client send command without waiting server's response
>> "nomx" -- the client's host does not have a MX record
>> "notselfmx" -- the client'host is not the MX of itself
>> "notmxhelo" -- the domain in the HELO is not the MX of the client's host
>> Multiple conditions can be specified concatenated with "+" as
> In message <_A3460@delegate-en.ML_> on 08/08/06(12:26:40) I wrote:
> |In message <_A3459@delegate-en.ML_> on 08/08/06(12:01:10) I wrote:
> | |In message <_A3458@delegate-en.ML_> on 08/08/06(01:27:31)
> | |you Martin Papadopoulos <firstname.lastname@example.org> wrote:
> | | |it would be awesome if you could implement an smtp reject for non mx
> | | |servers.
> | | |i mean that if the reverse lookup entry does not contain a valid MX
> | | |record, or
> | | |to satisfy scenario of multiple mx records on one IP to checkout the
> | | |helo domain if it has
> | | |an mx record.
> | | |
> | | |it is only a request though.
> | |
> | |Doing access control based on the (existence of) MX record seems useful
> | |and I'll support it in the next release.
> |I tested an extenstion like the enclosed patch with a parameter as follows:
> | RELIABLE="_MX.*"
> |It seems working as I expected to reject hosts without a MX record.
> |It will be able to be extended to "with A", "with AAAA", "with PTR" or so.
> 9 9 Yutaka Sato <email@example.com> http://delegate.org/y.sato/
> ( ~ ) National Institute of Advanced Industrial Science and Technology
> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller