Yes, it looks correct, is correct, the access.db
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Saturday, February 19, 2005 12:27 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer Hmm, it looks like the makemap command is smarter than I thought. If you don't specify a filename that ends in .db, it silently adds that to the output file name. If you do specify it .db on the end, it uses it. Without that added checking, doing some sort of command that reads in a file and writes back out to the same file, you normally wind up with a very empty file. Once I ran it, I did a "strings /etc/mail/access.db" command, and it showed me the various entries I had put into /etc/mail.access. Does yours do that? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Patrick B. O'Brien Sent: Friday, February 18, 2005 7:51 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer yes per my documentation, how should I have done it? -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Post, Mark K Sent: Friday, February 18, 2005 1:14 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer This looks like a recipe for disaster: makemap hash /etc/mail/access < /etc/mail/access Did you really specify the same file twice? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Patrick B. O'Brien Sent: Friday, February 18, 2005 3:15 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer I did, same error. [EMAIL PROTECTED]:/etc/mail # makemap hash /etc/mail/access < /etc/mail/access [EMAIL PROTECTED]:/etc/mail # /etc/init.d/sendmail start Starting sendmail: [EMAIL PROTECTED]:/etc/mail # /etc/init.d/sendmail restart Shutting down sendmail: [ OK ] Shutting down sm-client: [ OK ] Starting sendmail: [ OK ] Starting sm-client: [ OK ] [EMAIL PROTECTED]:/etc/mail # [EMAIL PROTECTED] on 2/18/2005 12:14 PM You do not have permission to send to this recipient. For assistance, contact your system administrator. <MX1.STATE.NV.US #5.7.1 smtp;550 5.7.1 <[EMAIL PROTECTED]>... Relaying denied> -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Friday, February 18, 2005 12:03 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer Did you re-hash the database after updating the file? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Patrick B. O'Brien Sent: Friday, February 18, 2005 2:59 PM To: [email protected] Subject: Re: sendmail relaying denied error, bummer Like this? Still no joy,thank you! [EMAIL PROTECTED]:/etc/mail # cat access # Check the /usr/share/doc/sendmail/README.cf file for a description # of the format of this file. (search for access_db in that file) # The /usr/share/doc/sendmail/README.cf is part of the sendmail-doc # package. # # by default we allow relaying from localhost... localhost.localdomain RELAY localhost RELAY 127.0.0.1 RELAY toulon.state.nv.us RELAY humboldt.state.nv.us RELAY lahontan.state.nv.us RELAY marlette.state.nv.us RELAY 10.131.0.0 RELAY [EMAIL PROTECTED]:/etc/mail # -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Friday, February 18, 2005 5:29 AM To: [email protected] Subject: Re: sendmail relaying denied error, bummer > I'm seeing the following on a fresh install of Sendmail 8 SuSe Server. > Any thoughts and thank you Normal/Working As Designed. You have to explicitly tell sendmail what IP addresses are permitted to use or relay through it, including your own. YaST has a panel to do this (in network services configuration), or... Update /etc/mail/access to include your IP address ranges and any other IP addresses that should be allowed to relay, cd /etc/mail/access, make. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
