Send As Public Folder in Outlook 2007 & Exchange 2003

I am trying to give a user/group permissions to send as a public folder while using Outlook 2007 & Exchange 2003.  I have granted them send as permission under the folder's directory rights in ESM.  I am in the Enterprise Admins group and I am able to send as by setting up a POP3 account (as I wish to do for these users).  When trying the same for the users I've been getting this send/receive error in Outlook: Task public_folder_email_address@domain.com - Sending reported error (0x800CCC0F): 'The connection to the server was interrupted.  If this problem continues....

I have setup the POP3 account exactly the same as I did on my account.
LVL 1
bmaitdepartmentAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SubsunCommented:
Are you able to send normal mails?
For troubleshooting refer
http://support.microsoft.com/kb/813514 
0
bmaitdepartmentAuthor Commented:
Yes, sending via the Exchange mail account is fine.
0
bmaitdepartmentAuthor Commented:
The only thing that can be different between my setup and the users is permissions.  The Outlook error given tells us nothing.  I've already exhausted the options on the kb page you posted.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

SubsunCommented:
Try configuring outlook Exchange/MAPI profile for user and check send as permission works or not.
0
SubsunCommented:
Also Pls tell us how you configured pop3 accounts to send the mail using PF email address as from address? Is it configured as two separate accounts? and send the mail by selecting the form?
0
MesthaCommented:
If you are using POP3/SMTP to send email, then Send As permissions has nothing to do with it. Send As only permissions are only required when you are using a MAPI client and the from field.

Therefore you need to be clear about how you are connecting. If you are using POP3/SMTP then the only thing you have to worry about is that the sending authentication in SMTP is correct.

Simon.
0
SubsunCommented:
In this case both account settings should be exactly same except the email address.
0
bmaitdepartmentAuthor Commented:
I am only sending from this address since all receives will go to the public folder.  We are using SMTP and I do not require authentication.  Now that you've established that permissions are not required then, we've tested this also with a few users and also a new test user- they have been able to send with no problem.  However, we still have these few clients getting the aforementioned error.  The error we are getting on these few clients pops up immediately after the send/receive.
0
SubsunCommented:
Try by creating a dummy pop account and see if it helps..
http://www.block.net.au/help/Dummy-POP3/
0
bmaitdepartmentAuthor Commented:
This is exactly what I am already doing.  Users have an MS Exchange mailbox which is the default- works fine.  We are setting up this public folder's address as a "secondary" "dummy" pop/smtp account and allowing only send.
0
MesthaCommented:
The error has to be caused by something other than the permissions on the folder - because the permissions on the folder mean nothing when you are sending via SMTP. All Exchange is looking at is the authentication credentials being used to send the email message.

Therefore that is where I would be looking - at the credentials set in the SMTP outbound email settings.

Simon.
0
SubsunCommented:
You mean to say there is no real POP account configured on this profile only dummy POP account?
0
bmaitdepartmentAuthor Commented:
Subsun, Only exchange & this dummy POP account.  Mestha, authentication is not necessary for outbound email.  I added an alias to the exchange account and set that up the same way and  I get the same error.  I'm thinking it's something more than the settings in Outlook.
0
SubsunCommented:
Can you check the authentication setting SMTP in dummy pop account and see if it works..
smtp.JPG
0
bmaitdepartmentAuthor Commented:
this works, but is not necessary because on the other users' setups I leave this unchecked and it works fine.
0
MesthaCommented:
The setup shown above is how it should work - with specific authentication credentials used for sending email to EXTERNAL recipients.
For INTERNAL recipients no authentication is required.

If you are routing email out through Exchange then you need to either authenticate or have the IP address of the machine sending the email listed as an address that can relay. Exchange does not work in the way that many ISPs servers do and allow email to be routed through their servers from their own network.

Therefore if you have other machines working without specific credentials being set then either
a. You have those machines listed as being able to relay.
b. You have an open relay
c. You are not using Exchange as the outbound SMTP Server.

It is simply not possible otherwise.

Simon.
0
SubsunCommented:
If you are logged in to your domain then this setting is not required, If you are logged in to some other domain or local system then it is required.
0
bmaitdepartmentAuthor Commented:
OK, you got me on this part.  If I'm sending to INTERNAL, then I don't need it.  Which right now to test this is what I am doing.  However, that's not my issue here.  For some reason, users at this one branch office are having issues.
0
bmaitdepartmentAuthor Commented:
I setup my email on a workstation at the branch office and I get the same error, where everything works fine for me at HQ.
0
MesthaCommented:
Looking at the original question - the error points to interference.
Firewall is the most likely cause, scanning port 25. AV software can do the same thing - McAfee for example blocks port 25 by default.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SubsunCommented:
I agree with Simon..

Are you able to telnet the server from workstation?
http://support.microsoft.com/kb/153119
You may check the MS KB from my first post to troubleshoot..
0
bmaitdepartmentAuthor Commented:
Never really got to the bottom of this, although we did isolate the issue at the branch location.  The business requirement changed, so this is no longer necessary.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.