Stupid list automatically replying to author not list... :-) On Fri, Jun 29, 2001 at 12:12:40PM -0700, Joost van der Lugt wrote:
o I have a dialup connection, so the obvious choice for sendmail setup is "host with temporarily(sic) network connection". However, this leaves my machine as an open SMTP relay.
Mmm, I would be very surprised if it does, what makes you think so?
Yast says "Anti-spam measures not available in deferred delivery mode" or something similar. Also, I tried telnetting to port 25, and it will relay mail without question.
Since I'm online 10+ hours a day, with a (relatively) high-speed ISDN connection, this is obviously not acceptable. If I choose "host with permanent network connection", sending mail is very slow, as I have to wait for it to time out on DNS requests. How can this be fixed?
Square brackets around the smarthost or ip [], avoids DNS lookups.
Thanks, will try that.
o The most bizarre problem: I use a masqueraded connection to the net, so I use Sendmail to re-write my domain address from the local name (machinename.djsnet) to my mail forwarding domain (ds-electronics.co.uk). This was working perfectly until I built the new DNS server. Now, when I try to send a mail, Sendmail tries to connect to my ISP and send with a rubbish domain name containing "*LOCAL*". The interesting thing about this is that it only happens if I have a working DNS zone for my local network (djsnet). If I break my DNS setup, sendmail works fine. It appears that it was only working before because my DNS setup was broken. I enclose a bounced mail. In case you're wondering: holly.djsnet is the local machine name demon.co.uk is my ISP gazpacho.demon.co.uk the name of my masqueraded machine on the internet ds-electronics.co.uk is my intended From: address - it is a mail forwarding service.
Well, this ain't sendmail setup:)
Check if you've filled in the domains correctly, you may have forgotten to put a dot behind the entries: [snip]
Since all my other domain lookups (nslookup, ping, ssh, etc.) work fine, I was thinking that it's not a problem with the DNS setup. ATM, I'm leaning towards a problem with my resolv.conf; I've got some things to try first, but if that doesn't work, I'll be back... Thanks for your help...