Thanks that's what I have done :) because I'm not always home :P

<p>I have recently got my hands on mercury/32 and quickly run into a wall :P I got it configured fine meaning I can send mail and receive mail from hotmail, gmail,yahoo and "spidernet" my isp however the strange things is that when I send eMail from another isp in my country "cytanet" I recieve no mail and I don't see mercury/32 even trying to proccess it meaning its not even finding the server, but isn't it strange that one isp "spidernet" and hotmail, gmail, yahoo, mail.ru etc all can send email to me exept the "cytanet" provider? I have called them to see if maybe they use other ports but they use the default ports 110 and 25, I am uterly stumped what could possily be the reason for this? </p><p>Regards </p><p>Mike</p><p>P.S My eMail with mercury is mike@dept.servehttp.com maybe you who deside to help me can send me an email here and see what happends.</p><p>Many thanks. </p>

<p>Your MX records work & your server responds well.</p><p>Too well in fact.</p><p>You need to tun off relaying & enable strict relaying in MercS config or you will be spewing spam and getting blacklisted, if you are not already.</p><p>You should also close your POP3 port (110) if you are not using it from outside.</p><p> </p>

<blockquote>[quote user="mixalis1987"]I have recently got my hands on mercury/32 and quickly run into a wall :P I got it configured fine meaning I can send mail and receive mail from hotmail, gmail,yahoo and "spidernet" my isp however the strange things is that when I send eMail from another isp in my country "cytanet" I recieve no mail and I don't see mercury/32 even trying to proccess it meaning its not even finding the server, but isn't it strange that one isp "spidernet" and hotmail, gmail, yahoo, mail.ru etc all can send email to me exept the "cytanet" provider? I have called them to see if maybe they use other ports but they use the default ports 110 and 25, I am uterly stumped what could possily be the reason for this? </blockquote><p>Responds to port 25 normally however it looks like you are running an open relay.  Go to Configuration | MercuryS | Connection control and check the relaying and strict blocks at least. </p><h1> Mail relay testing </h1> Connecting to dept.servehttp.com for anonymous test ...<p> <tt><<< 220 ebony ESMTP server ready.</tt> <tt>>>> HELO www.abuse.net</tt> <tt><<< 250 ebony Hello, www.abuse.net.</tt> </p><h3>Relay test 1</h3> <tt>>>> RSET</tt> <tt><<< 250 Command processed OK.</tt> <tt>>>> MAIL FROM:<spamtest@abuse.net></tt> <tt><<< 250 Sender OK - send RCPTs.</tt> <tt>>>> RCPT TO:<securitytest@abuse.net></tt> <tt><<< 250 Recipient OK - send RCPT or DATA.</tt> <h3>Relay test result</h3> Hmmn, at first glance, host appeared to accept a message for relay.<p> <blink><b>THIS MAY OR MAY NOT MEAN THAT IT'S AN OPEN RELAY.</b></blink></p><p> Some systems appear to accept relay mail, but then reject messages internally rather than delivering them, but you cannot tell at this point whether the message will be relayed or not.</p><p> You cannot tell if it is really an open relay without sending a test message; this anonymous user test <b>DID NOT</b> send a test message.</p><p>You might want to try turning on session logging for the connecting IP address of the "cytanet" SMTP severs IP addresses in this same section by enabling "Autoenable session logging".   If you check the Autoenable session logging for connections from this address range control, Mercury will automatically turn on session logging for any connection coming from the specified range of addresses. Session logs collect a complete transcript of the entire exchange between the client and MercuryS, and can be extremely useful in diagnosing problems and for evidentiary purposes. Remember when using this option that session logs are at least as large as all the data exchanged in the session, and they can chew through space at considerable speed - use them carefully. </p><blockquote><p>Regards </p><p>Mike</p><p>P.S My eMail with mercury is mike@dept.servehttp.com maybe you who desire to help me can send me an email here and see what happens.</p></blockquote><p>I'll give it a shot. Worked fine. </p><p>-------------------------------------------------------------------------                          Mail Delivery Transcript ------------------------------------------------------------------------- This system-generated message contains a transcript documenting the process of delivering an e-mail message. It does not prove that the recipient has either received or read your message - merely that the message has been successfully accepted by another system, which now assumes responsibility for delivering the message to the recipient. In the vast majority of cases, though, this transcript can be used as a reasonably reliable indication that a message has been successfully delivered. In the transcript, lines marked ">>" are the commands sent by this mail server, while lines marked "<<" represent the replies from the remote mail server.    Transcript generated by:     tstephenson.com    Message date:                Mon, 09 Mar 2009 08:07:47 -0700    Message subject:             Test Message    Job identifier:              MO000483    Delivery started:            Mon, 9 Mar 2009 08:08:05 -0700    Delivery ended:              Mon, 9 Mar 2009 08:08:09 -0700 ----------- Transcript of delivery process follows ---------------------- Established connection to 217.175.209.74 >> MAIL FROM:<support@tstephenson.com> SIZE=1114 << 250 Sender and size (1114) OK - send RCPTs. >> RCPT TO:<mike@dept.servehttp.com> << 250 Recipient OK - send RCPT or DATA. >> DATA << 354 OK, send data, end with CRLF.CRLF >> [Sent 1114 bytes of message data] << 250 Data received OK. 8:08:09: 4 seconds elapsed, closing connection. -------------------------------------------------------------------------  </p><blockquote><p>Many thanks.[/quote]</p></blockquote>

[quote user="dilberts_left_nut"]<p>Your MX records work & your server responds well.</p><p>Too well in fact.</p><p>You need to tun off relaying & enable strict relaying in MercS config or you will be spewing spam and getting blacklisted, if you are not already.</p><p>You should also close your POP3 port (110) if you are not using it from outside.</p><p> </p><p>[/quote]</p><p> </p><p>Thanks for the heads up on the relaying, this is just for testing at the moment, but I will keep that in mind :) I opened port 110 because I would like to access my emails from out side my network, was that wrong? </p>

<p>If you want to have POP3 access from the Internet you should keep port 110 open. It's a good idea to have strong passwords for your accounts, though.</p><p>/Rolf  </p>

<p>@<a href="http://community.pmail.com/forums/members/Thomas.aspx">Thomas R.</a></p><p>I have received both of your emails thanks, and will sort out the session logs and see what is going on. </p>