3 Replies Latest reply on Jun 2, 2014 11:25 PM by Steven English

    MobilePrint v2 - Mail forward vs. proxy address (i.e. mail alias)

    Chris Axtell Navigator

      Digging through the "MobilePrint 2.0 Installation and Configuration Guide for Uniprint.pdf" documentation it follows similar directions to the MobilePrint v1 with regards configuring MobilePrint email address to managed different print formatting/types when using the Terminal Release option. Both versions recommend setting up a primary email account (e.g. print@university.edu) and then setting up all other email accounts (e.g. printcolor@univeristy.edu) (pg.  58) to be forwarded (from the server side) to the primary email address (pg. 59).

       

      So the question is does it have to be a mail forward, or can the alternative addresses be configured as a proxyAddresses (i.e. email alias) on the primary address? Since the "to" header remains the same in either case Pharos should be able to process the message in the same fashion for both options.

       

      Searching through the community site I didn't seem to find any discussion with regards to this oneway or the other, and was wondering which options people are using. Are there pros/cons (besides the obvious pro of having only one email account to manage when using proxy addresses) with with one vs. the other?

       

      Thanks,

      Chris

        • Re: MobilePrint v2 - Mail forward vs. proxy address (i.e. mail alias)
          Steven English Guide

          Chris,

           

          In my experience, as long as the address listed in the To: field survives the alias mapping/interpretation, you should be fine.  Since Exchange does not preserve the original To: address when utilizing an alias, I typically recommend that you set up two mailboxes (one as the IMAP box that MP checks, and the other to forward jobs to the primary mailbox).

           

          Exchange Only:

          The first address/mailbox would be something like mobileprint@mydomain.edu with an alias of bwprints@mydomain.edu.  This results in being able to advertise the email address bwprints@mydomain (which is parallel in name to the one for color jobs) so that emails sent to the bwprints address are delivered to the mobileprint mailbox, and appearing to have been sent to mobileprint@mydomain.edu (which is defined as the primary email address in the MP web admin).

          I then recommend setting up a second mailbox with an email address of coloprints@mydomain.edu.  It should be set to forward all mail to mobileprint@mydomain.edu.  (If using PowerShell... Set-Mailbox -Identity colorprints -ForwardingAddress mobileprint@mydomain.edu -DeliverToMailboxAndForward $False). 

          The reason for the triple email addresses is that MP (at least 1.3.2) sends out the job status notifications and registration requests from the primary email address as defined in the we admin.  This configuration allows the outgoing emails that students receive to originate from mobileprint@mydomain.edu instead of bwprints@mydomain.edu which could be confusing if a student is printing a color job and receiving a confirmation from bwprints.  The mail forward on colorprint allows emails sent to colorprints to be delivered to the mobileprint mailbox while preserving the original destination in the To: field, and setting the mailbox delivery option to false prevents the mailbox from filling up.


          Edit:  To answer your question more specifically, I have used both aliases and forwards.  When Pharos checks the single IMAP mailbox for which it has been configured, the important thing is that MP is going to attempt to match up the To: address on each of the emails in the inbox to the various email addresses configured in the web admin in order to determine mono vs. color, and simplex vs. duplex.  If the to address is modified - as Exchange does for aliases - the student is not going to get a print job that matches what they wanted.  As long as the To: address is maintained (or the change is anticipated as with the Exchange configuration above), you should be fine regardless of wether you are using separate mailboxes with forwards, aliases, or any other configuration.

           

          Regards,

          Steven

           

          P.S.  If you are not using exchange, just set up a single email address with a single alias for color jobs.  I typically recommend a generic name so that outgoing emails do not generate confusion.

          1 of 1 people found this helpful
            • Re: MobilePrint v2 - Mail forward vs. proxy address (i.e. mail alias)
              Chris Axtell Navigator

              Hi Steven,

               

              Your comment about how Exchange deals with alias had me experimenting. We have an Exchange server here and I frequently get email to one of several alias where the alias address is displayed in the "to" line. Looking into the behavior a bit more and it seams that what is displayed in the "to" line depends on what email client is being used to access the message. Microsoft's Exchange clients (Outlook 2010, 2011, 2013) replace the email alias with that of the primary address, whereas other mail clients may or may not do the same substitution.

               

              Your suggestion would be the most straight forward method of making sure you get consistent results.

               

              Thanks,

              Chris

                • Re: MobilePrint v2 - Mail forward vs. proxy address (i.e. mail alias)
                  Steven English Guide

                  Chris,

                   

                  One other thing to consider is that if you are utilizing the upload feature, the uploaded jobs will default to the attributes assigned to the primary email address defined in the MP web admin.  That would be a possible reason to flip-flop the color and mono email addresses.  In MP 2.0 which released today, the expectation is that even if you disable the ability to release the print jobs from within My Print Center, users CAN use the document options buttons to modify the document properties for release via another release mechanism (Pharos Station, iMFP, Omega, Remote, and so forth).  This is a huge improvement over 1.3.2 for those who do not wish to allow releasing jobs from the web page or from a cell phone, but still want users to have the ability to control what they get on the printer without having to upload a document 5 times (or forward it 5 times) just to get 5 copies, nor will they have to jump through hoops to keep or eliminate color from their jobs when uploading in MP 2.0.

                   

                  Regards,

                  Steven