Sending a response to known phishing messages is blocked so that account info (username, password, ...) cannot be passed on.
Blocking bogus websites
All email is checked for viruses and spam:
Viruses will not be sent to the user.
Active spam runs are blocked.
Email identified as spam gets the label [SPAM] in the subject of the message.
You can avoid getting [SPAM] mails in your inbox by setting a filter rule. E.g. in webmail.
In the 'Exchange' environment (Junk) e-mail filtering is active by default.
The UGent system consists of two components:
First line We try to stop SPAM:
we adhere strictly to the smtp protocol definition
Second line Next we check the content of the remaining messages, using SpamAssassin. Messages which are recognized as spam are removed. Messages which could be spam get the [SPAM] label.
2. Do senders get a warning when their mail is marked as spam?
If the email was stopped in the first line, a bounce message is sent.
If the email was labeled in the second line, UGent does not send a warning to the sender.
3. Why is the delivery of external emails delayed?
When a sender sends too many messages to a UGent address or sends them too quickly, the delivery will be delayed. We use greylisting and throttling.
4. Why is the message delivery to a UGent address refused?
You are trying to send an e-mail to a UGent address and get a "Delivery not authorized, message refused" message. Why?
The most efficient and cheapest of anti-spam measures is to demand that senders (servers) follow the rules in sending email. Please contact your system administrator for further analysis. The system administrator can contact email@example.com.
To prevent spam from being sent, restrictions are set. The implications of these depend on your role.