|
Questions
|
|
Q: Why do I receive the following error: 550 5.7.1 Relay not permitted?
|
A: Email Error: There are two reasons why you would receive this message. You have an internal IP address, but the IP address is not registered in DNS or you are trying to send email from an ISP other than the service provided by the Johns Hopkins Institution.
Internal user- The IP address of the system that you are sending email from is not registered in the Hopkins primary name server. Therefore, the enterprise relays can not resolve your hostname and think that your machine is located outside of the Hopkins domain. You or your technical contact can register your machine online using the DNS Request Tool at https://jhars.nts.jhu.edu . Once this is done, you should not have any problems sending mail to users outside of Hopkins.
External user- Due to problems with external users sending unsolicited bulk e-mail through the Enterprise email relays, we have had to disable third-party relay on our resources. Third-party relay is someone outside of the Hopkins domains sending email through smtp.jhu.edu or smtp.jhmi.edu to other email users outside the Hopkins domains. If you received this error, then most likely you are using an ISP outside of the Hopkins domains and using smtp.jhu.edu or smtp.jhmi.edu as your SMTP server. A majority of ISP's have there own SMTP servers and you should use the one provided by your ISP. NOTE: Allegedly, AOL does not provide SMTP servers for their customers and you must use their proprietary email software to send email. Another option is to use authenticated SMTP. Please refer to our discussion on how
|
|
[Return to Top]
|
|
Q: Why am I receiving error messages stating that an email that I sent could not be delivered to the recipient? I never sent these messages.
|
A: This is a very common issue that is typically caused by spammers forging sender addresses. In an effort to hide his/her identity, the spammer will forge your email alias when sending spam. If any of the spammer's emails do not reach the intended recipients, those messages will be bounced to the forged sender address (your email alias). As a result, you will receive failed notification messages for messages you never even sent. Please refer to the link below for information about how this issue is being addressed:
Click Here For More Information
|
|
[Return to Top]
|
|
Q: What is authenticated SMTP?
|
|
A: Email: Authenticated SMTP is a service provided by the Enterprise email relays. Authenticated SMTP allows email users that are traveling outside of the JHU and JHMI networks to use the email relays as their outgoing SMTP server to send email. Your JHED LID and JHED password are required to authenticate, your email client must be configured to use authenticated SMTP and your ISP must allow outgoing SMTP connections in order to take advantage of authenticated SMTP.
|
|
[Return to Top]
|
|
Q: My Symantec anti-virus software detected a virus in a message. Who should I notify?
|
|
A: Anti-Virus: The institution has developed a two-tier approach to anti-virus. Sophos anti-virus runs on the enterprise email relays and Symantec anti-virus runs on a majority of the desktops. No vendor consistently releases signature updates for viruses before other vendors do and so it is expected that Symantec may release a signature before Sophos does and that you will detect these types of viruses in your anti-virus software.
|
|
[Return to Top]
|
|
Q: What is the maximum message size allowed by the enterprise relays?
|
|
A: Relays: The current maximum message size allowed by the enterprise relays is 25MB.
|
|
[Return to Top]
|
|
Q: I sent an email with an attachment but it was never received. What happened to the message?
|
A: Several reasons exist for an email message not reaching its destination. One solution is to check if the attachment extension is prohibited. Click the following link for more information:
Click Here For More Information
|
|
[Return to Top]
|
|
Q: Why are there no notifications sent to either the recipient or the sender when a message that contains a prohibited attachment is deleted?
|
|
A: One of the main reasons that these extensions are being blocked is because they are commonly used by viruses to infect other machines via email. Another trick that viruses use is to forge the From: email address so that, if the recipient can not be delivered to, it still has a chance to be bounced back to the forged sender address. The Enterprise Gateways currently drop about 10,000 messages a day that contain prohibited extensions. Of those messages, 95% or more are viruses. So, if we were to enable notifications to the recipient or the sender, we risk the chance of notifying the incorrect sender in the case of forged From: addresses or annoying the recipient who may be getting bombarded with these types of messages.
|
|
[Return to Top]
|
|
Q: Who can I report spam or false positives to?
|
A: False positives can be reported to: ham@access.ironport.com
Missed spam can be reported to: spam@access.ironport.com
|
|
[Return to Top]
|
|
Q: How do I check to see if my ISP is blocking port 25?
|
A: On a Windows Computer:
Click "Start" and then "Run..."
Type "cmd" in the box provided and press Enter
Now type "telnet smtp.johnshopkins.edu 25" and press Enter
If a message like the following appears, port 25 is open: "220 ipex.johnshopkins.edu ESMTP"
If a message like the following appears, port 25 is closed or firewall software is installed: "Could not open connection to the host, on port 25: Connect failed "
On a Linux, Unix or Mac Computer:
Open a terminal session and type "telnet smtp.johnshopkins.edu 25" and press Enter
If a message like the following appears, port 25 is open: ""220 ipex.johnshopkins.edu ESMTP"
If not, port 25 is blocked or firewall software is installed on your computer.
In the event that port 25 is blocked by your ISP, you can configure your email client to use port 587 (SMTP authentication and TLS are required). Otherwise, you should contact your ISP and ask them for the correct settings for their mail servers.
|
|
[Return to Top]
|
|
Q: Certain entities, outside of Hopkins, are unable to send emails to my Hopkins email address successfully. Their messages are being returned with a 5.x.x error code. What's going on?
|
|
A: It's likely the sender is being throttled\blocked by our perimeter security appliances because a high percentage of spam has been received from that particular sender's outgoing mail server. The sender/outside entity should have their technical contact fill out and submit an "Unblock Request Form".
|
|
[Return to Top]
|
