Thread View: comp.mail.pegasus-mail.misc
1 messages
1 total messages
Started by Lauri Laupmaa
Tue, 02 Jan 2001 12:40
mercury netware & refuse: 0.0.0.0
Author: Lauri Laupmaa
Date: Tue, 02 Jan 2001 12:40
Date: Tue, 02 Jan 2001 12:40
41 lines
2443 bytes
2443 bytes
--------------A65C3F204E112190502C6BAD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi I have setup of 3 mail servers for domain. Netware with mercury is MX 10 and two unix hosts are MX 20. Now I want to do some spamcontrol. I set up mercury to allow mail only from my two unix MX 20 hosts and refuse the rest of the world. The problem is: Some mail servers do not understand the 520 error mercury generates and mail is NOT delivered from these domains. I wanted to ask if this is legal configuration. And why mercury uses 520 error for that reason ? Has it been taken from some RFC ? TIA L. --------------A65C3F204E112190502C6BAD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Hi <p>I have setup of 3 mail servers for domain. Netware with mercury is MX 10 and two unix hosts are MX 20. Now I want to do some spamcontrol. I set up mercury to allow mail only from my two unix MX 20 hosts and refuse the rest of the world. <p>The problem is: Some mail servers do not understand the 520 error mercury generates and mail is NOT delivered from these domains. <p>I wanted to ask if this is legal configuration. And why mercury uses 520 error for that reason ? Has it been taken from some RFC ? <p>TIA <p><i>L.</i></html> --------------A65C3F204E112190502C6BAD--
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads