MFD scanning to Teams channel email address

%3CLINGO-SUB%20id%3D%22lingo-sub-1932448%22%20slang%3D%22en-US%22%3EMFD%20scanning%20to%20Teams%20channel%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1932448%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20that%20by%20posting%20this%20it%20will%20help%20others%20who%20have%20similar%20issues.%3C%2FP%3E%3CP%3EOur%20issue%20was%3A%3C%2FP%3E%3CP%3E-%20Moving%20departments%20from%20file%20shares%20to%20teams%2C%20staff%20were%20user%20MFD%20scan%20to%20file%20share%20functionality.%3C%2FP%3E%3CP%3EOur%20immediate%20response%20was%3A%3C%2FP%3E%3CP%3E-%20No%20problem%20we%20can%20setup%20Scan%20to%20Email%2C%20where%20the%20the%20user%20sends%20to%20the%20Teams%20%2F%20Channel%20email%20address%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20we%20did%20the%20testing%20it%20worked%20fine.%3C%2FP%3E%3CP%3EWhat%20we%20discovered%20was%20that%20our%20testing%20(5%20pages)%20and%20what%20actually%20was%20going%20on%20(50%20to%20100%20pages)%20caused%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESmall%20documents%20-%20scan%20to%20Teams%20%2F%20Channel%20email%20%3A%20no%20problem%3C%2FP%3E%3CP%3EBig%20documents%20-%26nbsp%3Bscan%20to%20Teams%20%2F%20Channel%20email%20%3A%20never%20appeared%20in%20the%20Channel.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20tried%20to%20figure%20out%20where%20the%20emails%20went.%3C%2FP%3E%3CP%3EIt%20turns%20out%20they%20were%20going%20via%20this%20route%20from%20the%20MFD%20scanner%20to%20the%20Teams%20%2F%20Channel%20%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3Epaper%20document%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3Eput%20document%20into%20MFD%20scanner%26nbsp%3B%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3Escanner%20creates%20PDF%20and%20emails%20it%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EMiddleware%20software%20provided%20by%20our%20printer%20provider%20gets%20the%20email%2C%20then%20sends%20it%20to%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EMS%20Exchange%20Mail%20relay%2C%20which%20accepts%20the%20scanner's%20email%20and%20attachment%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EMS%20Exchange%20Mail%20relay%20sends%20the%20email%20and%20attachment%20out%20as%20a%20valid%20email%20to%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EM365%20mail%20system%20(which%20provides%20some%20spam%20removal%20and%20protection%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-teams%2Fsecurity-scanning-protection-applied-to-teams-channel-emails%2Fm-p%2F669408%23M32617%22%20target%3D%22_self%22%3EReference%3C%2FA%3E)%20which%20sends%20it%20on%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3Eto%20Teams%20channel%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3Ewhich%20saves%20the%20attachment%20in%20'%3CCHANNELNAME%3E%2FEmail%20messages'%20SharePoint%20folder%3C%2FCHANNELNAME%3E%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAlong%20the%20way%20we%20found%20multiple%20places%20where%20LARGE%20documents%20were%20getting%20stopped.%3C%2FP%3E%3CP%3ETo%20get%20things%20flowing%20we%20did%20the%20following%3A%3C%2FP%3E%3CUL%3E%3CLI%3ETo%20reduce%20the%20size%20of%20the%20documents%20we%20reduced%20the%20default%20DPI%20setting%20on%20the%20MFD%20scanner%20to%20200dpi%2C%20but%20after%20testing%20we%20left%20the%20Auto%20Color%20setting.%3C%2FLI%3E%3CLI%3EWe%20found%20a%2020Mb%20limit%20on%20the%20Middle%20ware%20software%2C%20which%20we%20increased%26nbsp%3B%3C%2FLI%3E%3CLI%3EWe%20also%20found%20a%2020Mb%20limit%20for%20our%20Microsoft%20exchange%20mail%20relay%2C%20which%20we%20increased%26nbsp%3B%3C%2FLI%3E%3CLI%3EThough%20there%20is%20a%20stated%20limit%20on%20the%20size%20of%20emails%20to%20channels%20we%20haven't%20seen%20that%20come%20into%20play%20in%20our%20testing%20(we're%20not%20sure%20why).%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Flimits-specifications-teams%23emailing-a-channel%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EReference%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWith%20these%20settings%20we%20found%20that%20the%20scans%20turned%20up%20as%20attachments%20in%20the%20Teams%20%2F%20Channel.%20Yeah!%3C%2FP%3E%3CP%3EBut%20it%20took%203%20of%20us%20(1%20user%20and%202%20IT%20staff)%20about%20a%20week%20off%20an%20on%20to%20figure%20this%20out%2C%20mostly%20because%20once%20the%20email%20reaches%20the%20M365%20world%20there%20is%20no%20obvious%20logging%20%2F%20tracking%20or%20error%20notifications.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20looking%20at%20other%20printer%2Fscanner%20MFD%20middleware%20software%20that%20would%20allow%20%22Scan%20to%20sharepoint%22%20based%20on%20the%20printer's%20logged%20in%20user%20i.e.%20I%20go%20to%20the%20printer%2C%20fob%20login%2C%20then%20see%20a%20list%20of%20all%20the%20SharePoint%20sites%20I%20am%20a%20member%20of.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20that%20this%20helps%20others%20who%20are%20having%20similar%20issues%20by%20helping%20them%20understand%20where%20the%20scanned%20attachments%20may%20be%20being%20stopped.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1932448%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEmail%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%20channel%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Frequent Contributor

I hope that by posting this it will help others who have similar issues.

Our issue was:

- Moving departments from file shares to teams, staff were user MFD scan to file share functionality.

Our immediate response was:

- No problem we can setup Scan to Email, where the the user sends to the Teams / Channel email address

 

When we did the testing it worked fine.

What we discovered was that our testing (5 pages) and what actually was going on (50 to 100 pages) caused issues.

 

Small documents - scan to Teams / Channel email : no problem

Big documents - scan to Teams / Channel email : never appeared in the Channel.

 

So we tried to figure out where the emails went.

It turns out they were going via this route from the MFD scanner to the Teams / Channel :

  • paper document

  • put document into MFD scanner 

  • scanner creates PDF and emails it

  • Middleware software provided by our printer provider gets the email, then sends it to

  • MS Exchange Mail relay, which accepts the scanner's email and attachment

  • MS Exchange Mail relay sends the email and attachment out as a valid email to

  • M365 mail system (which provides some spam removal and protection Reference) which sends it on

  • to Teams channel

  • which saves the attachment in '<ChannelName>/Email messages' SharePoint folder

Along the way we found multiple places where LARGE documents were getting stopped.

To get things flowing we did the following:

  • To reduce the size of the documents we reduced the default DPI setting on the MFD scanner to 200dpi, but after testing we left the Auto Color setting.
  • We found a 20Mb limit on the Middle ware software, which we increased 
  • We also found a 20Mb limit for our Microsoft exchange mail relay, which we increased 
  • Though there is a stated limit on the size of emails to channels we haven't seen that come into play in our testing (we're not sure why). Reference

With these settings we found that the scans turned up as attachments in the Teams / Channel. Yeah!

But it took 3 of us (1 user and 2 IT staff) about a week off an on to figure this out, mostly because once the email reaches the M365 world there is no obvious logging / tracking or error notifications.

 

We are looking at other printer/scanner MFD middleware software that would allow "Scan to sharepoint" based on the printer's logged in user i.e. I go to the printer, fob login, then see a list of all the SharePoint sites I am a member of.

I hope that this helps others who are having similar issues by helping them understand where the scanned attachments may be being stopped.

0 Replies