SMTP-server

[zgti]

For scheduled reports we need an SMTP server without authentication.
Why is this still being needed? When working in the cloud, this is a major security issue!
Is there a way to change this? Or adapt this in the next version?

Hope someone can answer this.

Regards, Peter

[zakabog]

Just install an SMTP relay (like hMailServer) on a local Windows server and have that authenticate based on the IP.

[mnorst]

Just install an SMTP relay (like hMailServer) on a local Windows server and have that authenticate based on the IP.

This works well as a work-around, but I agree that needing a blind relay is not an optimal solution especially in an enterprise environment.

[jtarjanyi]

In exchange you can configure a host (ip address) to send mail without authentication, however I agree most of the time this not prefered due to security risk.
If you use hMailServer I think in server setting you can configure the bind address, and allowed host (server will accept SMTP from this IPs), and this will increase security.

[bucky101]

Still the case in 9.1.7?

Is this still the case? There are several auth based settings in
Administration > Email Configuration > Components > C3000SMTP Connector

Are they not utilized for the report scheduling?

[marquardt]

E-Mail in reporting via SMTP connector

The smtp sender for reporting mails works without authentication.

The SMTP connector is NOT used for sending reports per E-mail.

You can use the SMTP connector (and the appropriate settings for the relay host). But then you have to configure some settings.

1. Creale in the IPOCC a topic for E-mail, example reporting@ipoccserver
2. In the configuration set the reporting settings to the IPOCC Server.
SMTP Server ipoccserver
Domain: ipoccserver
3. Send the report to the internal E-Mail address, example reporting@ipoccserver
4. Create an external Destination ([email protected])
5. Create a taskflow for the topic. Connect to an external Destination.
6. The report will be send internal to the topic and then with the
faskflow to the external destination (via SMTP connector)