Show pageDiscussionOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. CKG Edit ==== Good email practices ==== === General === GNO has a connection to the internet via a satellite connection. This connection can handle a limited amount of data in a fixed amount of time. For the technicals amonst you: 2,5Mbits in and appr. 700bits out. At the moment of writing the main server for email is at the other side of the satellite connection, meaning that all emails being sent, be it to someone from gno-drc.com or any other will go trough the satellite connection. For example if someone from Direction CFO sends an email to someone from Direction Production, this email has to go out through the connection __and__ come back in. Because of the limited capacity of information that can be sent in a given amount of time it is good practice to limit the email traffic to the necessary, taking specialcare about the amount of attachments and of course about the size of attachments. A word document with a couple of pages of text is generally no problem, but a word document containing pictures, an mp3 file, or a video will take all the capacity available for a serious amount of time, making it for other users at the same moment very difficult to send their (perhaps even modestly sized documents) emails out. We are setting up a filesharing system that allows to transfer files between users within the concession in a much more efficient way... === Answer on emails === If you receive a mail, it is not necessary to tell the sender you got it, at least not always. === Answer to all === If you get an email which has been sent to many people : __do not answer to everybody__, limit yourself if you need to answer to the sender (we have to introduce mailinglists, Maurice ask me about that! ) .... email/useacl.txt Last modified: 9 years agoby koen