Frequently Asked Questions Q1. What is the difference between Window mode and Client mode in mgiPOP? A1. Window mode communicates directly with a POP email server to read, reply, forward and compose email messages using a static, web-based interface. Client mode downloads email from a POP server to an MGI database. Client mode does not have an interface, although it can be used in conjunction with other modes to create a custom web-based email interface. Q2. What happens to emails that cannot be delivered properly? A1. Any email that cannot be delivered to the server is saved in a Failed Mail Archive file or Failed Mail Archive database (depending on the version of MGI you are running).   Prior to version 1.6, failed mail was stored in the Failed Mail Archive file on the web server . You can find the Failed Mail Archive in the same location as the WebSTAR log file and MGI Server Log. If you are virtually hosted on a web server, contact the server administrator about the email. In all versions after 1.6, failed mail is stored in the Failed Mail Archive database. The Failed Mail Archive database is located in the MGI Data folder of the virtually hosted client that originally attempted to send the email. Emails in the Failed Mail Archive can be automatically re-attempted using a database search. You can find this code in the Web Based Email tutorial. Q3. Can I read or send attachments with mgiPOP? A1. In the current version of MGI, you cannot read or download attachments to the server or your computer and you cannot send attachments from your computer due to file upload and download problems and potential server space issues. Using a custom email solution, you could send files that are located on the server with the "attachmentFileLocation" parameter of mgiSendMail.