OK, here's my setup, slightly different, but seems to be same issue. I have a production mail server it's working perfectly fine. I have a test server on the LAN 192.168.0.195 I want it to be able to send the logwatch e mails to my address on my production server, but I get this error.
Connected to 64.168.70.133 but sender was rejected. Remote host said: 511 sorry, can't find a valid MX for sender domain (#5.1.1 - chkuser) My understanding is that I can make these changes change my current tcp.smtp 127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1" :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1" to this 127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1" 192.168.0.195:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",RBLSMTPD="",NOP0FCHECK="1" :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1" run service qmail cdb And I should be able to send mail to the production. Is this the recommended way of doing this? I have tried and it doesn't work for me, but I will try again if this is the correct method. This is not critical nor necessary. This server will only be on the LAN for a few day. I really just want to know how it's correctly done. Eric Shubert wrote: > Aleksander Podsiadly wrote: >> W dniu 30.10.2009 18:32, Eric Shubert pisze: >>> While I agree with your position and hypothetical scenario, I don't >>> believe that adding an MX record for each host is the correct nor >>> best solution. >>> >>> I don't see any purpose in adding an MX record for each host that >>> sends email. [...] >>> >> That's right, have to be in DNS the MX record or A record for literal >> after ,,@''. >> > > I'm not (necessarily) disputing that. I believe that the sending > server should probably not have the host name included in the address > after the @. IE @host.domain.com should simply be @domain.com, and > this is configured on the sending server. > > One other point I'd like to make. If you create an MX record for > host.domain.com, shouldn't host.domain.com also be defined in your > toaster as local or alias domain? I would think it should. So now > you're talking about a configuration change in DNS and the toaster for > each host that's going to submit email, as opposed to (simply) > configuring each server to authenticate. The later seems simpler to me. > -- Cecil Yother, Jr. "cj" cj's 2318 Clement Ave Alameda, CA 94501 tel 1.510.865.2787 | fax 1.510.864.7300 http://yother.com --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
