> I guess it could be possible, yes. > > - Davide I read this as "there is no way to do it NOW, but you're thinking that you could modify the code".
If this is the case, don't rush for a fix just for me, just add it to the list for next version. I've created a workaround. On my internal-view on my named server I created a dummy zone for the host.domain.com. This satisfies xmail's check and allows dns lookups for domain.com to the authoritative source. This works because it is not very likely that this domain will ever really use host.domain.com as a valid target email domain. Thanks, Rob :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Thursday, 11 May 2006 3:10 PM To: xmail@xmailserver.org Subject: [xmail] Re: CheckMailerDomain and lame postmasters On Thu, 11 May 2006, Rob Arends wrote: > Recently I enabled "CheckMailerDomain" "1" in SERVER.TAB. > To: > "Enable validation of the sender domain ('MAIL FROM:<[EMAIL PROTECTED]>') > by > looking up DNS/MX entries." > > All was doing the correct thing, until a user complained of no email > from a certain source. > > I found that the user had an email address elsewhere and had a rule > set to fwd any email to her account here. > Sounds simple and legit. > > The problem arose when those emails started getting "SNDR=ENODNS" in > the SMTP log. > > I found that the postmaster for the forwarding domain becomes the > sender in the server based fwd rule. > Again not a problem, except when they haven't set their postmaster > address correctly. > They use [EMAIL PROTECTED], where the usual domain for the > site is domain.com. > Obviously the 'host' part is the actual server (from a pool) that > processed the email. > > Now I've tried to talk to this company before to teach them the error > of their ways, but alas they are deaf. > > So I have to resort to a local solution. > I thought of SMTP.IPPROP.TAB > And set (example) "192.168.0.7/32" "WhiteList=1" > > But that did not work. The doco says: > WhiteList > If set to 1 and if the peer IP matches the address mask, all peer IP > based checks will be skipped. > > So perhaps this is not seen as an IP based check. > > SMTPRELAY.TAB might be another option, but I doubt it. > > For the moment I've disabled the CheckMailerDomain option, but I'd > really like to turn it on again. > > Davide, is there a way to WhiteList a server for ALL lameness checks, > or at least the CheckMailerDomain check? I guess it could be possible, yes. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
