Tertiary-mx: Difference between revisions
Content deleted Content added
→top: clean up |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
*Message size is over 1GB. |
*Message size is over 1GB. |
||
*The server will 'greylist' hosts. It will always defer (cause a temporary delivery failure) messages/connections under the following circumstances: |
*The server will 'greylist' hosts. It will always defer (cause a temporary delivery failure) messages/connections under the following circumstances: |
||
*Sending host in a DNS |
*Sending host in a DNS blocklist |
||
*Header syntax errors |
*Header syntax errors |
||
*Recipient rejected by the primary MX (It does a call back to the primary MX if it is available) |
*Recipient rejected by the primary MX (It does a call back to the primary MX if it is available) |
||
| Line 24: | Line 24: | ||
===etrn=== |
===etrn=== |
||
To force |
To force tertiary-mx to attempt to relay stored messages, telnet in on port 25 and issue an etrn command in the form of |
||
etrn #your-domain.co.uk |
etrn #your-domain.co.uk |
||
| Line 39: | Line 39: | ||
quit |
quit |
||
221 relentless.aa.net.uk closing connection |
221 relentless.aa.net.uk closing connection |
||
Note that tertiary-mx has various measures in place to discourage spam. You need to wait until after the "220 You are 2001:8b0:0::1" line is printed before you can issue the etrn, which may take a few seconds. Mismatching forward/reverse DNS etc. may upset it when you try to telnet in. If possible telnet in from your mail server itself, as that is more likely to look trustworthy. |
|||
==Setup== |
==Setup== |
||