11-05-2008
More info
I did a
#sendmail -Ac -v -q
and received this response
Running /var/spool/clientmqueue/mA55486v005844 (sequence 1 of 2)
u.com.my: Name server timeout
xxx@x.com.my... Transient parse error -- message queued for future delivery
Running /var/spool/clientmqueue/mA4A10Gm004805 (sequence 2 of 2)
u.com.my: Name server timeout
xxx@x.com.my... Transient parse error -- message queued for future delivery
u.com.my: Name server timeout
xxx@x.com.my... Transient parse error -- message queued for future delivery
There is no DNS server configured.
root@xxxx $ nslookup mailserver
;; connection timed out; no servers could be reached
10 More Discussions You Might Find Interesting
1. Solaris
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
2. UNIX for Dummies Questions & Answers
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
3. Solaris
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
4. Solaris
Hi all,
we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent..
Thanks in advance.. (1 Reply)
Discussion started by: bpsunadm
1 Replies
5. Red Hat
Hi Gurus,
I have been tampering around with sendmail for the past one week and seem to make little progress. Given below is an abstract of the issue.
I have a Fedora 12 server(A VM on vitual Box bridged with a Windows XP host) which has to act as a SMTP server and have accordingly put up the... (8 Replies)
Discussion started by: Hari_Ganesh
8 Replies
6. AIX
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
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
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
Hi All,
I have Solaris-10 box with 11 sparse root zone. After a upgrade activity and reverted back due to some issues, sendmail is not working on any of the Non Global Zone (NGZ), while it works fine on Global zone
root@trans01-zd01:/root# mailx -v my_email_id@xxxx.com
Subject: ZD01
.
EOT... (4 Replies)
Discussion started by: solaris_1977
4 Replies
10. UNIX for Advanced & Expert Users
One of the applications sends mail to the users on daily basis. It sends mail within (internal users) the firewall (e.g., username@companyname.com) and not sending mail outside (external users) the firewall (e.g., username@yyyy.com). When we contacted the admin people they informed us to register... (5 Replies)
Discussion started by: abuibi
5 Replies
AGR(4) BSD Kernel Interfaces Manual AGR(4)
NAME
agr -- link aggregation pseudo network interface driver
SYNOPSIS
pseudo-device agr
DESCRIPTION
The agr driver provides link aggregation functionality (a.k.a. L2 trunking or bonding).
It supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol.
The agr driver supports the following link specific flags for ifconfig(8):
link0 Use the round-robin distribution algorithm. Don't use it unless you're really sure, because it violates the frame ordering rule.
-link0 Use the default distribution algorithm, which is based on the hash of DA/SA, TCI, and, if available, some upper layer protocol infor-
mation like ip(4) DA/SA.
link1 Disable LACP. Prevents any LACP or Marker messaging which leaves the ports in the default static configuration. Set this prior to
adding ports.
EXAMPLES
Create an agr interface, agr0, and attach re0 and re1 to it. In other words, aggregate re0 and re1 so that they can be used as a single
interface, agr0. The physical interfaces which are attached to the agr interface must not have any IP addresses, neither IPv4 nor IPv6.
ifconfig re0 inet xxx.xxx.xxx.xxx delete
ifconfig re0 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig re1 inet xxx.xxx.xxx.xxx delete
ifconfig re1 inet6 fe80::xxxx:xxxx:xxxx:xxxx delete
ifconfig agr0 create
ifconfig agr0 agrport re0
ifconfig agr0 agrport re1
Destroy an interface created in the above example.
ifconfig agr0 -agrport re0
ifconfig agr0 -agrport re1
ifconfig agr0 destroy
SEE ALSO
ifconfig(8)
STANDARDS
IEEE 802.3ad Aggregation of Multiple Link Segments
HISTORY
The agr driver first appeared in NetBSD 4.0.
AUTHORS
The agr driver was written by YAMAMOTO Takashi.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation of the agr
driver always performs active-mode LACP and uses 0x8000 as system and port priorities.
The agr driver uses the MAC address of the first-added physical interface as the MAC address of the agr interface itself. Thus, removing the
physical interface and using it for another purpose can result in non-unique MAC addresses.
The current implementation of the agr driver doesn't prevent unsafe operations like some ioctls against underlying physical interfaces. Such
operations can result in unexpected behaviors, and are strongly discouraged.
There is no way to configure agr interfaces without attaching physical interfaces.
Physical interfaces being added to the agr interface shouldn't have any addresses except for link level address. Otherwise, the attempt will
fail with EBUSY. Note that it includes an automatically assigned IPv6 link-local address.
BSD
February 23, 2010 BSD