Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Sendmail issue on NGZ (Solaris) Post 302584472 by vishalaswani on Friday 23rd of December 2011 10:15:18 AM
Old 12-23-2011
Please check local_only parameter for sendmail through below command
Code:
 
svcprop sendmail | grep local_only

This must be set to false to allow remote access.

Regards,
Vishal
 

10 More Discussions You Might Find Interesting

1. Linux

Sendmail issue

Hi gurus! I need help to make sendmail to accept unknown user mail. That is if the user does not exist sendmail keep on processing the mail and store it in a some mailbox ... Thanks for any idea! (5 Replies)
Discussion started by: andryk
5 Replies

2. Solaris

Solaris sendmail issue

I am trying to send mail from a Solaris 10 machine to myself. The mail will be receive by a mail server. The problem is sendmail doesn't report any errors and there is nothing in mailq output. In the logs the stat=queued. I do not receive the mail in my mailbox. I could telnet to the... (7 Replies)
Discussion started by: sundar63
7 Replies

3. Solaris

sendmail issue

Hi, yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email, This happened with sendmail on solaris 10 and also with sendmail on a linux box. Found it is something to do with DNS blacklists, following lists did not work for me,... (2 Replies)
Discussion started by: upengan78
2 Replies

4. UNIX for Dummies Questions & Answers

Issue with sendmail

Hi Team, I have a script written to sendmail along with attachment in html format. The code is export MAILFROM="abc@abc.com" export MAILTO="abc@abc.com" export CONTENT="./GRP_SPI_ERR.html" export SUBJECT="TEST EMAIL: TESTING HTML" { print - "From: $MAILFROM" print - "To: ${MAILTO}"... (3 Replies)
Discussion started by: Vinaykumar1
3 Replies

5. Solaris

Sendmail Issue

Hi, Guru i had configure in my two server to send out the email. One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all. below is the syslog when i try to send out the mail. GOOD Server Dec 28 11:29:39... (5 Replies)
Discussion started by: SmartAntz
5 Replies

6. AIX

Sendmail issue

My aix boxes have the port 25 listening and I want to bock that. But before that I want to check the recent logs of the sendmail activity and any open sockets using the port. Please advise. (1 Reply)
Discussion started by: ranasarkar
1 Replies

7. Red Hat

Sendmail issue

Hi Every One, one of our server configuration on sendmail config we are using SMAR_HOST ### define(`SMART_HOST', 'mail.xxx.com') and /etc/sysconfig/sednmail DAEMON is setted to NO so let me know why sendmail is not working for this server any this else u need please do let me know (0 Replies)
Discussion started by: venikathir
0 Replies

8. Solaris

sendmail issue on solaris 9

We changed relay agent in sendmail.cf and submit.cf files, and restarted the send mail services from init.d, able to see the sendmail processes. But unable to send an email. Relay agent is telnetable with port 25. Please help us with the issue (2 Replies)
Discussion started by: sudhakar110
2 Replies

9. Emergency UNIX and Linux Support

Sendmail issue

Hi, I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Discussion started by: maverick_here
3 Replies

10. Red Hat

Sendmail issue

Dear All , I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine. But suddenly there was an issue , the SMTP takes the IP of the bond1 interface. So the IP could not get validated in the relay server. So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
zone2ldap(1)						      General Commands Manual						      zone2ldap(1)

NAME
zone2ldap /- Load BIND 9 Zone files into LDAP Directory SYNOPSIS
zone2ldap [-D Bind DN] [-w Bind Password] [-b Base DN] [-z Zone] [-f Zone File ] [-h Ldap Host] [-cd] [-v] DESCRIPTION
zone2ldap will parse a complete BIND 9 format DNS zone file, and load the contents into an LDAP directory, for use with the LDAP sdb back- end. If the zone already exists, zone2ldap will exit succesfully. If the zone does not exists, or partially exists, zone2ldap will attempt to add all/missing zone data. Options -b LDAP Base DN. LDAP systems require a "base dn", which is generally considered the LDAP Directory root. If the zone you are loading is different from the base, then you will need to tell zone2ldap what your LDAP base is. -v Print version information, and immediatly exit. -f Zone file. Bind 9.1 compatible zone file, from which zone information will be read. -d Dump debug information to standard out. -w LDAP Bind password, corresponding the the value of "-b". -h LDAP Directory host. This is the hostname of the LDAP system you wish to store zone information on. An LDAP server should be lis- tening on port 389 of the target system. This may be ommited, and will default to "localhost". -c This will create the zone portion of the DN you are importing. For instance, if you are creating a domain.com zone, zone2ldap should first create "dc=domain,dc=com". This is useful if you are creating multiple domains. -z This is the name of the zone specified in the SOA record. EXAMPLES
Following are brief examples of how to import a zone file into your LDAP DIT. Loading zone domain.com, with an LDAP Base DN of dc=domain,dc=com zone2ldap -D dc=root -w secret -h localhost -z domain.com -f domain.com.zone This will add Resource Records into an ALREADY EXISTING dc=domain,dc=com. The final SOA DN in this case, will be dc=@,dc=domain,dc=com Loading customer.com, if your LDAP Base DN is dc=provider,dc=net. zone2ldap -D dc=root -w secret -h localhost -z customer.com -b dc=provider,dc=net -f customer.com.zone -c This will create dc=customer,dc=com under dc=provider,dc=net, and add all necessary Resource Records. The final root DN to the SOA will be dc=@,dc=customer,dc=com,dc=provider,dc=net. SEE ALSO
named(8) ldap(3) http://www.venaas.no/ldap/bind-sdb/ BUGS
Send all bug reports to Jeff McNeil <jeff@snapcase.g-rock.net> AUTHOR
Jeff McNeil <jeff@snapcase.g-rock.net> 8 March 2001 zone2ldap(1)
All times are GMT -4. The time now is 09:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy