• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

how do I set qmail to be an selective relay ...

Server -> Mail -> Relaying

You can either choose 'Closed' or 'Authorization is required' (I use this with the SMTP method myself). In either case you're not running an open relay.
 
ok, I found that - forgot to mention - but exchange seems not to be able to send login-data while sending via smtp

so how could I set it for a special IP ?
 
The other option under Authorization is POP3, maybe you can use that? I don't use Exchange.

There's also the Whitelist tab on Server -> Mail.
 
I want to set our Plesk machine to be a Smart Host relay for our Exchange server too.

What was it that got it to work? POP3 or SMTP authorization? White List?

thanks.
 
on exchange you need to set up the pop3- (for every email-account on your plesk-server that should recieve emails over exchange from outside of your lan) and smtp-connectors (tell him that it should send over your plesk-server, not over dns)

then put your local-inet-ip in the whitelist of your plesk-server

for this to work you need a static IP at your local-inet-connection - it seem's that plesk does not accept any dyndns-entries or something like this.

I found no way to tell exchange that it should use the pop3-user/password for authorization while sending. therefore the emails are marked as from servername.yourlocaldomain.local - not from yourwebserver.tld
but thats no problem if you told exchange the real (plesk) email adress of each user
 
Back
Top