Sponsored Content
Operating Systems Linux Red Hat postfix connection timed out issue on centOS Post 302368174 by fpmurphy on Wednesday 4th of November 2009 09:11:24 AM
Old 11-04-2009
Postfix, by default, will forward mail to authorized remote destinations only. Authorized remote destinations are defined with the relay_domains configuration parameter. The default is to authorize all domains (and subdomains) of the domains listed with the mydestination parameter.

Example:
Code:
        relay_domains = $mydestination

What is your $mydestination set to?

Postfix, by default, attempts to deliver mail directly to the Internet. However your system may be behind a firewall, or it may be connected via a provider who does not allow direct mail to the Internet. In those cases you need to configure Postfix to deliver mail indirectly via a relay host. You should specify one (and only one) of the following:

Code:
        relayhost =                               (default: direct delivery to Internet)
        relayhost = $mydomain            (deliver via local mailhub)
        relayhost = [mail.$mydomain]   (deliver via local mailhub)
        relayhost = [mail.isp.tld]           (deliver via provider mailhub)

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Connection Timed out

I connect to a Sun Box through telnet but it timed out in couple of minutes. Advance thanks for any idea...help... (2 Replies)
Discussion started by: s_aamir
2 Replies

2. UNIX for Advanced & Expert Users

deferred: connection timed out with NT

We recently installed a new release of SCO UNIX (5.0.6) and when I try to relay e-mail from the UNIX box to my NT server (the mail server) I get the following message from sendmail. Deferred: Connection timed out with nt I have nt set up as my relay server in sendmail.cf and the mail seems to... (8 Replies)
Discussion started by: jmossman
8 Replies

3. Linux Benchmarks

Connection Timed out problem - EM64T

Hai All, I have problem during HTTP benchmarking with polygraph tool on EM64T machine. Benchmarking results are getting problem bcas of connection timed out system errors. Machine log information is as, /var/log/messages.3:Feb 18 16:17:44 proxy64 network: Bringing up interface eth0: ... (0 Replies)
Discussion started by: muthukumar
0 Replies

4. HP-UX

connection timed out

I am trying to connect with my hp machine using "dialup networking." It times out after 30 seconds. Is there a way to adjust this time. Would it have anything to do with rexec? thanks (0 Replies)
Discussion started by: paschal
0 Replies

5. Programming

Socket Programming - Port Scanner. I Get Connection Timed Out, Why?

When i put the target IP as 127.0.1.1, the program is working fine, can catch blocked & open ports. But when i try to scan remotely, i get connection timed out! Can you tell me why? :( Here is my code - Look at between where i put astriks - at the bottom: #include<iostream>... (3 Replies)
Discussion started by: f.ben.isaac
3 Replies

6. UNIX for Dummies Questions & Answers

Please help with Postfix config issue - How to allow remote Exchange server to relay to my postfix

Hi guys One of our clients have a problem with sending email to a certain domain. No matter what we try, the mails just dont get delivered. What I did then, is created a new connector on their Exchange server, pointing all mail sent to their client at "domain1" to relay to our Postfix mail... (0 Replies)
Discussion started by: wbdevilliers
0 Replies

7. Red Hat

SMTP authentication on Postfix/Dovecot on CentOS

Hi, I did setup one E-mail Server with postfix/dovecot/squirrelmail on CentOS 5.x and is working fine. I did configure SMTP authentication (without TSL/SSL) so that users from outside can send emails via our email server with SMTP auth. One weird issue i'm getting is that it's working from... (1 Reply)
Discussion started by: prvnrk
1 Replies

8. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies

9. AIX

Ssh connection timed out

Hello, I have two AIX6.1 machines that can communicate with each other through ssh. The problem is that one of them somehow closes the connection after some time and i don't know the reason of that. For example today i send through rsync command 7 files from one server to the other. It send... (7 Replies)
Discussion started by: omonoiatis9
7 Replies

10. Red Hat

Centos 6 Postfix 1 IP Two Domains Two Machines

Hello Folks, I have what I believe is a basic problem. I'm sure the problem is related to my incorrect understanding of the terms used by the postfix main.cf file. I have two mail servers. 192.168.1.110 (msrecycle.com) and 192.168.1.111 (sportbikebody.com). Now what I am trying to do is have... (1 Reply)
Discussion started by: SportBikeBody
1 Replies
TRIVIAL-REWRITE(8postfix)												 TRIVIAL-REWRITE(8postfix)

NAME
trivial-rewrite - Postfix address rewriting and resolving daemon SYNOPSIS
trivial-rewrite [generic Postfix daemon options] DESCRIPTION
The trivial-rewrite(8) daemon processes three types of client service requests: rewrite context address Rewrite an address to standard form, according to the address rewriting context: local Append the domain names specified with $myorigin or $mydomain to incomplete addresses; do swap_bangpath and allow_per- cent_hack processing as described below, and strip source routed addresses (@site,@site:user@domain) to user@domain form. remote Append the domain name specified with $remote_header_rewrite_domain to incomplete addresses. Otherwise the result is identi- cal to that of the local address rewriting context. This prevents Postfix from appending the local domain to spam from poorly written remote clients. resolve sender address Resolve the address to a (transport, nexthop, recipient, flags) quadruple. The meaning of the results is as follows: transport The delivery agent to use. This is the first field of an entry in the master.cf file. nexthop The host to send to and optional delivery method information. recipient The envelope recipient address that is passed on to nexthop. flags The address class, whether the address requires relaying, whether the address has problems, and whether the request failed. verify sender address Resolve the address for address verification purposes. SERVER PROCESS MANAGEMENT
The trivial-rewrite(8) servers run under control by the Postfix master server. Each server can handle multiple simultaneous connections. When all servers are busy while a client connects, the master creates a new server process, provided that the trivial-rewrite server process limit is not exceeded. Each trivial-rewrite server terminates after serving at least $max_use clients of after $max_idle seconds of idle time. STANDARDS
None. The command does not interact with the outside world. SECURITY
The trivial-rewrite(8) daemon is not security sensitive. By default, this daemon does not talk to remote or local users. It can run at a fixed low privilege in a chrooted environment. DIAGNOSTICS
Problems and transactions are logged to syslogd(8). CONFIGURATION PARAMETERS
On busy mail systems a long time may pass before a main.cf change affecting trivial-rewrite(8) is picked up. 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. COMPATIBILITY CONTROLS
resolve_dequoted_address (yes) Resolve a recipient address safely instead of correctly, by looking inside quotes. resolve_null_domain (no) Resolve an address that ends in the "@" null domain as if the local hostname were specified, instead of rejecting the address as invalid. resolve_numeric_domain (no) Resolve "user@ipaddress" as "user@[ipaddress]", instead of rejecting the address as invalid. Available with Postfix version 2.5 and later: allow_min_user (no) Allow a sender or recipient address to have `-' as the first character. ADDRESS REWRITING CONTROLS
myorigin ($myhostname) The domain name that locally-posted mail appears to come from, and that locally posted mail is delivered to. allow_percent_hack (yes) Enable the rewriting of the form "user%domain" to "user@domain". append_at_myorigin (yes) With locally submitted mail, append the string "@$myorigin" to mail addresses without domain information. append_dot_mydomain (yes) With locally submitted mail, append the string ".$mydomain" to addresses that have no ".domain" information. recipient_delimiter (empty) The separator between user names and address extensions (user+foo). swap_bangpath (yes) Enable the rewriting of "site!user" into "user@site". Available in Postfix 2.2 and later: remote_header_rewrite_domain (empty) Don't rewrite message headers from remote clients at all when this parameter is empty; otherwise, rewrite message headers and append the specified domain name to incomplete addresses. ROUTING CONTROLS
The following is applicable to Postfix version 2.0 and later. Earlier versions do not have support for: virtual_transport, relay_trans- port, virtual_alias_domains, virtual_mailbox_domains or proxy_interfaces. local_transport (local:$myhostname) The default mail delivery transport and next-hop destination for final delivery to domains listed with mydestination, and for [ipad- dress] destinations that match $inet_interfaces or $proxy_interfaces. virtual_transport (virtual) The default mail delivery transport and next-hop destination for final delivery to domains listed with $virtual_mailbox_domains. relay_transport (relay) The default mail delivery transport and next-hop destination for remote delivery to domains listed with $relay_domains. default_transport (smtp) The default mail delivery transport and next-hop destination for destinations that do not match $mydestination, $inet_interfaces, $proxy_interfaces, $virtual_alias_domains, $virtual_mailbox_domains, or $relay_domains. parent_domain_matches_subdomains (see 'postconf -d' output) What Postfix features match subdomains of "domain.tld" automatically, instead of requiring an explicit ".domain.tld" pattern. relayhost (empty) The next-hop destination of non-local mail; overrides non-local domains in recipient addresses. transport_maps (empty) Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). Available in Postfix version 2.3 and later: sender_dependent_relayhost_maps (empty) A sender-dependent override for the global relayhost parameter setting. Available in Postfix version 2.5 and later: empty_address_relayhost_maps_lookup_key (<>) The sender_dependent_relayhost_maps search string that will be used instead of the null sender address. Available in Postfix version 2.7 and later: empty_address_default_transport_maps_lookup_key (<>) The sender_dependent_default_transport_maps search string that will be used instead of the null sender address. sender_dependent_default_transport_maps (empty) A sender-dependent override for the global default_transport parameter setting. ADDRESS VERIFICATION CONTROLS
Postfix version 2.1 introduces sender and recipient address verification. This feature is implemented by sending probe email messages that are not actually delivered. By default, address verification probes use the same route as regular mail. To override specific aspects of message routing for address verification probes, specify one or more of the following: address_verify_local_transport ($local_transport) Overrides the local_transport parameter setting for address verification probes. address_verify_virtual_transport ($virtual_transport) Overrides the virtual_transport parameter setting for address verification probes. address_verify_relay_transport ($relay_transport) Overrides the relay_transport parameter setting for address verification probes. address_verify_default_transport ($default_transport) Overrides the default_transport parameter setting for address verification probes. address_verify_relayhost ($relayhost) Overrides the relayhost parameter setting for address verification probes. address_verify_transport_maps ($transport_maps) Overrides the transport_maps parameter setting for address verification probes. Available in Postfix version 2.3 and later: address_verify_sender_dependent_relayhost_maps ($sender_dependent_relayhost_maps) Overrides the sender_dependent_relayhost_maps parameter setting for address verification probes. Available in Postfix version 2.7 and later: address_verify_sender_dependent_default_transport_maps ($sender_dependent_default_transport_maps) Overrides the sender_dependent_default_transport_maps parameter setting for address verification probes. 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. empty_address_recipient (MAILER-DAEMON) The recipient of mail addressed to the null address. 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. max_use(100) The maximal number of incoming connections that a Postfix daemon process will service before terminating voluntarily. relocated_maps (empty) Optional lookup tables with new contact information for users or domains that no longer exist. 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. queue_directory (see 'postconf -d' output) The location of the Postfix top-level queue directory. show_user_unknown_table_name (yes) Display the name of the recipient table in the "User unknown" responses. 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". Available in Postfix version 2.0 and later: helpful_warnings (yes) Log warnings about problematic configuration settings, and provide helpful suggestions. SEE ALSO
postconf(5), configuration parameters transport(5), transport table format relocated(5), format of the "user has moved" table master(8), process manager syslogd(8), system logging README FILES
Use "postconf readme_directory" or "postconf html_directory" to locate this information. ADDRESS_CLASS_README, Postfix address classes howto ADDRESS_VERIFICATION_README, Postfix address verification LICENSE
The Secure Mailer license must be distributed with this software. AUTHOR(S) Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA TRIVIAL-REWRITE(8postfix)
All times are GMT -4. The time now is 06:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy