On 2008-02-18 14:27:59 -0500, Charlie Brady wrote: > On Mon, 18 Feb 2008, Peter J. Holzer wrote: > >On 2008-02-16 18:27:21 -0500, Charlie Brady wrote: > >>However I stand by my original statement that qpsmtpd can (and should, and > >>I believe does, via require_resolvable_fromhost) *avoid* loops created by > >>MX records resolving to 0.0.0.0, so there is no need to detect the loop > >>which such a record creates with qmail. > > > >I probably missed something, but how does this avoid mail loops? > >require_resolvable_fromhost checks the domain name of the *sender*, > >which cannot cause a mail loop. > > It can, if a bounce is generated.
A bounce is a different message. > Or if the message is accepted and then replied to. This is also a different message (Also, a reply is usually sent to the Reply-To or From header, not the Return-Path, which may be - and often is - different). > >A mail loop would happen when the domain > >of the recipient resolves to 0.0.0.0 (or 127.0.0.1, or any other local > >address). > > Quite correct. So qpsmtpd should perhaps have require_resolvable_rcpthost. So write one. I won't stop stop you ;-). I just don't have a need for such a plugin myself for two reasons: 1) It only makes sense for outgoing mail, where I don't use qpsmtpd (yet). For incoming mail, all the recpient domains are known and under our control, so an MX of 0.0.0.0 cannot happen (and if does, we can fix it). 2) qpsmtd can only receive mails, not send them. For sending, we use postfix, which already does loop-detection. So duplicating it in qpsmtpd doesn't help much. > >This could be checked by the SMTP client, if necessary. > > It could, but we can't expect that it will be. It's under your control. If yours doesn't, feel free to write a plugin for qpsmtpd. -- _ | Peter J. Holzer | It took a genius to create [TeX], |_|_) | Sysadmin WSR | and it takes a genius to maintain it. | | | [EMAIL PROTECTED] | That's not engineering, that's art. __/ | http://www.hjp.at/ | -- David Kastrup in comp.text.tex
signature.asc
Description: Digital signature