Eclarsys Support Forum
Welcome, Guest. Please login or register.
February 06, 2012, 12:53:41 PM

Login with username, password and session length
Search:     Advanced search
Eclarsys PopGrabber Professional 1.0.7
Updated version with new features and bug fixes. Login to your Eclarsys account to download.
536 Posts in 119 Topics by 194 Members
Latest Member: Resselstrasse
* Home Help Search Login Register
+  Eclarsys Support Forum
|-+  General Category
| |-+  Eclarsys PopGrabber Support
| | |-+  A challenging PopGrabber Professional and Exchange problem. Giant kudos to anyo
« previous next »
Pages: [1] Print
Author Topic: A challenging PopGrabber Professional and Exchange problem. Giant kudos to anyo  (Read 1577 times)
thecymbrogi
Newbie
*
Posts: 4


« on: April 16, 2009, 10:05:26 AM »

Logged
Eclarsys Support
Administrator
Hero Member
*****
Posts: 244


« Reply #1 on: April 16, 2009, 12:14:08 PM »

You should setup you exchange server to use a smart host to send the outgoing emails.

Check the following Microsoft Knowledge Base article for information on how to configure an SMTP connector:

http://support.microsoft.com/kb/265293

You should set POP3.mydomain.com as your Smart Host in the SMTP connector, and set the connector to route all email (*) through this server. Normally you can use any account to authenticate regardless of the real address sending the message.

Is this what you wanted to do or do you have a different issue?

Regards,

Eclarsys Support
Logged
thecymbrogi
Newbie
*
Posts: 4


« Reply #2 on: April 16, 2009, 05:33:41 PM »

thanks for the asnwer, I had looked at that, but whatever acount logs onto POP3.mydomain.com is the account that sends out, regardless of the actual "FROM" in the SMTP connection Sad  I was hoping that there was some way to make POPGrabber or Exchange to it on a credential by credential basis....

Any other thoughts?

thanks--
Logged
Eclarsys Support
Administrator
Hero Member
*****
Posts: 244


« Reply #3 on: April 16, 2009, 11:17:22 PM »

The only other option we can think of, would be to ask your hosting company directly if they have a solution for this, our use a third party server for outgoing email.

Sometimes your ISP also provides a free outgoing SMTP server.
Logged
thecymbrogi
Newbie
*
Posts: 4


« Reply #4 on: April 17, 2009, 07:43:37 AM »

Sad great ideas, too, but have already worked with that.....  Alas!  It would be nice to have an SMTP server program that exchange could forward to that then takes the "from" and uses account information like that to forward it on.....  kind of like the POP3 grabber in reverse--a kind of SMTP sender.....  but I guess that wouldn't be a POPGrabber after all lol.....    Guess I am stuck in "hack" land.......  too bad, so sad Sad
Logged
Eclarsys Support
Administrator
Hero Member
*****
Posts: 244


« Reply #5 on: April 18, 2009, 12:46:24 AM »

You can try setting up an outgoing SMTP connector for each user, then configure the connector to be restricted only for the specific user:

Connector 1:
Address space: *
Restricted to User 1 (Reject everyone by default, Accept User 1)
Credentials for User1 on Smarthost.

Connector 2
Address space: *
Restricted to User 2 (Reject everyone by default, Accept User 2)
Credentials for User 2 on Smarthost.

This would make no sense if you have a lot of users, but for a few ones it could be the solution you are looking for.

Regards,

Eclarsys Support
Logged
Eclarsys Support
Administrator
Hero Member
*****
Posts: 244


« Reply #6 on: April 18, 2009, 05:41:48 AM »

Looking further into this problem, it seems this solution will not work correctly because Exchange will select a random SMTP connector and return a NDR if the user is not allowed to use the connector. You can try it though, and see what happens.

However, using a different SMTP server should not be a problem and is the recommended solution if you do not have a static IP for your Exchange server.

Regards,

Eclarsys Support
Logged
thecymbrogi
Newbie
*
Posts: 4


« Reply #7 on: April 20, 2009, 09:40:52 AM »

thanks for your help!  I'll continue to tweek and work around the issue until we can get the folks to make some changes and spend the correct $$$$ to fix it all.....
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!