• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

forward to exchange IP address for SMTP

R

richardtknight

Guest
Hi all, i run spam guardian on my server and it pretty much gets rid of 99% of my customers spam. I number of customers are moving to exchange servers ad having their mail sent direct to it, therefore they are now getting lots of spam as it isnt being cleaned by my server.

My question is there away other than them pooing the email to clean it via my server and then forward or push onto the exchange servers IP address for final delivery ?

most dont want to pop their email now they have in house exchanger severs, so being able to push mail to them would have a lot of value for us !

any ideas
richard
 
Hi all, i run spam guardian on my server and it pretty much gets rid of 99% of my customers spam. I number of customers are moving to exchange servers ad having their mail sent direct to it, therefore they are now getting lots of spam as it isnt being cleaned by my server.

My question is there away other than them pooing the email to clean it via my server and then forward or push onto the exchange servers IP address for final delivery ?

most dont want to pop their email now they have in house exchanger severs, so being able to push mail to them would have a lot of value for us !

any ideas
richard
I'm using postfix for that.
There is only one problem with such a setup - valid recipients. You have to synchronize them with exchange users.
After that it's just the matter of transport file -
go to /var/spool/postfix/plesk
edit with your favourite editor file transport:
===============
spamcleandomain.com smtp:[domainip][:eek:ptional port] // [if you write in brackets - there will be no dns lookup for more information read manual about transport file]
[email protected] virtual:
[email protected] virtual:
===============
That's my setup - I wanna mail delivery reports delivered to my mailbox, the rest is forwarded to exchange.

After editing run `postmap transport`
 
thanks for that, can you give me a little more help.

Does your solution work after the mail has been processed, as spam guardian cleans the email just before its delivered to the local mail box as i understand it.

so if you solution can work after that it would be perfect, also can it work across different domains and different exchange servers ?

I also dont understand what you meant about syncing with exchange users..

if your solution works after spam guardian and clean server as done its stuff then i'd be happy to pay for you to set it up for me

regards
richard
 
thanks for that, can you give me a little more help.

Does your solution work after the mail has been processed, as spam guardian cleans the email just before its delivered to the local mail box as i understand it.

so if you solution can work after that it would be perfect, also can it work across different domains and different exchange servers ?

I also dont understand what you meant about syncing with exchange users..

if your solution works after spam guardian and clean server as done its stuff then i'd be happy to pay for you to set it up for me

regards
richard
Well, it works like that. Just on final stage, when mail is processed and is about to delivered to local mailbox, it is instead transported to exchange server.
By syncing I mean that you have to know valid users (for which mail should be accepted and delivered). The most simple way to do it is to create a plesk mailbox when you're creating exchange one.
 
Back
Top