Sponsored Content
Full Discussion: Emails issue
Operating Systems Solaris Emails issue Post 302824139 by hasan.kamali on Thursday 20th of June 2013 09:11:13 AM
Old 06-20-2013
Can you elaborate further on sender address rewriting/masquerading?

Moreover, even if system does send out local system users system generated emails we don't care if they are rejected or discarded.
 

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

NAME
nullmailer-inject - Reformat and inject a message into the queue. SYNOPSIS
nullmailer-inject [-a] [-b] [-e] [-f sender] [-h] [recipient [recipient ...]] DESCRIPTION
This program reads a email message from standard input, reformats its header to comply with RFC822, and sends the resulting message to the queue. HEADER FIELDS The following lines are parsed for recipient addresses: To, Cc, Bcc, Apparently-To, Resent-To, Resent-Cc, and Resent-Bcc. The following sender address lines are parsed and rewritten: Sender, From, Reply-To, Return-Path, Return-Receipt-To, Errors-To, Resent- Sender, Resent-From, and Resent-Reply-To. If the Return-Path header field is present and contains a single address, its contents will be used to set the envelope sender address. If the message contains any of the following fields, it is treated as a resent message: Resent-Sender, Resent-From, Resent-Reply-To, Resent-To, Resent-Cc, Resent-Bcc, Resent-Date, Resent-Message-ID. If the message is resent, only the recipient fields prefixed with Resent- are examined for addresses. Any occurrences of Bcc, Resent-Bcc, Return-Path, or Content-Length are discarded after they are parsed (if necessary). If the header lacks a Message-Id field, a unique string is generated and added to the message. If the header lacks a Date field, the cur- rent local date and time in RFC822 format is appended to the message. If the message has no To or Cc fields, the following line is appended to the message: Cc: recipient list not shown: ; ADDRESS LISTS Address lists are expected to follow the syntax set out in RFC822. The following is a simplified explanation of the syntax. An address list is list of addresses separated by commas. An individual address may have one of the following three forms: user@fqdn, com- ment<user@fqdn>, or phrase:address-list;. Any of the first two forms may be used within the address list of the third form. Any word con- taining special characters must be placed in double quotes and the special characters must be preceded with a backslash. Comments may be placed between addresses in parenthesis. All comments are ignored. Addresses lists are reformatted as they are parsed for ease of later re-parsing when the message reaches the destination(s). If an address is missing a fqdn, nullmailer-inject adds one. OPTIONS
-a Use only the command line arguments as recipient addresses. Ignore the header recipient lines. -b Use both the command line arguments and data from the message header as recipient addresses. -e Use either the command line arguments (if there are any) or data from the message header (if there are no arguments) as the recipi- ent addresses. -f sender Set the envelope sender address to sender . -h Use only data from the message header as the recipient addresses. -n Do not queue the message, but print the reformatted contents to standard output. -v Print out the envelope (sender and recipient addresses) preceding the message when printing the message to standard output. RETURN VALUE
Exits 0 if it was successful, otherwise it prints a diagnostic message to standard output and exits 1. ENVIRONMENT
The environment variable NULLMAILER_FLAGS is parsed and the behavior of nullmailer-inject is modified if any of the following letters are present: c Use "address (comment)" style in the generated From field instead of the default "comment <address>" style. f Ignore and remove any From header lines and always insert a generated one. i Ignore and remove any Message-Id header lines. s Ignore and remove any Return-Path header lines. t Insert a To line containing a list of the recipients if the header does not contain either a To or a Cc field. If the message is determined to be a resent message (see above), a Resent-To field is added if the header does not contain either a Resent-To or a Resent-Cc field. The user name is set by NULLMAILER_USER, MAILUSER, USER, or LOGNAME, whichever comes first. If none of the above are set the name is taken from the password file, or set to unknown if that fails. The host name is set by the canonicalized value of NULLMAILER_HOST, MAILHOST, or HOSTNAME, whichever comes first, or the defaulthost config file if none of the above are set (see below). The full name of the user is set by NULLMAILER_NAME, MAILNAME, or NAME, whichever comes first. The user and host name of the envelope sender default to the user and host name set above, but may be overridden by NULLMAILER_SUSER and NULLMAILER_SHOST. If NULLMAILER_QUEUE is set, the program named is used in place of nullmailer-queue to queue the formatted message. CONTROL FILES
When reading the following files, a single line is read and stripped of all leading and trailing whitespace characters. defaultdomain The content of this file is appended to any host name that does not contain a period (except localhost), including defaulthost and idhost. Defaults to the value of the /etc/mailname system file, if it exists, otherwise the literal name defauldomain. defaulthost The content of this file is appended to any address that is missing a host name. Defaults to the value of the /etc/mailname system file, if it exists, otherwise the literal name defaulthost. idhost The content of this file is used when building the message-id string for the message. Defaults to the canonicalized value of defaulthost. /etc/mailname The fully-qualifiled host name of the computer running nullmailer. Defaults to the literal name me. SEE ALSO
nullmailer-queue(8) NOTES
This document glosses over very many details of how address parsing and rewriting actually works (among other things). nullmailer-inject(1)
All times are GMT -4. The time now is 07:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy