Sponsored Content
Full Discussion: Emails issue
Operating Systems Solaris Emails issue Post 302824005 by hasan.kamali on Thursday 20th of June 2013 05:42:25 AM
Old 06-20-2013
Hi,

I'm Junaid Subhani's team member. Let me further clarify our email architecture for our system email alerts.

All unix/linux machines sendmail client is set to use two MTA relay sendmail servers internally in our network.

Then those two MTA relay sendmail servers forwards all the email to our company's microsoft exchange server (Microsoft servers are managed and administered by a seperate windows team).

Then mircosoft exchange server delivers the system alerts to valid microsoft exchange email IDs, e.g. xyz@waridtel.com.

So basically submit.cf of all the client machines has the IP address of internal network MTA relay sendmail server and MTA sendmail relay server has the IP of Microsoft exchange server for D{MTAHost} in submit.cf.

All the system email alerts configured by us and different application/database team (in their scripts) is properly being delivered.

Now the problem we are facing is this. Along with all the system alerts emails, all of the sendmail client machines are also sending out native OS users system generated emails (to the native user ) as well. And ...... our internal network MTA relay sendmail server obviously also relay them to our domain's microsoft exchange server, which obviously cannot recognize the destination address (e.g. user@server-hostname.waridtel.com) floods our outbound email gateway (sendmail server) with all those unwanted emails and overwhelms the mail queue.

So far, we concluded to use '.forward' option to at least deliver all the emails to proper email address (xyz@waridtel.com) of the respective owner team of the unix/linux system user. That way our corporate outbound sendmail email gateway will not be brought down due to 100,000+ unwanted system users email everyday.

Another option we have read somewhere is to configure /etc/mail/access file on the internal MTA relay sendmail server, which would discard or reject any email addressed to user@server-hostname.warditel.com. But we are not sure about the syntax to be used. Whether we can use wild card options to reject/discard all emails addressed to user@server-hostname.waridtel.com or we have to add lines for each and every user of all the servers.
 

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
TMAIL(1)						      General Commands Manual							  TMAIL(1)

NAME
tmail - Mail Delivery Module SYNOPSIS
tmail [-b format] [-D] [-f from_name] [-I inbox_specifier] user[+folder] ... DESCRIPTION
tmail delivers mail to a user's INBOX or a designated folder. tmail may be configured as a drop-in replacement for binmail(1), mail.local(1) or any program intended for use for mail delivery by a mail delivery program such as sendmail(8). tmail is intended to be used for direct delivery by the mailer daemon; dmail(1) is the preferred tool for user applications, e.g. a mail delivery filter such as procmail(1). If tmail is used for a user application, then the calling program must be aware of the restrictions noted below. When tmail exits, it returns exit status values to enable the mail delivery program to determine whether a message was delivered successfully or had a temporary (requeue for later delivery) or permanent (return to sender) failure. If the +folder extension is included in the user argument, tmail will attempt to deliver to the designated folder. If the folder does not exist or the extension is not included, the message is delivered to the user's INBOX. If delivery is to INBOX and no INBOX currently exists, tmail will create a new INBOX, using the -I or -b flag if specified. tmail recognizes the format of an existing INBOX or folder, and appends the new message in that format. The -b flag specifies a format to create INBOX if INBOX does not already exist. This flag requires privileges, and can not be used with -I. The argument is a format name such as mix, mbx, etc. The -D flag specifies debugging; this enables additional message telemetry. The -f or -r flag is used by the mail delivery program to specify a Return-Path. The header Return-Path: <from_name> is prepended to the message before delivery. The -I flag is used by the mail delivery program to specify an alternative INBOX name. This flag requires privileges, and can not be used with -b. This affects the location and format of INBOX. If specified, it should be in one of three forms: The first form of argument to -I is the string "INBOX", which means to write to the system default inbox using the system default mailbox format. These system defaults are defined when the c-client library is built. The second form of argument to -I is a delivery specification, consisting of "#driver.", a c-client mailbox format driver name, "/", and a file name. This will write to the specified file in the specified format. For example, #driver.mbx/INBOX will write to file "INBOX" in the home directory in mbx format; and #driver.unix/mail/incoming will write to file "incoming" in the user's "mail" subdirectory in unix (default UNIX) format. The third form of argument to -I is any other name. Normally, this will write to the specified file on the user's home directory in the specified format. However, certain names are special. These are: value equivalant to ----- ------------- INBOX.MTX #driver.mtx/INBOX.MTX mbox #driver.unix/mbox mail.txt #driver.tenex/mail.txt If -I is not specified, the default action is -I INBOX. If multiple recipients are specified on the command line, tmail spawns one child process per recipient to perform actual delivery. This way of calling tmail is not recommended; see below under RESTRICTIONS. INSTALLATION
If tmail is to be used for mail delivery from the mail delivery program, it must be installed setuid root. If sendmail is the mail delivery program, tmail is invoked from sendmail.cf. Look for the "Mlocal" line, and substitute the path name for the tmail binary in place of /bin/mail, /usr/lib/mail.local, etc. You should also add the flag to invoke tmail with CRLF style newlines; this is usually done with E= in the Mlocal line. Here is an example of an Mlocal line in sendmail version 8: Mlocal, P=/usr/local/etc/tmail, F=lsDFMAw5:/|@qPrn+, S=10/30, R=20/40, E= , T=DNS/RFC822/X-Unix, A=tmail $u If tmail is to be called with the -I flag, it must be invoked with both real and effective UID root. Many sendmail configurations invoke the local mailer as the sending user when that user is local, which will prevent -b or -I from working. SECURITY CONSIDERATIONS
If tmail is invoked by an ordinary user, the Received: header line will indicate the name or UID of the user that invoked it. Ordinary users are not permitted to use the -b or -I flag since otherwise a user could create any file on another user's directory. tmail can deliver mail to home directories. In addition, tmail can be used to deliver mail to other mail folders in a home directory or an inferior directory of a home directory. RESTRICTIONS
The calling program should invoke tmail with CRLF newlines, otherwise tmail will complain in syslog. Absolute pathnames and ~user specifications are not permitted in +folder extensions. Ordinary users are not permitted to use the -I flag. IMAP4 namespace names are not yet supported in +folder extensions. It is not possible to use tmail to deliver to mh(1) format mailboxes. If delivery to multiple users is specified and delivery to any single user fails, the entire delivery will be reported as having failed, even though delivery to other users may have succeeded. If tmail is used for mail delivery from sendmail(8), a separate tmail invocation should be done for each user. Otherwise a delivery failure for a single user in a message going to multiple users will cause multiple deliveries to all the other users every time sendmail(8), retries. AUTHOR
Mark Crispin, MRC@CAC.Washington.EDU SEE ALSO
binmail(1) sendmail(8) September 27, 2007 TMAIL(1)
All times are GMT -4. The time now is 12:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy