Sponsored Content
Full Discussion: Emails issue
Operating Systems Solaris Emails issue Post 302823365 by Junaid Subhani on Wednesday 19th of June 2013 07:35:32 AM
Old 06-19-2013
Wrench Emails issue

Dear all,
I am facing an issue in my data Center environment related to mails being generated by users on my machines.

Let me walk you through the issue one by one.

Each system (100+ servers in my DC) has a user sysmon on it that sends mails to a specific Email ID. The user runs scripts related to system monitoring i.e. scripts monitoring disk space , system health etc.

Example name of 2 systems are mercury0 & mercury1

The scripts work fine and send Emails to the ID given.

The issue arises when the /var/spool/mqueue directory on my MTA Relay host servers starts to increase with Emails being stuck in them.

Those emails are addressed to the system's own users.
Mercury0 is sending an Email to itself using sysmon ID.

Example of two mail outputs found on my MTA Relay host servers are below:

I did did the following on the /var/spool/mqueue directory on one of my MTA Relay host servers:

Code:
sudo cat * | grep sysmon | grep mercury0

Code:
H??To: sysmon@mercury0.domain.com

H??To: sysmon@mercury1.domain.com

How can I make sure that such mails do not pile up in the /var/spool/mqueue directory of my MTA Relay host servers?
Is there a way to make sure such mails being addressed to a systems own ID be forwarded to another Email ID but hte best option would be to simply discard them.


P.S. I have placed the IP address of MTA Host servers in the submit.cf file on all client machines.

Regards

Last edited by Junaid Subhani; 06-19-2013 at 08:43 AM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

send emails to groups

Hi, I am trying to send alert emails through my script to users using a group name like DL_Failure Group@company.com but I am not able to send it, I thought it is because of the space in between and I tried to sedn is with quotes "DL_Failure Group@company.com" but that too did not work....I... (2 Replies)
Discussion started by: mgirinath
2 Replies

2. UNIX for Dummies Questions & Answers

Creating emails

Hi, I posted here 2 months ago, saying I wanted to learn UNIX for my work running a small ISP. I had the problem of practically no technical support for our system. Many courses later, I can just about do everything I need to do. The server is a FreeBSD i386. I can now create email accounts for... (4 Replies)
Discussion started by: ferret495
4 Replies

3. UNIX for Dummies Questions & Answers

duplicate emails

Hi all new here. Question. My mail server is sending out duplicate emails but its not system wide. We have several virtual host that use our email server and some are having the duplicate emails issue and some are not. For example in the office some people are getting duplicate emails but i am... (1 Reply)
Discussion started by: mcraul
1 Replies

4. UNIX for Dummies Questions & Answers

Emails on HP-UX

Hi Guys I am running Oracle database on HP-UX, every now and then I get emails that are sent to me by root. When check with the sysadmin know one have a clue as to where does the emails come from. I need to stop this emails...how do I check which script is sending me the emails. Thanks ... (0 Replies)
Discussion started by: Phuti
0 Replies

5. Solaris

Adding a footer to all emails

I am running Solaris 10 and have been asked to create a footer for all emails that go from the server. I have been looking around but no dice. I am not sure how complicated or easy it is to do it. Our system generates emails every night and then sends them out to different people on the list. We... (0 Replies)
Discussion started by: Sucio
0 Replies

6. Shell Programming and Scripting

examples of hyperlinks in emails

Hi All, Im using bash on a sloaris box. I am using mailx to send emails from the unix box to internal email accounts. Does anyone have an example of how I can generate a hyperlink within the email body so that when the recipeint recieves the email, they can click on the link and the link... (1 Reply)
Discussion started by: satnamx
1 Replies

7. UNIX for Dummies Questions & Answers

.forward for forwarding emails

Hi, I want to forward my emails to a different email account on Unix. I created a .forward file with just one line in it. forward_to@yahoo.com The emails are not getting forwarded to the forward_to email address, instead they are going to my original inbox. Is it required that I run the... (1 Reply)
Discussion started by: foxtron
1 Replies

8. UNIX for Dummies Questions & Answers

send emails

hi guys I need to send emails to some accounts 1. I need sendmail up and running right? 2. I need my local sendmail to use an existing SMTP server to send emails (10.x.x.x)? in that case what I need to configure to send emails? since using mail myaccount@companyame.com is not sending emails... (3 Replies)
Discussion started by: karlochacon
3 Replies

9. Shell Programming and Scripting

extracting emails from a file

i have a large html file that has emails like something@domain.com and somethingdomain.com how can i print the emails? its fine if duplicates show up and it doesnt need to save into a file or anything, just whatever is the easiest way to make some basic code for this thanks! :) (2 Replies)
Discussion started by: vanessafan99
2 Replies

10. Debian

Problem sending out emails

Hi, Our email relay server is a debian server. The application team in our company regularly receives email alerts from one hpux server (which is routed through the email relay server). Today we had problems whereby our company's email recipients are not receiving email alerts from the hpux... (2 Replies)
Discussion started by: anaigini45
2 Replies
Email::Send::Test(3pm)					User Contributed Perl Documentation				    Email::Send::Test(3pm)

NAME
Email::Send::Test - Captures emails sent via Email::Send for testing SYNOPSIS
# Load as normal use Email::Send; use Email::Send::Test; # Always clear the email trap before each test to prevent unexpected # results, and thus spurious test results. Email::Send::Test->clear; ### BEGIN YOUR CODE TO BE TESTED (example follows) my $sender = Email::Send->new({ mailer => 'Test' }); $sender->send( $message ); ### END YOUR CODE TO BE TESTED # Check that the number and type (and content) of mails # matched what you expect. my @emails = Email::Send::Test->emails; is( scalar(@emails), 1, 'Sent 1 email' ); isa_ok( $emails[0], 'Email::MIME' ); # Email::Simple subclasses pass through DESCRIPTION
Email::Send::Test is a driver for use in testing applications that use Email::Send to send email. To be able to use it in testing, you will need some sort of configuration mechanism to specify the delivery method to be used, or some other way that in your testing scripts you can convince your code to use "Test" as the mailer, rather than "Sendmail" or another real mailer. How does it Work Email::Send::Test is a trap for emails. When an email is sent, it adds the emails to an internal array without doing anything at all to them, and returns success to the caller. If your application sends one email, there will be one in the trap. If you send 20, there will be 20, and so on. A typical test will involve doing running some code that should result in an email being sent, and then checking in the trap to see if the code did actually send out the email. If you want you can get the emails out the trap and examine them. If you only care that something got sent you can simply clear the trap and move on to your next test. The Email Trap The email trap is a simple array fills with whatever is sent. When you send an email, it is pushed onto the end of the array. You can access the array directly if you wish, or use the methods provided. METHODS
send $message As for every other Email::Send mailer, "send" takes the message to be sent. However, in our case there are no arguments of any value to us, and so they are ignored. It is worth nothing that we do NOTHING to check or alter the email. For example, if we are passed "undef" it ends up as is in the trap. In this manner, you can see exactly what was sent without any possible tampering on the part of the testing mailer. Of course, this doesn't prevent any tampering by Email::Send itself :) Always returns true. emails The "emails" method is the preferred and recommended method of getting access to the email trap. In list context, returns the content of the trap array as a list. In scalar context, returns the number of items in the trap. clear The "clear" method resets the trap, emptying it. It is recommended you always clear the trap before each test to ensure any existing emails are removed and don't create a spurious test result. Always returns true. deliveries This method returns a list of arrayrefs, one for each call to "send" that has been made. Each arrayref is in the form: [ $mailer, $email, @rest ] The first element is the invocant on which "send" was called. The second is the email that was given to "send". The third is the rest of the arguments given to "send". SUPPORT
All bugs should be filed via the CPAN bug tracker at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Email-Send-Test> For other issues, or commercial enhancement or support, contact the author. AUTHORS
Current maintainer: Ricardo SIGNES, <rjbs@cpan.org>. Original author: Adam Kennedy <cpan@ali.as>, <http://ali.as/> COPYRIGHT
Copyright (c) 2004 - 2005 Adam Kennedy. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.12.4 2011-08-31 Email::Send::Test(3pm)
All times are GMT -4. The time now is 03:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy