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
2004-04-15

      mailping

      0.0.4

MAILPING-CRON(1)						     Mailping							  MAILPING-CRON(1)

NAME
mailping-cron - run periodic processing to test email service availability and functioning SYNOPSIS
mailping-cron DESCRIPTION
mailping-cron processes incoming emails, updates status and sends out probe messages. The idea is to configure multiple email "circuits", send probe messages regularly, and see whether they complete the circuit and how long it took. Setting up a circuit 1. Give a name to the circuit, hereafter referred to as circuit. 2. Arrange for a local email address to be delivered to maildir /var/lib/mailping/state/circuit/incoming/. See mailping-store. 3. Create a configuration for the circuit, by creating directory /etc/mailping/circuit. If you need non-default sender and/or recipient addresses, create files from and to there, containing the sender and recipient addresses suitable for the circuit. 4. You're done! Munin should now see the data. Testing multiple servers To test functioning of more than one email server, arrange an email alias at a remote site pointing to an address on your server, and set the address of that alias here. Here's an example of testing a system consisting of two email servers and everything in that path (smarthosts, primary MXs, virus checkers, etc.): Local address <mailping+that@this.example.com> is delivered with mailping-store to /var/lib/mailping/state/that/incoming/. Remote address <echo@that.example.com> is an alias that redirects all email to <mailping+that@this.example.com>. /etc/mailping/that/to is set to <echo@that.example.com>. FILES
/etc/mailping/circuit/from Sender address for the probe emails. Default: <currentuserid@fullyqualifiedhostname>. /etc/mailping/circuit/to Recipient address for the probe emails. You must arrange for the email to eventually get delivered to the maildir /var/lib/mailping/state/circuit/incoming/. mailping-store will probably be useful in that. Default: <currentuserid+circuit@fullyqualifiedhostname> /etc/mailping/circuit/admin Admistrative address, set as Reply-To in probe messages. Default: do not add Reply-To. /etc/mailping/circuit/interval How often a probe message is sent, in seconds. Default: 600 seconds. /var/lib/mailping/state/circuit/ Stored state for the probing. /var/lib/mailping/state/circuit/junk/ Maildir used to store all messages in incoming that do not look like probe messages. Read and delete them regularly. /var/lib/mailping/state/circuit/broken/ Maildir used to store all messages in incoming that do look like probe messages, but a corresponding pending entry cannot be found. Duplicated probe messages cause these. Read and delete them regularly. ENVIRONMENT
MAILPING_CONFIGDIR Override the location of the configuration directory. Default: /etc/mailping MAILPING_STATEDIR Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories named after the circuit name. Default: /var/lib/mailping SEE ALSO
mailping-store(1), mailping-success(1), mailping-latency(1) AUTHOR
Tommi Virtanen <tv@havoc.fi> Havoc Consulting Author. COPYRIGHT
Copyright (C) 2004 Havoc Consulting mailping 0. 2004-04-15 MAILPING-CRON(1)
All times are GMT -4. The time now is 08:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy