ICC Home / Members / Meetings / Peer Support / Documentation / Projects
Bounced E-mail from Senders:
(with thanks to Dwight Jesseman)
First rule out an improper Gatorlink forward setting
Each user can modify their own forward settings (unfortunately) via the "Modify" link at the Gatorlink website. For people with IFAS mailboxes, that should be set to "GLusername@my.ifas.ufl.edu". If forwarding is removed, then senders outside of our Exchange system will get a bounced message similar to the following:
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: firstname.lastname@example.org SMTP error from remote mail server after RCPT TO:
Either have the user assist you in checking their settings via the web (preferably) or contact Dwight Jesseman who can view and set that field for them.
Assuming that was not the problem, then see if the following scenario fits...
A sender to a UF email recipient gets a bounced email indicating something like "451 4.7.1 Please try again later".
With a suspicious email, the UF Greylisting process requests the sender's email system to resend the email within a certain time interval. If the sender's email system does not resend the email in the required time interval, the message gets bounced.
There are two noticeable indicators that a message has been affected by Greylisting,
To get a Greylisting issue resolved, have the affected recipient send an email to email@example.com. There is an individual that reviews all messages sent to this list on a case-by-case bases, it is not an automated process to get an issue resolved.
The follow information should be included in an email to the Open Systems Group regarding a Greylisting issue:
Following the above process should result in better mail flow for your users when Greylisting has caused an issue. Previously for Greylisting issues Dwight had indicated that users send an email to firstname.lastname@example.org; that was incorrect, and is not the recommended method.
last edited 23 August 2007 by Steve Lasley