On 10/27/2010 08:37 AM, Tim wrote: Since the OP mentioned the IP address to be 192.168.3.30 I didn't see the need to bring all that up. -- "There's very good eating on one of these, you know." -- Eyeing the tortoise for tea (Terry Pratchett, Small Gods) 葛斯克 愛德華 / 台北市八 德路四段

On 10/27/2010 06:20 PM, Hiisi wrote: I have seen a router where if you wanted to use an IP address instead of a hostname you had to format the email address as user(a)[192.168.3.30] to prevent the router from trying to do a DNS lookup. -- I appoint you ambassador to Fantasy Island!!! 葛斯克 愛德華 / 台北市八德 路四段

On Wed, 2010-10-27 at 14:20 +0400, Hiisi wrote: When I tried to get my modem/router to email its logs to a computer in my LAN, and went through similar problems. The router would try to use the DNS servers it knew about (the ones the ISP sets up through DHCP), and obviously they couldn't resolve my LAN addresses. But, I gather from your first message that your router is a computer, not a device, so your problem ought to be different. I think you want to check that each computer in the equation can resolve its own name, and the other computer's. Avoid using "localhost" as part of the mail addresses. On my LAN, I have a DNS server that all the computers use, and it has all the local machine names in its records. It solved a lot of name issues, and freed me from ever having to mess around with hosts files, again. The [bracketing] the IP address after the @ sign ought to work, to use an IP address without name lookups, but I don't know if everything does that trick. Where are you seeing the error messages? The SMTP server logs from where you're trying to send from, trying to receive at, or something else? Later on you mention a "user unknown" error. Are you accidentally trying to send mail out using your ISP's SMTP server? -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.

On 10/27/2010 06:57 AM, Hiisi wrote: Look at your /etc/mail/access file. You will need to add the hostnames of all machines on your local network that you want to have access to your sendmail daemon. Do it on each machine. -- Kevin J. Cummings kjchome(a)rcn.com cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org)

Tim: Hiisi: The dig tool can be used to check DNS queries. But, you can probably just try pinging the hostnames, and look at what happens. e.g. Presuming a host was called "mail", issuing "ping mail" as a command would produce several lines of output. The first one would have the fully qualified domain name and IP address (that it finds out about), the next few lines the ping results. [tim@suspishus ~]$ ping mail PING mail.example.com (192.168.1.2) 56(84) bytes of data. 64 bytes from mail.example.com (192.168.1.2): icmp_seq=1 ttl=64 time=1.43 ms 64 bytes from mail.example.com (192.168.1.2): icmp_seq=2 ttl=64 time=1.19 ms ^C --- mail.example.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1414ms rtt min/avg/max/mdev = 1.192/1.313/1.435/0.126 ms If names and IP addresses are correct, then you'd expect that name resolution is working fine. The ping results (timewise) just show networking responses, not responses from any mail software. Well, to be honest, I find running a normal DNS server much much simpler than messing around with hosts files. It gives me central management of name resolution, which is particularly useful if I ever need to change anything. And for *proper* mail handling, it's essential. The hosts file is inadequate - it cannot handle MX enquires, for instance. I'm not sure if you need the full normal functionality to get local mail working, it's been years since I've tried to do mail with a crippled network setup. In the normal run of things, when you try to mail someone, the mail server will do a MX record lookup to find out what should handle the mail. i.e. If you try to mail johndoe(a)example.com, mail doesn't simply get passed off to example.com, a MX lookup is done on example.com to find the address for example.com's mail server. There are fallbacks for dealing with a lack of MX records, but how that's all handled will depend on your mail software. Old-timer's standard advice is "when you stop doing things the normal way, all bets are off." What tests are you trying? Obviously what you want to work isn't working, but what else are you trying to get mail to go through? The "mail" command line, a graphical mailer? First I'd try doing mail on each computer to itself, to see if that works. e.g. mail root@localhost Then, I'd try a similar test (still mailing itself), this time substituting the computer's own hostname. e.g. mail root@computer1 and, separately, mail root@computer2 Does sound rather like you're getting error messages back from different servers (in one case, your SMTP server talking to another). You could try disconnecting your LAN from the ISP to limit what's involved in the test. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.

On 10/27/2010 8:32 AM, Hiisi wrote: Which MAILER-DAEMON is sending the bounce? PK

On Thu, 2010-10-28 at 10:28 +0400, Hiisi wrote: On the machine that is trying to accept your emails (or the machine that sendmail is running on). Are you running a local dns for your private network? If not, might look at dnsmasq and/or also at least put in your hostnames/ip's to all your machines (if not that many) in your /etc/hosts file on all of them. Might help with recognizing hostnames and such. -- Mike Chambers Madisonville, KY "Best lil town on Earth!"

ke, 2010-10-27 kello 20:59 -0400, Kevin J. Cummings kirjoitti: <--SNIP--> OK, now I have: On F-12 router: cat /etc/mail/access Connect:localhost.localdomain RELAY Connect:localhost RELAY Connect:127.0.0.1 RELAY Connect:192.168.3.30 RELAY On 192.168.3.30 machine: cat /etc/mail/access Connect:localhost.localdomain RELAY Connect:localhost RELAY Connect:127.0.0.1 RELAY Connect:192.168.3.20 RELAY (192.168.3.20 is the addr of F12-eth2 on which 192.168.3.30 is connected) Now if I send mail to <user&gt;(a)192.168.3.30 it's returned with reason: 550 Host unknown. If I send message to <user&gt;(a)[192.168.3.30] then it's returned with reason: 553 5.3.5 system config error. And more over, the same message appears in root mailbox on 192.168.3.30 machine: Diagnostic-Code: SMTP; 553 5.3.5 system config error. What's next? I think there's the light at the end of this configure trouble, isn't it? -- There's the light at the end of the the Windows. -- Havlik Denis

On 10/27/2010 06:57 PM, Hiisi wrote: First, you haven't said what router you are using. While it sounds as if you will have to set up a local name server to properly resolve the hostname of 192.168.3.30 to its IP address you may want to consult the router's documentation and/or contact the manufacturer of the router. FWIW, I am assuming the error you reported is being seen in the logs of the router. -- ... I see TOILET SEATS ... 葛斯克 愛德華 / 台北市八德路四段

ke, 2010-10-27 kello 18:37 +0800, Ed Greshko kirjoitti: <--SNIP--> Failed :-( (reason: 550 5.7.1 <user@[192.168.3.30]>... Relaying denied. IP name lookup f ailed [192.168.3.20]) Any other suggestions? -- "The medium is the massage." -- Crazy Nigel

On 10/27/2010 12:57 PM, Hiisi wrote: Do you have the sendmail-cf package installed? It isn't installed by default and it is necessary to have it installed in order to remake the sendmail.cf. That detail is covered in the sendmail.mc file at the top.... -- Fine day for friends. So-so day for you. 葛斯克 愛德華 / 台北市八德路四段

On Wed, 2010-10-27 at 07:00 +0800, Ed Greshko wrote: Though, consider the following: Will that machine be accessible from outside your LAN? If so, you need to take anti-spam steps. Will that machine be accessible by (potentially) untrustworthy users within your LAN? The same precaution applies. What anti-spam steps could you take? You could limit SMTP server to only sending to local addresses, so it can't spam the outside world. You could limit it to only accepting connections from your LAN, so outsiders can't get in. You can use the detection of bogus/forged addresses for blocking transmission of spam. You can run anti-spam software that looks at message content, to block spam... -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.

Hiisi writes: What happens when you run: telnet 192.168.3.30 25