Postfix Email Forwarding: 421 Toomanyconnections. Please kindly advise !!! -- Linux Enterprise Application-Linux server application information. For details, refer to the following section. After configuring the Netease integrity mailbox Alliance according to the configuration provided by it, the log always displays Too transport connections. below is Netease's configuration, log, and my mailbox configuration. Please kindly advise, thank you !!!
Netease configuration code:
1. transport_maps settings in the query system:
[Root @ ~] # Postconf transport_maps
Transport_maps =
[Root @ ~] #
If the system has not configured transport map as shown in the preceding output, continue with the following steps. If you have configured transport_maps = hash :****, go to Step 3 and change the file name involved in step 3 to the file above.
If it is not hash, it will be a little troublesome. For example, mysql: ***, you need to change the corresponding records in the corresponding database.
2. Configure transport map for postfix:
[Root @ ~] # Postconf-e 'Transport _ maps = hash:/etc/postfix/transport'
[Root @ ~] #
[Root @ ~] #
3. Enter the query command in step 1. If Step 2 is set successfully, the following output is displayed:
[Root @ ~] # Postconf transport_maps
Transport_maps = hash:/etc/postfix/transport
[Root @ ~] #
4. Next, let's modify the transport map file.
Tell the postfix that when the recipient is 126.com/163.com/yeah.net, it will be sent to our dedicated channel
Cat>/etc/postfix/transport < 126. com smtp: [mopen.126.com]
163. com smtp: [mopen.163.com]
Yeah.net smtp: [mopen.yeah.net]
EOF
5. The configuration in the second step is to use the HASH data format, so we need to convert the changes made in the fourth step into the HASH data format.
Because postfix will eventually only read organized data and will not read text files.
6. Run the postmap/etc/postfix/transport Command to convert the input in Step 4 to the HASH format:
[Root @ ~] # Ls-l/etc/postfix/transport *
-Rw-r -- 1 root 12647 Dec 19 18:50/etc/postfix/transport
[Root @ ~] # Postmap/etc/postfix/transport
[Root @ ~] # Ls-l/etc/postfix/transport *
-Rw-r -- 1 root 12647 Dec 19 18:50/etc/postfix/transport
-Rw-r -- 1 root 12288 Dec 19 18:50/etc/postfix/transport. db
[Root @ ~] #
Check the ls output. After the command is executed, a transport. db file is generated. The postfix is used to read the file.
7. Check whether the transport. db content is consistent with our Configuration:
[Root @ ~] # Postmap-q 'Yeah. net'/etc/postfix/transport
Smtp: mopen.yeah.net
[Root @ ~] # Postmap-q '2014. com'/etc/postfix/transport
Smtp: mopen.163.com
[Root @ ~] #
[Root @ ~] # Postmap-q '2014. com'/etc/postfix/transport
Smtp: mopen.126.com
[Root @ ~] # Postmap-q '2014. com'/etc/postfix/transport
[Root @ ~] #
Note that the last line of postmap command is not configured with 188.comin Step 4. Therefore, no result can be found.
8. The last step is to make the postfix take effect in transport map settings.
Postfix reload
9. Check maillog
Tail-f/var/log/maillog | egrep '@ 126.com | @ 163.com | @ yeah.net'
See if there are any logs similar to the following:
Postfix/smtp [25367]: 3029053952FF: to = <*** @ 126.com>, relay = mopen.126.com [220.181.15.120]: 25, delay =
Relay = mopen.126.com indicates that the email is replayed to mopen.126.com.
10. Complete
Logs:
Nov 28 16:45:16 websvr-122-11-49-187 postfix/error [26246]: 1CF8947E0: to = , Relay = none, delay = 8829, delays = 8829/0/0/0.02, dsn = 4.0.0, status = deferred (delivery temporarily suspended: host mopen.126.com [220.1815.120] refused to talk to me: 421 Too connections)
Nov 28 16:45:16 websvr-122-11-49-187 postfix/error [23704]: 104633A02: to = , Relay = none, delay = 67523, delays = 67523/0/0/0.02, dsn = 4.0.0, status = deferred (delivery temporarily suspended: host mopen.163.com [220.181.12.140] refused to talk to me: 421 Too connections)
Nov 28 16:48:24 websvr-122-11-49-187 postfix/smtp [23714]: 8138449E2: to = , Relay = mopen.163.com [220.181.12.140]: 25, delay = 0.05, delays = 0.02/0/0.03/0, dsn = 4.0.0, status = deferred (host mopen.163.com [220.181.12.140] refused to talk to me: 421 Too many connections)
On the Internet, Baidu has set the following parameters:
### 2014-11-28 ######
Smtpd_client_message_rate_limit = 5
Smtpd_client_recipient_rate_limit = 10
Initial_destination_concurrency = 2
Default_destination_concurrency_limit = 5
Default_destination_recipient_limit = 25
Smtpd_client_connection_rate_limit = 5
But the problem persists. The following is my postfix Configuration:
Queue_directory =/var/spool/postfix
Command_directory =/usr/sbin
Daemon_directory =/usr/libexec/postfix
Data_directory =/var/lib/postfix
Mail_owner = postfix
Myhostname = mail.xxxxxx.net
Mydomain = xxxxxx.net
Myorigin = $ mydomain
Unknown_local_recipient_reject_code = 550
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
