Papercut Query

[Michael]

Hi all,

 

I've configured some automated/scheduled reports in Papercut and when I run this manually it's OK, but in the example e-mail O365 reports "fraud detection" and possible spoofing which is great it's right to detect it's an automated e-mail, but how can I authorise/whitelist this?

 

It's simply configured as [email protected]

 

Any suggestions would be welcome

[howartp]

The Exchange equivalent of this would be to authorise the sending IP address as a legitimate sending server.

 

This is under Server Config > Hub Transport > Receive connectors in Exchange - can you see a similar option anywhere in O365?

 

Peter

[Michael]

But this server isn't public facing, it's just on the internal LAN.

[Steve21]

You can't do it the way you're talking. You'd either need to give it a valid account on your 365 domain, or do it via a relay that authorities it.

 

Steve

[tekins]

You can't do it the way you're talking. You'd either need to give it a valid account on your 365 domain, or do it via a relay that authorities it.

 

Steve

 

Agree, we have an account for "[email protected]", this is a cloud account on 365, works a treat for papercut and other services.

[robyholmes]

We had this problem for scan to email. We sent out mail out via a SMTP relay on the Smoothwall. I had to add the public IP of the Smoothie to the SPF record and create an account in O365 to match the one used in papercut. Once this was done we had no problem.

[Cache]

If it's just going internally, you could try a mail rule which sets the Spam Confidence Level to -1 (bypass) if it matches the senders address - we've done that with a couple of email addresses that come from web servers externally.

 

If it's coming from an internal service though I send everything via a Postfix SMTP relay which is authorised to send as those addresses.

Edited December 3, 2016 by Cache