Scanning to Email with Office 365

KB Home   |   Scanning to Email with Office 365

Main.Office365 History

Hide minor edits - Show changes to output

November 21, 2018, at 06:20 AM by Aaron Pouliot - Added category - Integrated Scanning
Changed line 16 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]], [[Category.Troubleshooting|+]]
to:
''Categories:'' [[Category.IntegratedScanning|+]]
October 31, 2018, at 03:38 AM by TimG - Updated to refer to the 'sender unauthenticated' issue seen when using scan to email with Office 365
Changed lines 1-26 from:
(:title Email To Print with Microsoft Exchange and Email Aliases:)

Customers using our Email to Print feature with a Microsoft Exchange Server report that they will get emails bounced back stating "Your Email to Print job was received, but the printer's email address was not recognized. Please check the email and try again". This is because Microsoft Exchange modifies the email address header information, which subsequently affects PaperCut's ability to detect the printer alias to which the email was originally sent.

Within PaperCut, we have two Email address settings:

1) Global address (the mailbox which PaperCut checks for Emails):\\
Options > Mobile & BYOD > Email to Print > Username

2) Printer-specific alias (the address that identifies to which printer
the job should be sent):\\
Printers > (affected printer) > Email to Print > Email Address

!!!Aliases are set up in Exchange or Gmail - outside of our software
.

Some
email systems, like Microsoft Exchange, strip the alias address from the header and replace it with the end-destination email address.

The ''To:'' field will always show the global email address:  @@printers@school.edu@@\\
Rather than
the printer-specific aliases: @@printer1@school.edu@@

If you login to the Global mailbox and examine
the Header information in an email, do you see the printer-specific alias, or the global address?  If you see the global address, and the printer-specific alias has been stripped, those clients won't be able to use an alias with Email to Print.

!!!Workaround:

One workaround found by one of our customers is to use distribution groups - for example in the case above, you would set up a distribution list called @@printer1@school.edu@@ - then add @@printers@school.edu@@ as the only member of that DL. When you send a test email to that DL, it should then retain the DL name - i.e. @@printer1@school.edu@@ in the 'To:' field of the email.


to:
(:title Scanning to Email with Office 365:)

Customers using our Scanning (Integrated Scanning) feature may come across an issue when using Office 365 where you'll see a message hinting that the sender is unauthenticated.

The issue normally happens when the device is trying to send
the scan by email, using the user's 'from' address. In that instance, the device logs into Office 365 using the device-configured account, and the email is attempting to send from the user's email address - which can result in a 'sender is unauthenticated' message, or similar.

With Office 365, the SMTP username and password must match the user logging into the device (however that's not really appropriate, because the user logging into
the device will change all the time).

So... as an alternative, Microsoft have a few different suggestions for getting around that issue, listed in their [=TechNet=] article [[https://support
.office.com/en-us/article/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-365-69f58e99-c550-4274-ad18-c805d654b4c4|How to set up a multifunction device or application to send email using Office 365]].

We've heard from customers that any of their suggested methods work, with the easiest option being
the first option, but other customers have also reported success with the 3rd option of setting up the relay.

See more [[https://www.papercut.com/kb/Main/CommonIntergratedScanningquestions|Common Integrated Scanning Questions]]
.
Changed line 18 from:
[-Keywords: Email, BYOD, Microsoft Exchange, Office 365, Windows-]
to:
[-Keywords: Email, Integrated Scanning, Scan to Email, Device Scanning, Microsoft Exchange, Office 365, Windows-]
April 07, 2015, at 12:17 AM by TimG - Updated to add workaround from customer in the comments
Changed lines 3-4 from:
Customers using our Email to Print feature with a Microsoft Exchange Server report email delivery failures on known email addresses. This is because Microsoft Exchange modifies the email address header information, which subsequently affects PaperCut's ability to detect the printer alias to which the email was originally sent.
to:
Customers using our Email to Print feature with a Microsoft Exchange Server report that they will get emails bounced back stating "Your Email to Print job was received, but the printer's email address was not recognized. Please check the email and try again". This is because Microsoft Exchange modifies the email address header information, which subsequently affects PaperCut's ability to detect the printer alias to which the email was originally sent.
Changed lines 17-19 from:
The ''To:'' field will always show the global email address:  @@printers@testsite.edu@@\\
Rather than the printer-specific aliases: @@printer1@testsite.edu@@
to:
The ''To:'' field will always show the global email address:  @@printers@school.edu@@\\
Rather than the printer-specific aliases: @@printer1@school.edu@@
Changed lines 24-26 from:
At this time, the only known workaround is to use Gmail or a similar non-Microsoft Exchange email system.

to:
One workaround found by one of our customers is to use distribution groups - for example in the case above, you would set up a distribution list called @@printer1@school.edu@@ - then add @@printers@school.edu@@ as the only member of that DL. When you send a test email to that DL, it should then retain the DL name - i.e. @@printer1@school.edu@@ in the 'To:' field of the email.

Changed lines 1-2 from:
(:title Email To Print Issues with Microsoft Exchange and Email Aliases:)
to:
(:title Email To Print with Microsoft Exchange and Email Aliases:)
Changed line 28 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips & Tricks|+]], [[Category.Troubleshooting|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]], [[Category.Troubleshooting|+]]
Changed line 28 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]], [[Category.Troubleshooting|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips & Tricks|+]], [[Category.Troubleshooting|+]]
Changed line 30 from:
[-Keywords: Microsoft Exchange,Office 365, BYOD, Email-]
to:
[-Keywords: Email, BYOD, Microsoft Exchange, Office 365, Windows-]
Changed line 28 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]], [[Category.Troubleshooting|+]]
Changed line 28 from:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]], [[Category.Tips and Tricks|+]]
Changed line 30 from:
[-Keywords: relay, Office 365, BYOD-]
to:
[-Keywords: Microsoft Exchange,Office 365, BYOD, Email-]
Changed line 28 from:
''Categories:'' [[Category.Architecture|+]]
to:
''Categories:'' [[Category.Architecture|+]], [[Category.Windows|+]]
Changed lines 24-26 from:
At this time, the only known workaround is to use Gmail or a similar non-exchange email system.

to:
At this time, the only known workaround is to use Gmail or a similar non-Microsoft Exchange email system.

Changed line 17 from:
The ''To:'' field will always show the global email address:  printers@testsite.edu\\
to:
The ''To:'' field will always show the global email address:  @@printers@testsite.edu@@\\
Changed line 17 from:
The ''To:'' field will always show the global email address:  printers@testsite.edu
to:
The ''To:'' field will always show the global email address:  printers@testsite.edu\\
Changed line 17 from:
The To: field will always show the global email address:  printers@testsite.edu
to:
The ''To:'' field will always show the global email address:  printers@testsite.edu
Changed lines 15-16 from:
Some email systems, like Microsoft Exchange, strip the alias address from the header and replace it with the end-destination email address, so the To: field will always show the global email address:  printers@testsite.edu
to:
Some email systems, like Microsoft Exchange, strip the alias address from the header and replace it with the end-destination email address.

The
To: field will always show the global email address:  printers@testsite.edu
Changed line 7 from:
1) Global address (the mailbox which PaperCut checks for Emails):
to:
1) Global address (the mailbox which PaperCut checks for Emails):\\
Changed line 10 from:
2) Printer-specific alias (the address that identifies to which printer the job should be sent):
to:
2) Printer-specific alias (the address that identifies to which printer the job should be sent):\\
Changed lines 7-10 from:
1) Global address (the mailbox which PaperCut checks for Emails):  Options > Mobile & BYOD > Email to Print > Username

2) Printer-specific alias (the address that identifies to which printer the job should be sent):  Printers > (affected printer) > Email to Print > Email Address
to:
1) Global address (the mailbox which PaperCut checks for Emails):
Options > Mobile & BYOD > Email to Print > Username

2) Printer-specific alias (the address that identifies to which printer the job should be sent):
Printers > (affected printer) > Email to Print > Email Address
Changed lines 7-9 from:
Global address (the mailbox which PaperCut checks for Emails):  Options > Mobile & BYOD > Email to Print > Username
Printer-specific alias (the address that identifies to which printer the job should be sent):  Printers > (affected printer) > Email to Print > Email Address
to:
1) Global address (the mailbox which PaperCut checks for Emails):  Options > Mobile & BYOD > Email to Print > Username

2)
Printer-specific alias (the address that identifies to which printer the job should be sent):  Printers > (affected printer) > Email to Print > Email Address
Changed lines 3-4 from:
Customers using our Email to Print feature with an Exchange Server sometimes report email delivery failures on known email addresses. Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see which printer alias to which the email was originally sent.
to:
Customers using our Email to Print feature with a Microsoft Exchange Server report email delivery failures on known email addresses. This is because Microsoft Exchange modifies the email address header information, which subsequently affects PaperCut's ability to detect the printer alias to which the email was originally sent.
Changed lines 8-9 from:
Printer-specific alias (the address that identifies which printer the job should be sent to):  Printers > (affected printer) > Email to Print > Email Address
to:
Printer-specific alias (the address that identifies to which printer the job should be sent):  Printers > (affected printer) > Email to Print > Email Address
Changed lines 10-11 from:
Aliases are set up in Exchange or Gmail - outside of our software.
to:
!!!Aliases are set up in Exchange or Gmail - outside of our software.
Changed lines 10-11 from:
!Aliases are set up in Exchange or Gmail - outside of our software.
to:
Aliases are set up in Exchange or Gmail - outside of our software.
Changed lines 10-11 from:
!!Aliases are set up in Exchange or Gmail - outside of our software.
to:
!Aliases are set up in Exchange or Gmail - outside of our software.
Changed lines 10-11 from:
Aliases are set up in Exchange or Gmail - outside of our software.
to:
!!Aliases are set up in Exchange or Gmail - outside of our software.
Changed lines 20-22 from:
At this time, the only known workaround is to use a Gmail or a similar non-exchange email system.

to:
At this time, the only known workaround is to use Gmail or a similar non-exchange email system.

January 14, 2015, at 05:30 PM by Don Jacobson - Remove not helpful workaround suggestion.
Changed lines 3-4 from:
Customers using our Email to Print feature in conjunction with an Exchange Server sometimes report email delivery failures on known email addresses. Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see which printer alias the email was originally sent to.
to:
Customers using our Email to Print feature with an Exchange Server sometimes report email delivery failures on known email addresses. Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see which printer alias to which the email was originally sent.
Changed lines 10-11 from:
Aliases are set up in e.g. Exchange or Gmail - outside of our software.
to:
Aliases are set up in Exchange or Gmail - outside of our software.
Changed lines 18-24 from:
!!!Workarounds:

1)  One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article on [[https://www.papercut.com/products/ng/manual/email-to-print.html#email-to-print-before-you-start|achieving printer aliases in PaperCut]]

2) Another workaround is to use a Gmail or a similar non-exchange email system instead
.

to:
!!!Workaround:

At this time, the only known workaround is to use a Gmail or a similar non-exchange email system.

Changed lines 3-6 from:
Customers using our Email to Print feature in conjunction with an Exchange Server sometimes report email delivery failures on known email addresses.  '''This is an Alias resolution issue.'''

Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see which printer alias the email was originally sent to.
to:
Customers using our Email to Print feature in conjunction with an Exchange Server sometimes report email delivery failures on known email addresses. Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see which printer alias the email was originally sent to.
January 09, 2015, at 01:22 AM by TimG - Updated additional text
Changed lines 1-15 from:
(:title Email To Print Issues with Microsoft Exchange & Microsoft Office 365:)

Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  '''This is an Alias resolution issue.'''

Office 365 modifies our email address header information,
which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)

Within our software, we have two Email addresses settings:

Global address:  Options > Mobile & BYOD > Email
to Print > Username
Printer-specific alias:  Printers
> (affected printer) > Email to Print > Email Address

Aliases are set up in Exchange or Gmail - outside of our
software.

Some email clients, like Microsoft Exchange, strips the alias address from the header before it is delivered, so the To: field will always show the global email address:  printers@testsite.edu
to:
(:title Email To Print Issues with Microsoft Exchange and Email Aliases:)

Customers using our Email to Print feature in conjunction with an Exchange Server sometimes report email delivery failures on known email addresses.  '''This is an Alias resolution issue.'''

Exchange modifies the email address header information, which subsequently affects PaperCut's ability to see
which printer alias the email was originally sent to.

Within PaperCut, we have two Email address settings:

Global address (the mailbox which PaperCut checks for Emails):  Options > Mobile & BYOD > Email to Print > Username
Printer-specific alias (the address that identifies which printer the job should be sent
to):  Printers > (affected printer) > Email to Print > Email Address

Aliases are set up in e.g. Exchange or Gmail - outside of our
software.

Some email systems, like Microsoft Exchange, strip the alias address from the header and replace it with the end-destination email address, so the To: field will always show the global email address:  printers@testsite.edu
Changed lines 18-28 from:
If you login to the Global email address, do you see the full alias name, or the regular email box?  If you see the global email box, and the alias portion has been stripped, those clients won't be able to use an alias with Email to Print.

!!!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.

1)  One workaround in our software is
to use separate email accounts & email forwarding, as shown in this KB article:

Before You Start: Aliases > Email forwarding\\
[https://www
.papercut.com/products/ng/manual/email-to-print.html]

2) Another workaround is to use a Gmail or a similar email program instead.

to:
If you login to the Global mailbox and examine the Header information in an email, do you see the printer-specific alias, or the global address?  If you see the global address, and the printer-specific alias has been stripped, those clients won't be able to use an alias with Email to Print.

!!!Workarounds:

1)  One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article on [[https://www.papercut.com/products/ng/manual/email-
to-print.html#email-to-print-before-you-start|achieving printer aliases in PaperCut]]

2) Another workaround is to use a Gmail or a similar non-exchange email system instead
.

Changed lines 20-21 from:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
to:
!!!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
Changed lines 20-21 from:
!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
to:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
Changed lines 20-21 from:
!!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
to:
!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
Changed lines 20-21 from:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
to:
!!At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.
January 08, 2015, at 03:24 PM by Don Jacobson - clean-up
Changed lines 20-22 from:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.  One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:

Before You Start: Aliases > Email forwarding
to:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.

1)
  One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:

Before You Start: Aliases > Email forwarding\\
Changed lines 27-28 from:
Another workaround is to use a Gmail or a similar email program instead.
to:
2) Another workaround is to use a Gmail or a similar email program instead.
Changed lines 20-28 from:
One workaround in our software may be to use separate email accounts & email forwarding, as shown in this KB article:
https://www.papercut.com/products/ng/manual/email-to-print.html
(Before You Start: Aliases > Email forwarding)

One workaround in our software is to use separate email accounts & email forwarding, as shown in the
[[https://www.papercut.com/products/ng/manual/email-to-print.html|Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.

Many customers that experience relay issues with Office 365 have resolved them by using a forwarded address.

Customers with a mixed, hybrid environment may need to move the mailboxes out to the cloud and reconfigure the settings in PaperCut in order to avoid email delivery failures on known email addresses.
to:
At this time, Microsoft Exchange & Office 365 products may not work with our Email to Print module.  One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:

Before You Start: Aliases > Email forwarding
[https://www.papercut.com/products/ng/manual/email-to-print.html]

Another workaround is to use a Gmail or a similar email program instead
.
Changed line 9 from:
Global address:  Options > Mobile & BYOD > Email to Print > Usernname
to:
Global address:  Options > Mobile & BYOD > Email to Print > Username
Changed lines 16-19 from:
Rather than the printer-specific aliases:  printer1@testsite.edu

If you login to the Glopbal email address, do you see the full alias name, or the regular email box?  If you see the global email box, and the alias portion has been stripped, those clients won't be able to use an alias with Email to Print.
to:
Rather than the printer-specific aliases: @@printer1@testsite.edu@@

If you login to the Global email address, do you see the full alias name, or the regular email box?  If you see the global email box, and the alias portion has been stripped, those clients won't be able to use an alias with Email to Print.
Changed lines 24-26 from:
One workaround in our software is to use separate email accounts & email forwarding, as shown in the [[https://www.papercut.com/products/ng/manual/email-to-print.html
Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.
to:
One workaround in our software is to use separate email accounts & email forwarding, as shown in the [[https://www.papercut.com/products/ng/manual/email-to-print.html|Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.
Changed lines 3-4 from:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  '''This is an Authentication issue.'''
to:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  '''This is an Alias resolution issue.'''
Changed lines 24-25 from:
One workaround in our software is to use separate email accounts & email forwarding, as shown in the [[https://www.papercut.com/products/ng/manual/email-to-print.html|Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.
to:
One workaround in our software is to use separate email accounts & email forwarding, as shown in the [[https://www.papercut.com/products/ng/manual/email-to-print.html
Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.
Changed lines 1-3 from:
(:title Email To Print Issues with
Microsoft Exchange & Microsoft Office 365:)
to:
(:title Email To Print Issues with Microsoft Exchange & Microsoft Office 365:)
Changed lines 1-2 from:
(:title Email To Print Issues with Microsoft Exchange & Microsoft Office 365:)
to:
(:title Email To Print Issues with
Microsoft Exchange & Microsoft Office 365:)
Changed lines 10-12 from:
1.  Global address:  Options > Mobile & BYOD > Email to Print > Usernname
2.  Printer-specific alias:  Printers > (affected printer) > Email to Print > Email Address
to:
Global address:  Options > Mobile & BYOD > Email to Print > Usernname
Printer-specific alias:  Printers > (affected printer) > Email to Print > Email Address
October 28, 2014, at 06:06 PM by Don Jacobson - Added more text to clarify.
Changed lines 1-2 from:
(:title Office 365 Relay Issues with Email To Print:)
to:
(:title Email To Print Issues with Microsoft Exchange & Microsoft Office 365:)
Added lines 7-23:
Within our software, we have two Email addresses settings:

1.  Global address:  Options > Mobile & BYOD > Email to Print > Usernname
2.  Printer-specific alias:  Printers > (affected printer) > Email to Print > Email Address

Aliases are set up in Exchange or Gmail - outside of our software.

Some email clients, like Microsoft Exchange, strips the alias address from the header before it is delivered, so the To: field will always show the global email address:  printers@testsite.edu

Rather than the printer-specific aliases:  printer1@testsite.edu

If you login to the Glopbal email address, do you see the full alias name, or the regular email box?  If you see the global email box, and the alias portion has been stripped, those clients won't be able to use an alias with Email to Print.

One workaround in our software may be to use separate email accounts & email forwarding, as shown in this KB article:
https://www.papercut.com/products/ng/manual/email-to-print.html
(Before You Start: Aliases > Email forwarding)

September 09, 2014, at 05:44 PM by Rick - wordsmithing
Changed lines 7-17 from:
One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:


https:
//www.papercut.com/products/ng/manual/email-to-print.html\\
'''Before You Start: Aliases > Email forwarding
'''\\


Many customers having relay issues with Office 365 have reported success when using a forwarded address.

Customers with a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured
the settings in PaperCut, the error messages stopped.\\
to:
One workaround in our software is to use separate email accounts & email forwarding, as shown in the [[https://www.papercut.com/products/ng/manual/email-to-print.html|Email to Print]] section of the User Guide under the '''Before You Start: Aliases > Email forwarding''' heading.

Many customers that experience relay issues with Office 365 have resolved them by using a forwarded address.

Customers with a mixed, hybrid environment may need to move the mailboxes out to
the cloud and reconfigure the settings in PaperCut in order to avoid email delivery failures on known email addresses.
Changed line 15 from:
[-Keywords: relay, Office 365-]
to:
[-Keywords: relay, Office 365, BYOD-]
Changed lines 16-17 from:
Customers having a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured the settings in PaperCut, the error messages stopped.\\
to:
Customers with a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured the settings in PaperCut, the error messages stopped.\\
August 22, 2014, at 10:24 PM by Don Jacobson -
August 22, 2014, at 10:22 PM by Don Jacobson -
Changed lines 1-2 from:
(:title Office 365 Relay Issues:)
to:
(:title Office 365 Relay Issues with Email To Print:)
August 22, 2014, at 10:20 PM by Don Jacobson -
Changed line 19 from:
''Categories:'' [[Architecture|+]]
to:
''Categories:'' [[Category.Architecture|+]]
August 22, 2014, at 10:19 PM by Don Jacobson -
Changed line 19 from:
''Categories:'' [[Office 365|+]]
to:
''Categories:'' [[Architecture|+]]
August 22, 2014, at 10:16 PM by Don Jacobson -
August 22, 2014, at 10:13 PM by Don Jacobson -
Changed line 19 from:
''Categories:'' [[Category.Office365|+]]
to:
''Categories:'' [[Office 365|+]]
August 22, 2014, at 10:12 PM by Don Jacobson -
Added line 13:
August 22, 2014, at 10:11 PM by Don Jacobson -
August 22, 2014, at 10:11 PM by Don Jacobson -
Changed line 10 from:
https://www.papercut.com/products/ng/manual/email-to-print.html
to:
https://www.papercut.com/products/ng/manual/email-to-print.html\\
August 22, 2014, at 10:11 PM by Don Jacobson -
Added line 10:
https://www.papercut.com/products/ng/manual/email-to-print.html
Changed lines 12-13 from:
https://www.papercut.com/products/ng/manual/email-to-print.html
to:
August 22, 2014, at 10:10 PM by Don Jacobson -
Changed line 18 from:
''Categories:'' [[Category.Office 365|+]]
to:
''Categories:'' [[Category.Office365|+]]
August 22, 2014, at 07:50 PM by Don Jacobson -
Changed line 10 from:
'''Before You Start: Aliases > Email forwarding'''
to:
'''Before You Start: Aliases > Email forwarding'''\\
August 22, 2014, at 07:49 PM by Don Jacobson -
Changed line 18 from:
''Categories:'' [[Category.relay|+]]
to:
''Categories:'' [[Category.Office 365|+]]
Changed line 20 from:
[-Keywords: relay, Office 365-]
to:
[-Keywords: relay, Office 365-]
August 22, 2014, at 07:49 PM by Don Jacobson -
Deleted line 10:
August 22, 2014, at 07:48 PM by Don Jacobson -
Changed lines 10-11 from:
'''Before You Start: Aliases > Email forwarding
to:
'''Before You Start: Aliases > Email forwarding'''
August 22, 2014, at 07:48 PM by Don Jacobson -
Changed lines 10-11 from:
'''Before You Start: Aliases > Email forwarding'''
to:
'''Before You Start: Aliases > Email forwarding
August 22, 2014, at 07:48 PM by Don Jacobson -
Changed lines 5-6 from:
Office 365 modifies our email address header information, which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)\\
to:
Office 365 modifies our email address header information, which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)
August 22, 2014, at 07:47 PM by Don Jacobson -
Changed line 20 from:
[-Keywords: relay, Office365-]
to:
[-Keywords: relay, Office 365-]
August 22, 2014, at 07:47 PM by Don Jacobson -
Changed line 18 from:
''Categories:'' [[Category.relay|+]], [[Category.Office 365|+]]
to:
''Categories:'' [[Category.relay|+]]
August 22, 2014, at 07:46 PM by Don Jacobson -
Changed lines 10-11 from:
Before You Start: Aliases > Email forwarding
to:
'''Before You Start: Aliases > Email forwarding'''
August 22, 2014, at 07:45 PM by Don Jacobson -
Changed line 19 from:
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
to:
''Categories:'' [[Category.relay|+]], [[Category.Office 365|+]]
August 22, 2014, at 07:43 PM by Don Jacobson -
Changed lines 14-15 from:
Many customers having relay issues with Office 365 have reported success when using a forwarded address.\\
to:
Many customers having relay issues with Office 365 have reported success when using a forwarded address.
August 22, 2014, at 07:41 PM by Don Jacobson -
Changed lines 4-5 from:
\\
to:
Changed lines 7-9 from:
\\One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:
\\
to:
One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:

Changed line 11 from:
\\
to:
Changed lines 13-14 from:
\\
to:
Changed lines 15-16 from:
\\
to:
August 22, 2014, at 07:40 PM by Don Jacobson -
Changed lines 3-5 from:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.\\

\\!!This is an Authentication
issue.
to:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  '''This is an Authentication issue.'''
August 22, 2014, at 07:34 PM by Don Jacobson -
Added line 4:
Added line 7:
Added line 9:
Added line 12:
Added line 17:
Added line 20:
Added line 22:
August 22, 2014, at 07:30 PM by Don Jacobson -
Changed line 4 from:
!!This is an Authentication issue.
to:
\\!!This is an Authentication issue.
Changed line 7 from:
One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:
to:
\\One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:
Changed line 13 from:
Many customers having relay issues with Office 365 have reported success when using a forwarded address.
to:
Many customers having relay issues with Office 365 have reported success when using a forwarded address.\\
August 22, 2014, at 07:29 PM by Don Jacobson -
Changed lines 3-4 from:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  This is an Authentication issue.
to:
Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.\\
!!
This is an Authentication issue.
Changed line 6 from:
Office 365 modifies our email address header information, which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)
to:
Office 365 modifies our email address header information, which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)\\
Changed line 15 from:
Customers having a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured the settings in PaperCut, the error messages stopped.
to:
Customers having a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured the settings in PaperCut, the error messages stopped.\\
August 22, 2014, at 07:28 PM by Don Jacobson - new KB
Added lines 1-18:
(:title Office 365 Relay Issues:)

Customers using our Email to Print feature in conjunction with an Exchange Server and Microsoft Office 365 sometimes report email delivery failures on known email addresses.  This is an Authentication issue.
\\
Office 365 modifies our email address header information, which subsequently affects routing & delivery to the final destination address.  (Office 365 does not link to Active Directory; it has its own set of User Names which it maps to Active Directory entries.)
One workaround in our software is to use separate email accounts & email forwarding, as shown in this KB article:
\\
Before You Start: Aliases > Email forwarding
\\
https://www.papercut.com/products/ng/manual/email-to-print.html
\\
Many customers having relay issues with Office 365 have reported success when using a forwarded address.
\\
Customers having a mixed, hybrid environment sometimes need to move the mailboxes out to the cloud.  Once they did and reconfigured the settings in PaperCut, the error messages stopped.
----
''Categories:'' [[Category.TODOFirstCategory|+]], [[Category.TODOSecondCategoryIfNeeded|+]]
----
[-Keywords: relay, Office365-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on November 21, 2018, at 06:20 AM
Printable View   |   Article History   |   Edit Article