Postfix: emails addressed to multiple smart hosts


 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Postfix: emails addressed to multiple smart hosts
# 1  
Old 02-17-2014
RedHat Postfix: emails addressed to multiple smart hosts

Hi,

I am in process of setting up a SMTP server on RHEL 6 using Postfix.

I am stuck at one point so any help would be appreciated.

I have configured my xsender to use this new SMTP server as its mail server.

If I send any emails addressed TO example.com the SMTP server should use the DNS MX record and forward that email.

If I send any email to any domain APART from example.com the SMTP server should use "myrelayhost.com" as its Relay Host which is an Iron port device.

Basically I do not want any email going internally to organization to hit my Ironport Device "myrelayhost.com"

How is this possible using postfix?
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Issues sending emails using PostFix Mail Server

I'm unable to send email from my Linux server despite SMTP port 25 Active and Listening. # hostname TechX I checked the mail log ( /var/log/maillog ) and found the below error. I'm sharing all the ".cf" files seen in the error log. 1. # more /etc/postfix/main.cf # postfix... (0 Replies)
Discussion started by: mohtashims
0 Replies

2. Shell Programming and Scripting

Ssh to multiple hosts and then run multiple for loops under remote session

Hello, I am trying to login to multiple servers and i have to run multiple loops to gather some details..Could you please help me out. I am specifically facing issues while running for loops. I have to run multiple for loops in else condition. but the below code is giving errors in for... (2 Replies)
Discussion started by: mohit_vardhani
2 Replies

3. Shell Programming and Scripting

Sending files to multiple emails

Hi All, I want to send each file to each email id as below. Instead of writing saparate 10 mail commands can we do it in a simple step. file1.csv to raghu.s@hps.com file2.csv to kiran.m@hps.com file3.csv to kenni.d@hps.com file4.csv to rani.d@hps.com file5.csv to sandya.s@hps.com... (2 Replies)
Discussion started by: ROCK_PLSQL
2 Replies

4. Shell Programming and Scripting

Avoid multiple emails being sent - Counter, Loop?

Hello, I have currently coded a bash script below in which it does the following: # Archives compressed file from another location. Basically it moves *.gz files to another location. The script also sends an email whenever a new compressed file is placed. This is the issue that i... (5 Replies)
Discussion started by: Wizard_1979
5 Replies

5. UNIX for Dummies Questions & Answers

Explain the difference between the commands cd ~smart and cd ~/smart

Is it possible for both commands to work? (1 Reply)
Discussion started by: phunkypants
1 Replies

6. Shell Programming and Scripting

Multiple emails via telnet in a script

Hi everyone, I'm writing a script that connect to telnet and write some email taking the RCPT from a file. My problem is the fact I'm not able to put all the addresses I have in the file as subject for the "RCPT TO:":confused:... Can anyone please help me? Thanks ps: I wrote this right... (7 Replies)
Discussion started by: t_waspy
7 Replies

7. Shell Programming and Scripting

mailx script to do multiple emails

I am looking for a script that I can use with mailx to do the following: 1. Grab usernames from a flat file (one at a time) 2. Attach a file to the email and mail out. Thanks. Cubefeed (3 Replies)
Discussion started by: CubeFeed
3 Replies

8. Shell Programming and Scripting

uuencode mailx - send multiple emails

The following is an extract from one of my Shell Scripts which uses uuencode and mailx to send an email with multiple attachements: uuencode $LOG_REPORT $(basename $LOG_REPORT) uuencode $HTML_FILE $(basename $HTML_FILE ) ) | if then mailx -b "$COPY_TO" -s "$SUBJECT" -r "$MAIL_FROM"... (2 Replies)
Discussion started by: suthera
2 Replies

9. IP Networking

Configuring POSTFIX to receive emails only from localhost

Hello, I am new to POSTFIX. My manager has asked me to configure POSTFIX running on a server to accept mail only from itself(localhost). Can someone tell me how I can go about doing this? (1 Reply)
Discussion started by: mojoman
1 Replies
Login or Register to Ask a Question
SCACHE(8postfix)														  SCACHE(8postfix)

NAME
scache - Postfix shared connection cache server SYNOPSIS
scache [generic Postfix daemon options] DESCRIPTION
The scache(8) server maintains a shared multi-connection cache. This information can be used by, for example, Postfix SMTP clients or other Postfix delivery agents. The connection cache is organized into logical destination names, physical endpoint names, and connections. As a specific example, logical SMTP destinations specify (transport, domain, port), and physical SMTP endpoints specify (transport, IP address, port). An SMTP connection may be saved after a successful mail transaction. In the general case, one logical destination may refer to zero or more physical endpoints, one physical endpoint may be referenced by zero or more logical destinations, and one endpoint may refer to zero or more connections. The exact syntax of a logical destination or endpoint name is application dependent; the scache(8) server does not care. A connection is stored as a file descriptor together with application-dependent information that is needed to re-activate a connection object. Again, the scache(8) server is completely unaware of the details of that information. All information is stored with a finite time to live (ttl). The connection cache daemon terminates when no client is connected for max_idle time units. This server implements the following requests: save_endp ttl endpoint endpoint_properties file_descriptor Save the specified file descriptor and connection property data under the specified endpoint name. The endpoint properties are used by the client to re-activate a passivated connection object. find_endp endpoint Look up cached properties and a cached file descriptor for the specified endpoint. save_dest ttl destination destination_properties endpoint Save the binding between a logical destination and an endpoint under the destination name, together with destination specific con- nection properties. The destination properties are used by the client to re-activate a passivated connection object. find_dest destination Look up cached destination properties, cached endpoint properties, and a cached file descriptor for the specified logical destina- tion. SECURITY
The scache(8) server is not security-sensitive. It does not talk to the network, and it does not talk to local users. The scache(8) server can run chrooted at fixed low privilege. The scache(8) server is not a trusted process. It must not be used to store information that is security sensitive. DIAGNOSTICS
Problems and transactions are logged to syslogd(8). BUGS
The session cache cannot be shared among multiple machines. When a connection expires from the cache, it is closed without the appropriate protocol specific handshake. CONFIGURATION PARAMETERS
Changes to main.cf are picked up automatically as scache(8) processes run for only a limited amount of time. Use the command "postfix reload" to speed up a change. The text below provides only a parameter summary. See postconf(5) for more details including examples. RESOURCE CONTROLS
connection_cache_ttl_limit(2s) The maximal time-to-live value that the scache(8) connection cache server allows. connection_cache_status_update_time(600s) How frequently the scache(8) server logs usage statistics with connection cache hit and miss rates for logical destinations and for physical endpoints. MISCELLANEOUS CONTROLS
config_directory (see 'postconf -d' output) The default location of the Postfix main.cf and master.cf configuration files. daemon_timeout(18000s) How much time a Postfix daemon process may take to handle a request before it is terminated by a built-in watchdog timer. ipc_timeout(3600s) The time limit for sending or receiving information over an internal communication channel. max_idle(100s) The maximum amount of time that an idle Postfix daemon process waits for an incoming connection before terminating voluntarily. process_id (read-only) The process ID of a Postfix command or daemon process. process_name (read-only) The process name of a Postfix command or daemon process. syslog_facility (mail) The syslog facility of Postfix logging. syslog_name (see 'postconf -d' output) The mail system name that is prepended to the process name in syslog records, so that "smtpd" becomes, for example, "postfix/smtpd". SEE ALSO
smtp(8), SMTP client postconf(5), configuration parameters master(8), process manager syslogd(8), system logging README FILES
Use "postconf readme_directory" or "postconf html_directory" to locate this information. CONNECTION_CACHE_README, Postfix connection cache LICENSE
The Secure Mailer license must be distributed with this software. HISTORY
This service was introduced with Postfix version 2.2. AUTHOR(S) Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA SCACHE(8postfix)