Outlook Email Issue

[Adao-Cruz, Miguel]

Hi,
 
I think that looking at the outlook logs will give you the answer.
But usually SAP people don't have access to it, that's why I didn't mention
it.
 
Cheers
 
___________________________________________________________________________
Miguel Adao-Cruz | Capgemini | London
Technology Services
SAP Application Architect

T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com
<file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft
\Signatures\www.capgemini.com> 

Join the Collaborative Business Experience
___________________________________________________________________________

________________________________

From: sap-wug-bounces at mit.edu on behalf of Lalitha Sankaran
Sent: Tue 25/07/2006 17:16
To: SAP Workflow Users' Group
Subject: Re: Outlook Email Issue


Hi Miguel,
 
Thank you,
The user receives this email from "Corp DES WFBatch"  The email ID is
corpwfbatch at company.com,
 
We checked with them to see they were'nt blocking any emails in outlook.
they told they did not have any rules setup for blocking.
but the problem is , they stopped receiving the emails suddenly,
they were receiving it before.
 
So not sure what else I could check,
can looking into the outlook log give any explaination ?
 
Thank you
Lalitha
 
 


 
On 7/25/06, Adao-Cruz, Miguel <miguel.adao-cruz at capgemini.com> wrote: 

	Check the technical details of both sent e-mails.
	Is it the same recipient e-mail?
	Is it the same sender e-mail? 
	
	Once I had the case when a user was manually converting a
requisition in a
	PO. The Po was then outputed to an e-mail address (Form). The system
by
	default, was putting the sender e-mail address of the user that
converted 
	the requisition. This user didn't have an e-mail address maintained
in SU01.
	In SOST, the sent e-mail was green, everything ok. But Outlook was
blocking
	it because the sender field (e-mail address) was empty.
	Besides, I suspect that if even the sender e-mail address is
populated with
	somethink like xxx.YYY at company.com, outlook might block it because
xxx.yyy
	is not in his database. It might depend on Oulook settings but
that's beyond 
	my knowledge.
	
	Hope it will help.
	
	
___________________________________________________________________________
	Miguel Adao-Cruz | Capgemini | London
	Technology Services
	SAP Application Architect
	
	T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com
<http://www.capgemini.com/> 
	
<file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Microsoft
<file:///,DanaInfo=owa+C:\Documents%20and%20Settings\madaocru\Application%20
Data\Microsoft> 
	\Signatures\www.capgemini.com>
	
	Join the Collaborative Business Experience
	
___________________________________________________________________________
	
	________________________________
	
	From: sap-wug-bounces at mit.edu on behalf of Lalitha Sankaran
	Sent: Tue 25/07/2006 15:53
	To: SAP Workflow Users' Group
	Subject: Outlook Email Issue
	
	
	Hi All,
	
	We are having some issues with our workflow emails. 
	
	The Email Log SOST shows that the email was sent to the Approver
	or the user successfully. But the users did not receive the email in
their
	Outlook inbox.
	
	They do receive other emails from other Workflows in the system. 
	
	Since SAP email log shows that the email is sent ,
	am not sure what else could be going wrong,
	
	Appreciate any input on this matter
	
	Thank you
	Lalitha
	
	
	_______________________________________________ 
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	
	
	


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 8220 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20060725/56b04a7b/attachment.bin
-------------- next part --------------
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.