SCAN TO EMAIL USING O365 Cloud Email

Use this forum if you want to discuss a problem or ask a question related to a hMailServer beta release.
Post Reply
maykol1
New user
New user
Posts: 4
Joined: 2018-04-26 11:37

SCAN TO EMAIL USING O365 Cloud Email

Post by maykol1 » 2018-04-26 11:58

Hi Everyone/hMAILServer Admin,

Good day, I have a problem regarding my scan to email, We are using RICOH MF Printers, the problem is, the printer was already sent the data to hmail server but the hmail relay won't sent it to the receiver, this is the logs I've got. Can you explain what this is?

"SMTPC" 1316 161 "2018-04-26 14:03:07.827" "40.100.29.194" "RECEIVED: 550 5.7.60 SMTP; Client does not have permissions to send as this sender [KU1PR02MB2423.apcprd02.prod.outlook.com]"
"SMTPC" 1316 161 "2018-04-26 14:03:07.827" "40.100.29.194" "SENT: QUIT"
"SMTPC" 1988 161 "2018-04-26 14:03:07.874" "40.100.29.194" "RECEIVED: 221 2.0.0 Service closing transmission channel"

I've just only encountered this to scan to email, but it other APPS it works perfectly, please help me on this, We are using O365 Mail Cloud Based.

Thanks,

Mike

User avatar
mattg
Moderator
Moderator
Posts: 22435
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by mattg » 2018-04-26 14:03

maykol1 wrote:
2018-04-26 11:58
"RECEIVED: 550 5.7.60 SMTP; Client does not have permissions to send as this sender [KU1PR02MB2423.apcprd02.prod.outlook.com]"
What is the name of the Ricoh machine?

Does KU1PRO2MB2423 fit?
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

maykol1
New user
New user
Posts: 4
Joined: 2018-04-26 11:37

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by maykol1 » 2018-05-02 05:33

Hi Mattg,

Thank you for your response, I think "KU1PR02MB2423.apcprd02.prod.outlook.com" is one of the cloud server in outlook, hmailserver does it jobs on our other applications, Notifications on the other applications has no problem, we are facing this issue only at SCAN TO EMAIL of the RICOH PRINTER, exact model is:

RICOH MP 5055
Model Name : MP 5055
Machine ID : C387PA00161

Sorry for the delay response, could you help me on this.

Thanks,

Mike

User avatar
mattg
Moderator
Moderator
Posts: 22435
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by mattg » 2018-05-02 06:24

show logging from start to end please.

That snippet clearly shows that the remote server rejected the mail and why, but I can't see what happened before that connection....
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

maykol1
New user
New user
Posts: 4
Joined: 2018-04-26 11:37

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by maykol1 » 2018-05-02 12:29

hi mattg,

I apologize for that, below is the full logs of scan to email process.

Thanks,

MIke

==========================

"SMTPD" 2028 158 "2018-04-26 14:02:00.887" "10.230.75.226" "SENT: 220 2go-alert-dev.2go.com ESMTP"
"SMTPD" 1172 158 "2018-04-26 14:02:00.887" "10.230.75.226" "RECEIVED: HELO 2GOPRN02.2go.com"
"SMTPD" 1172 158 "2018-04-26 14:02:00.887" "10.230.75.226" "SENT: 250 Hello."
"SMTPD" 1956 158 "2018-04-26 14:02:00.903" "10.230.75.226" "RECEIVED: MAIL FROM:<michael_erandio@2go.com.ph>"
"SMTPD" 1956 158 "2018-04-26 14:02:00.903" "10.230.75.226" "SENT: 250 OK"
"SMTPD" 1316 158 "2018-04-26 14:02:00.918" "10.230.75.226" "RECEIVED: RCPT TO:<michael_erandio@2go.com.ph>"
"SMTPD" 1316 158 "2018-04-26 14:02:00.918" "10.230.75.226" "SENT: 250 OK"
"SMTPD" 1956 158 "2018-04-26 14:02:00.934" "10.230.75.226" "RECEIVED: DATA"
"SMTPD" 1956 158 "2018-04-26 14:02:00.934" "10.230.75.226" "SENT: 354 OK, send."
"SMTPD" 1832 158 "2018-04-26 14:02:01.027" "10.230.75.226" "SENT: 250 Queued (0.096 seconds)"
"SMTPD" 1316 158 "2018-04-26 14:02:01.027" "10.230.75.226" "RECEIVED: QUIT"
"SMTPD" 1316 158 "2018-04-26 14:02:01.027" "10.230.75.226" "SENT: 221 goodbye"
"SMTPC" 1956 160 "2018-04-26 14:02:01.168" "40.100.29.18" "RECEIVED: 220 SG2PR0401CA0013.outlook.office365.com Microsoft ESMTP MAIL Service ready at Thu, 26 Apr 2018 06:02:18 +0000"
"SMTPC" 1956 160 "2018-04-26 14:02:01.168" "40.100.29.18" "SENT: EHLO 2go-alert-dev.2go.com"
"SMTPC" 1980 160 "2018-04-26 14:02:01.246" "40.100.29.18" "RECEIVED: 250-SG2PR0401CA0013.outlook.office365.com Hello [222.127.101.2][nl]250-SIZE 157286400[nl]250-PIPELINING[nl]250-DSN[nl]250-ENHANCEDSTATUSCODES[nl]250-STARTTLS[nl]250-8BITMIME[nl]250-BINARYMIME[nl]250-CHUNKING[nl]250 SMTPUTF8"
"SMTPC" 1980 160 "2018-04-26 14:02:01.246" "40.100.29.18" "SENT: STARTTLS"
"SMTPC" 2036 160 "2018-04-26 14:02:01.293" "40.100.29.18" "RECEIVED: 220 2.0.0 SMTP server ready"
"SMTPC" 1988 160 "2018-04-26 14:02:01.417" "40.100.29.18" "SENT: EHLO 2go-alert-dev.2go.com"
"SMTPC" 2036 160 "2018-04-26 14:02:01.464" "40.100.29.18" "RECEIVED: 250-SG2PR0401CA0013.outlook.office365.com Hello [222.127.101.2][nl]250-SIZE 157286400[nl]250-PIPELINING[nl]250-DSN[nl]250-ENHANCEDSTATUSCODES[nl]250-AUTH LOGIN XOAUTH2[nl]250-8BITMIME[nl]250-BINARYMIME[nl]250-CHUNKING[nl]250 SMTPUTF8"
"SMTPC" 2036 160 "2018-04-26 14:02:01.464" "40.100.29.18" "SENT: AUTH LOGIN"
"SMTPC" 1980 160 "2018-04-26 14:02:01.511" "40.100.29.18" "RECEIVED: 334 VXNlcm5hbWU6"
"SMTPC" 1980 160 "2018-04-26 14:02:01.527" "40.100.29.18" "SENT: MmdvLm5vdGlmaWNhdGlvbi50ZXN0QDJnby5jb20ucGg="
"SMTPC" 2028 160 "2018-04-26 14:02:01.573" "40.100.29.18" "RECEIVED: 334 UGFzc3dvcmQ6"
"SMTPC" 2028 160 "2018-04-26 14:02:01.573" "40.100.29.18" "SENT: ***"
"SMTPC" 2036 160 "2018-04-26 14:02:03.040" "40.100.29.18" "RECEIVED: 235 2.7.0 Authentication successful target host KU1PR02MB2423.apcprd02.prod.outlook.com"
"SMTPC" 2036 160 "2018-04-26 14:02:03.040" "40.100.29.18" "SENT: ***"
"SMTPC" 1980 160 "2018-04-26 14:02:03.196" "40.100.29.18" "RECEIVED: 250 2.1.0 Sender OK"
"SMTPC" 1980 160 "2018-04-26 14:02:03.196" "40.100.29.18" "SENT: RCPT TO:<michael_erandio@2go.com.ph>"
"SMTPC" 2028 160 "2018-04-26 14:02:03.289" "40.100.29.18" "RECEIVED: 250 2.1.5 Recipient OK"
"SMTPC" 2028 160 "2018-04-26 14:02:03.289" "40.100.29.18" "SENT: DATA"
"SMTPC" 2036 160 "2018-04-26 14:02:03.367" "40.100.29.18" "RECEIVED: 354 Start mail input; end with <CRLF>.<CRLF>"
"SMTPC" 2036 160 "2018-04-26 14:02:03.367" "40.100.29.18" "SENT: [nl]."
"SMTPC" 2028 160 "2018-04-26 14:02:08.687" "40.100.29.18" "RECEIVED: 550 5.7.60 SMTP; Client does not have permissions to send as this sender [KU1PR02MB2423.apcprd02.prod.outlook.com]"
"SMTPC" 2028 160 "2018-04-26 14:02:08.734" "40.100.29.18" "SENT: QUIT"
"SMTPC" 1956 160 "2018-04-26 14:02:08.781" "40.100.29.18" "RECEIVED: 221 2.0.0 Service closing transmission channel"
"SMTPC" 2028 161 "2018-04-26 14:03:01.135" "40.100.29.194" "RECEIVED: 220 SG2PR06CA0094.outlook.office365.com Microsoft ESMTP MAIL Service ready at Thu, 26 Apr 2018 06:03:18 +0000"
"SMTPC" 2028 161 "2018-04-26 14:03:01.135" "40.100.29.194" "SENT: EHLO 2go-alert-dev.2go.com"
"SMTPC" 1996 161 "2018-04-26 14:03:01.244" "40.100.29.194" "RECEIVED: 250-SG2PR06CA0094.outlook.office365.com Hello [222.127.101.2][nl]250-SIZE 157286400[nl]250-PIPELINING[nl]250-DSN[nl]250-ENHANCEDSTATUSCODES[nl]250-STARTTLS[nl]250-8BITMIME[nl]250-BINARYMIME[nl]250-CHUNKING[nl]250 SMTPUTF8"
"SMTPC" 1996 161 "2018-04-26 14:03:01.244" "40.100.29.194" "SENT: STARTTLS"
"SMTPC" 2004 161 "2018-04-26 14:03:01.291" "40.100.29.194" "RECEIVED: 220 2.0.0 SMTP server ready"
"SMTPC" 1316 161 "2018-04-26 14:03:01.400" "40.100.29.194" "SENT: EHLO 2go-alert-dev.2go.com"
"SMTPC" 2004 161 "2018-04-26 14:03:01.447" "40.100.29.194" "RECEIVED: 250-SG2PR06CA0094.outlook.office365.com Hello [222.127.101.2][nl]250-SIZE 157286400[nl]250-PIPELINING[nl]250-DSN[nl]250-ENHANCEDSTATUSCODES[nl]250-AUTH LOGIN XOAUTH2[nl]250-8BITMIME[nl]250-BINARYMIME[nl]250-CHUNKING[nl]250 SMTPUTF8"
"SMTPC" 2004 161 "2018-04-26 14:03:01.447" "40.100.29.194" "SENT: AUTH LOGIN"
"SMTPC" 2020 161 "2018-04-26 14:03:01.494" "40.100.29.194" "RECEIVED: 334 VXNlcm5hbWU6"
"SMTPC" 2020 161 "2018-04-26 14:03:01.494" "40.100.29.194" "SENT: MmdvLm5vdGlmaWNhdGlvbi50ZXN0QDJnby5jb20ucGg="
"SMTPC" 1424 161 "2018-04-26 14:03:01.541" "40.100.29.194" "RECEIVED: 334 UGFzc3dvcmQ6"
"SMTPC" 1424 161 "2018-04-26 14:03:01.541" "40.100.29.194" "SENT: ***"
"SMTPC" 2004 161 "2018-04-26 14:03:02.477" "40.100.29.194" "RECEIVED: 235 2.7.0 Authentication successful target host KU1PR02MB2423.apcprd02.prod.outlook.com"
"SMTPC" 2004 161 "2018-04-26 14:03:02.477" "40.100.29.194" "SENT: ***"
"SMTPC" 2020 161 "2018-04-26 14:03:02.555" "40.100.29.194" "RECEIVED: 250 2.1.0 Sender OK"
"SMTPC" 2020 161 "2018-04-26 14:03:02.555" "40.100.29.194" "SENT: RCPT TO:<michael_erandio@2go.com.ph>"
"SMTPC" 1424 161 "2018-04-26 14:03:02.617" "40.100.29.194" "RECEIVED: 250 2.1.5 Recipient OK"
"SMTPC" 1424 161 "2018-04-26 14:03:02.617" "40.100.29.194" "SENT: DATA"
"SMTPC" 2004 161 "2018-04-26 14:03:02.664" "40.100.29.194" "RECEIVED: 354 Start mail input; end with <CRLF>.<CRLF>"
"SMTPC" 2004 161 "2018-04-26 14:03:02.664" "40.100.29.194" "SENT: [nl]."
"SMTPC" 1316 161 "2018-04-26 14:03:07.827" "40.100.29.194" "RECEIVED: 550 5.7.60 SMTP; Client does not have permissions to send as this sender [KU1PR02MB2423.apcprd02.prod.outlook.com]"
"SMTPC" 1316 161 "2018-04-26 14:03:07.827" "40.100.29.194" "SENT: QUIT"
"SMTPC" 1988 161 "2018-04-26 14:03:07.874" "40.100.29.194" "RECEIVED: 221 2.0.0 Service closing transmission channel"

User avatar
jimimaseye
Moderator
Moderator
Posts: 10053
Joined: 2011-09-08 17:48

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by jimimaseye » 2018-05-02 21:23

5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
mattg
Moderator
Moderator
Posts: 22435
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by mattg » 2018-05-03 05:07

jimimaseye wrote:
2018-05-02 21:23
All explained in here:

https://answers.microsoft.com/en-us/mso ... 505d233e6a
yep

Option 3 on this page I suspect will be the correct process >> https://support.office.com/en-us/articl ... n-US&ad=US

You need to get O365 to accept the mail from your hMailserver.
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

maykol1
New user
New user
Posts: 4
Joined: 2018-04-26 11:37

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by maykol1 » 2018-05-03 08:17

hi mattg,

I read the article of jimimaseye, one of the answer is fit to our requirements, I've test it and it works, I just made an adjustment to mailbox delegation the email notification email address should given a permission to the mailbox of the receiver, I've give Send as permission. For your suggestion the option 3 is to much complicated for me I've already read that article before I've consulted here at hmail forums. But I'm glad that you help, no I mean you helped me a LOT and thanks so much for that cheers!!! :D :D :D :D :D Now I've got a salary increase!! LOL! :D :D :D

Thanks,

Mike

--CLOSE THREAD--

User avatar
mattg
Moderator
Moderator
Posts: 22435
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by mattg » 2018-05-03 11:22

No worries

I think that jimimaseye and I will give ourselves a salary increase of double too...

Double nothing is ...nothing. :D
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

palinka
Senior user
Senior user
Posts: 4455
Joined: 2017-09-12 17:57

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by palinka » 2018-08-03 10:33

mattg wrote:
2018-05-03 11:22
No worries

I think that jimimaseye and I will give ourselves a salary increase of double too...

Double nothing is ...nothing. :D
In that case I'll let HR know it's OK to TRIPLE your salary! Good job, everybody! :mrgreen:

msandhu413
New user
New user
Posts: 6
Joined: 2018-08-22 01:07

Re: SCAN TO EMAIL USING O365 Cloud Email

Post by msandhu413 » 2018-08-22 21:48

maykol1 wrote:
2018-05-03 08:17
hi mattg,

I read the article of jimimaseye, one of the answer is fit to our requirements, I've test it and it works, I just made an adjustment to mailbox delegation the email notification email address should given a permission to the mailbox of the receiver, I've give Send as permission. For your suggestion the option 3 is to much complicated for me I've already read that article before I've consulted here at hmail forums. But I'm glad that you help, no I mean you helped me a LOT and thanks so much for that cheers!!! :D :D :D :D :D Now I've got a salary increase!! LOL! :D :D :D

Thanks,

Mike

--CLOSE THREAD--
Hello Mike.
We are having the same issue with sending email to office 365 accounts. I have made changes to mailbox delegation the email for permissions to the mailbox in office 365 but still same following messages but I don't think i did it right. Anyways, can you advise what specific steps you made to fix following message.
Thank you. Mac


“ RECEIVED: 550 5.7.60 SMTP; Client does not have permissions to send as this sender [BYAPR06MB4182.namprd06.prod.outlook.com]"


Here is diagnostics report: Test: Collect server details

hMailServer version: hMailServer 5.6.7-B2425
Database type: MSSQL Compact

Test: Test IPv6
IPv6 support is available in operating system.

Test: Test outbound port
SMTP relayer is in use.
Trying to connect to host smtp.office365.com...
Trying to connect to TCP/IP address 40.97.28.114 on port 587.
Received: 220 BN6PR03CA0015.outlook.office365.com Microsoft ESMTP MAIL Service ready at Tue, 21 Aug 2018 23:11:06 +0000.
Connected successfully.

Test: Test backup directory
ERROR: Backup directory has not been specified.

Test: Test MX records
Trying to resolve MX records for avaya.4c-alameda.org...
ERROR: MX records for domain avaya.4c-alameda.org could not be resolved

Test: Test local connect
Connecting to TCP/IP address in MX records for local domain domain avaya.4c-alameda.org...
ERROR: MX records for local domain avaya.4c-alameda.org could not be resolved

Test: Test message file locations
Relative message paths are stored in the database for all messages.

Test: Test IP range configuration
No problems were found in the IP range configuration.

Post Reply