Email addresses look odd with @name

system · January 24, 2014, 9:12am

This is how I fixed ours.

Our Vantage server is Windows Server 2008 R2 Enterprise where I installed the SMTP service. Using the IIS Manager, I set SMTP E-mail to "Deliver e-mail to SMTP server" and for the e-mail server I put the ip address of my exchange server. I also used the Administrator credentials under the authentication settings.

On the Exchange server, under Server Configuration / Hub Transport, I set up a new receive connector called "Anonymous Relay". Under the property settings of the connector I set the authentication to "Transport Layer Security" and "Externally Secured". The permission Groups are "Anonymous users" and "Exchange servers". Under network I added the internal ip addresses of those servers that need to relay through the SMPT service on my Vantage Server. I removed all other ip addresses.

Finally, in the company configuration in Vantage, I set the SMPT server address for email to the IP address of the Vantage server since it was the one that had the SMPT service set up for relaying.

Now, as long as I enclose the email address in <>, the email address on the receiving end looks normal.

Steven G.

On Friday, January 24, 2014 6:38 AM, brenda mohr <brenda@...> wrote:

<div id="ygrps-yiv-1252784418yiv0753183046ygrp-text">
  
  
  <div>

I have tried every solution offered (this thread & others) and all my research still comes up with it being a setting on email server. Not that I have managed to find and fix it yet.

Brenda

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of livingstonmh@...
Sent: Thursday, January 23, 2014 7:50 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Email addresses look odd with @name

So I have been dealing with this same issue. I have tried encasing the TO email in the <> but this will not even send the email. Does anyone know of any other solution?

How do you set up the smtp forwarding that was mentioned?

</div>
 


<div style="color:#fff;height:0;"></div></div>

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046 -- #ygrps-yiv-1252784418yiv0753183046ygrp-mkp { border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp #ygrps-yiv-1252784418yiv0753183046hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp #ygrps-yiv-1252784418yiv0753183046ads {
margin-bottom:10px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp .ygrps-yiv-1252784418yiv0753183046ad {
padding:0 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp .ygrps-yiv-1252784418yiv0753183046ad p {
margin:0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mkp .ygrps-yiv-1252784418yiv0753183046ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ygrp-lc {
font-family:Arial;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ygrp-lc #ygrps-yiv-1252784418yiv0753183046hd {
margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ygrp-lc .ygrps-yiv-1252784418yiv0753183046ad {
margin-bottom:10px;padding:0 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity span {
font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity span:first-child {
text-transform:uppercase;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity span a {
color:#5085b6;text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity span span {
color:#ff7900;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046activity span .ygrps-yiv-1252784418yiv0753183046underline {
text-decoration:underline;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046attach div a {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046attach img {
border:none;padding-right:5px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046attach label {
display:block;margin-bottom:5px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046attach label a {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 blockquote {
margin:0 0 0 4px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046bold {
font-family:Arial;font-size:13px;font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046bold a {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 dd.ygrps-yiv-1252784418yiv0753183046last p a {
font-family:Verdana;font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 dd.ygrps-yiv-1252784418yiv0753183046last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 dd.ygrps-yiv-1252784418yiv0753183046last p span.ygrps-yiv-1252784418yiv0753183046yshortcuts {
margin-right:0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046attach-table div div a {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046attach-table {
width:400px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046file-title a, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046file-title a:active, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046file-title a:hover, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046file-title a:visited {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046photo-title a, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046photo-title a:active, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046photo-title a:hover, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div.ygrps-yiv-1252784418yiv0753183046photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 div#ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg #ygrps-yiv-1252784418yiv0753183046ygrp-msg p a span.ygrps-yiv-1252784418yiv0753183046yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046green {
color:#628c2a;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046MsoNormal {
margin:0 0 0 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 o {
font-size:0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046photos div {
float:left;width:72px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046photos div div {
border:1px solid #666666;height:62px;overflow:hidden;width:62px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046reco-category {
font-size:77%;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046reco-desc {
font-size:77%;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 .ygrps-yiv-1252784418yiv0753183046replbq {
margin:4px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg table {
font-size:inherit;font:100%;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg select, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 input, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg pre, #ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 code {
font:115% monospace;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg * {
line-height:1.22em;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-mlmsg #ygrps-yiv-1252784418yiv0753183046logo {
padding-bottom:10px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-msg p a {
font-family:Verdana;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-msg p#ygrps-yiv-1252784418yiv0753183046attach-count span {
color:#1E66AE;font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-reco #ygrps-yiv-1252784418yiv0753183046reco-head {
color:#ff7900;font-weight:700;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-reco {
margin-bottom:20px;padding:0px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ov li a {
font-size:130%;text-decoration:none;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ov li {
font-size:77%;list-style-type:square;padding:6px 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-sponsor #ygrps-yiv-1252784418yiv0753183046ov ul {
margin:0;padding:0 0 0 8px;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-text {
font-family:Georgia;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-text p {
margin:0 0 1em 0;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-text tt {
font-size:120%;}

#ygrps-yiv-1252784418 #ygrps-yiv-1252784418yiv0753183046 #ygrps-yiv-1252784418yiv0753183046ygrp-vital ul li:last-child {
border-right:none !important;}
#ygrps-yiv-1252784418

system · August 24, 2012, 10:15pm

yes, we do and sorry for not changing the subject line.

I see it already converted in the smtp log though. I put in a call to support.

08/24/12 17:18:54 SendCommand: From: Epicor Info <info@...>

To: mese@... <mese@...>

CC: info@... <info@...>

Greg

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Steven Gotschall
Sent: Friday, August 24, 2012 4:27 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry

I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.

Steven G.

________________________________
From: Greg Payne <gpayne@...<mailto:gpayne%40compulink-usa.com>>
To: "vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>" <vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>>
Sent: Friday, August 24, 2012 3:35 PM
Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry

Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?

I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info

Thanks

Greg

________________________________
CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

________________________________
CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."

[Non-text portions of this message have been removed]

system · August 27, 2012, 8:43am

If you don't mind, please let us know what they say.

________________________________
From: Greg Payne <gpayne@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Friday, August 24, 2012 10:15 PM
Subject: [Vantage] Email addresses look odd with @name

Â
yes, we do and sorry for not changing the subject line.

I see it already converted in the smtp log though. I put in a call to support.

08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>

To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>

CC: mailto:info%40compulink.com <mailto:info%40compulink.com>

Greg

From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
Sent: Friday, August 24, 2012 4:27 PM
To: mailto:vantage%40yahoogroups.com
Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry

I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.

Steven G.

________________________________
From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
Sent: Friday, August 24, 2012 3:35 PM
Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry

Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?

I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info

Thanks

Greg

________________________________
CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

________________________________
CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

system · October 18, 2012, 7:08am

Hi All,
We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@...>
It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
For BAM or Global Alerts:
<User@...>;
<User2@...>;

For coded BPM email: '<User@...>'

We put this in place and all is well. I hope this helps someone out there.
Have a great day.
Helen
Saugus MA

--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> If you don't mind, please let us know what they say.
>
>
>
> ________________________________
> From: Greg Payne <gpayne@...>
> To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
> Sent: Friday, August 24, 2012 10:15 PM
> Subject: [Vantage] Email addresses look odd with @name
>
>
> Ã‚Â
> yes, we do and sorry for not changing the subject line.
>
> I see it already converted in the smtp log though. I put in a call to support.
>
> 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
>
> To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
>
> CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
>
> Greg
>
> From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> Sent: Friday, August 24, 2012 4:27 PM
> To: mailto:vantage%40yahoogroups.com
> Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
>
>
>
> I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
>
> Steven G.
>
> ________________________________
> From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> Sent: Friday, August 24, 2012 3:35 PM
> Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
>
>
> Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
>
> I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
>
> Thanks
>
> Greg
>
> ________________________________
> CONFIDENTIALITY NOTICE
>
> The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
>
> "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
>
> [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
> ________________________________
> CONFIDENTIALITY NOTICE
>
> The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
>
> "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
>
> [Non-text portions of this message have been removed]
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · October 18, 2012, 7:27am

I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
'<Fullemailaddress>'
Sorry about that.
Helen

--- In vantage@yahoogroups.com, "hellybell12" <hellybell12@...> wrote:
>>
> Hi All,
> We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@...>
> It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> For BAM or Global Alerts:
> <User@...>;
> <User2@...>;
>
> For coded BPM email: '<User@...>'
>
> We put this in place and all is well. I hope this helps someone out there.
> Have a great day.
> Helen
> Saugus MA
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> >
> > If you don't mind, please let us know what they say.
> >
> >
> >
> > ________________________________
> > From: Greg Payne <gpayne@>
> > To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
> > Sent: Friday, August 24, 2012 10:15 PM
> > Subject: [Vantage] Email addresses look odd with @name
> >
> >
> > Ã‚Â
> > yes, we do and sorry for not changing the subject line.
> >
> > I see it already converted in the smtp log though. I put in a call to support.
> >
> > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> >
> > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> >
> > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> >
> > Greg
> >
> > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > Sent: Friday, August 24, 2012 4:27 PM
> > To: mailto:vantage%40yahoogroups.com
> > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> >
> >
> >
> > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> >
> > Steven G.
> >
> > ________________________________
> > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > Sent: Friday, August 24, 2012 3:35 PM
> > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> >
> >
> > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> >
> > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> >
> > Thanks
> >
> > Greg
> >
> > ________________________________
> > CONFIDENTIALITY NOTICE
> >
> > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> >
> > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> >
> > [Non-text portions of this message have been removed]
> >
> > [Non-text portions of this message have been removed]
> >
> >
> > ________________________________
> > CONFIDENTIALITY NOTICE
> >
> > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> >
> > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

system · October 18, 2012, 9:30am

We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?

________________________________
From: hellybell12 <hellybell12@...>
To: vantage@yahoogroups.com
Sent: Thursday, October 18, 2012 7:27 AM
Subject: [Vantage] Re: Email addresses look odd with @name

Â

I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
'<Fullemailaddress>'
Sorry about that.
Helen

--- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@...> wrote:
>>
> Hi All,
> We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@...>
> It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> For BAM or Global Alerts:
> <User@...>;
> <User2@...>;
>
> For coded BPM email: '<User@...>'
>
> We put this in place and all is well. I hope this helps someone out there.
> Have a great day.
> Helen
> Saugus MA
>
> --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> >
> > If you don't mind, please let us know what they say.
> >
> >
> >
> > ________________________________
> > From: Greg Payne <gpayne@>
> > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > Sent: Friday, August 24, 2012 10:15 PM
> > Subject: [Vantage] Email addresses look odd with @name
> >
> >
> > Ã‚Â
> > yes, we do and sorry for not changing the subject line.
> >
> > I see it already converted in the smtp log though. I put in a call to support.
> >
> > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> >
> > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> >
> > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> >
> > Greg
> >
> > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > Sent: Friday, August 24, 2012 4:27 PM
> > To: mailto:vantage%40yahoogroups.com
> > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> >
> >
> >
> > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> >
> > Steven G.
> >
> > ________________________________
> > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > Sent: Friday, August 24, 2012 3:35 PM
> > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> >
> >
> > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> >
> > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> >
> > Thanks
> >
> > Greg
> >
> > ________________________________
> > CONFIDENTIALITY NOTICE
> >
> > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> >
> > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> >
> > [Non-text portions of this message have been removed]
> >
> > [Non-text portions of this message have been removed]
> >
> >
> > ________________________________
> > CONFIDENTIALITY NOTICE
> >
> > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> >
> > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

[Non-text portions of this message have been removed]

system · October 18, 2012, 10:40am

Are you using the greater than and less than and then full email address? In the BAM List:
<emailaddress1>;
<emailaddress2>;
<emailaddress3>;

In the Bpm hard coded I put the <emailaddress> in quotes
'<emailaddress'
Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.

Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.

--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
>
>
>
>
> ________________________________
> From: hellybell12 <hellybell12@...>
> To: vantage@yahoogroups.com
> Sent: Thursday, October 18, 2012 7:27 AM
> Subject: [Vantage] Re: Email addresses look odd with @name
>
> Ã‚Â
>
> I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> '<Fullemailaddress>'
> Sorry about that.
> Helen
>
> --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> >>
> > Hi All,
> > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > For BAM or Global Alerts:
> > <User@>;
> > <User2@>;
> >
> > For coded BPM email: '<User@>'
> >
> > We put this in place and all is well. I hope this helps someone out there.
> > Have a great day.
> > Helen
> > Saugus MA
> >
> > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > >
> > > If you don't mind, please let us know what they say.
> > >
> > >
> > >
> > > ________________________________
> > > From: Greg Payne <gpayne@>
> > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > Sent: Friday, August 24, 2012 10:15 PM
> > > Subject: [Vantage] Email addresses look odd with @name
> > >
> > >
> > > ÃƒÂ‚Ã‚Â
> > > yes, we do and sorry for not changing the subject line.
> > >
> > > I see it already converted in the smtp log though. I put in a call to support.
> > >
> > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > >
> > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > >
> > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > >
> > > Greg
> > >
> > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > Sent: Friday, August 24, 2012 4:27 PM
> > > To: mailto:vantage%40yahoogroups.com
> > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > >
> > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > >
> > > Steven G.
> > >
> > > ________________________________
> > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > Sent: Friday, August 24, 2012 3:35 PM
> > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > >
> > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > >
> > > Thanks
> > >
> > > Greg
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · October 18, 2012, 10:45am

When posting on yahoo, yahoo masks a portion of email addresses so that if someone forwards the text email addresses are not included.

Jim Kinneman
Encompass Solutions, Inc

--- In vantage@yahoogroups.com, "hellybell12" <hellybell12@...> wrote:
>
>
> I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> '<Fullemailaddress>'
> Sorry about that.
> Helen
>
> --- In vantage@yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> >>
> > Hi All,
> > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > For BAM or Global Alerts:
> > <User@>;
> > <User2@>;
> >
> > For coded BPM email: '<User@>'
> >
> > We put this in place and all is well. I hope this helps someone out there.
> > Have a great day.
> > Helen
> > Saugus MA
> >
> > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > >
> > > If you don't mind, please let us know what they say.
> > >
> > >
> > >
> > > ________________________________
> > > From: Greg Payne <gpayne@>
> > > To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
> > > Sent: Friday, August 24, 2012 10:15 PM
> > > Subject: [Vantage] Email addresses look odd with @name
> > >
> > >
> > > Ã‚Â
> > > yes, we do and sorry for not changing the subject line.
> > >
> > > I see it already converted in the smtp log though. I put in a call to support.
> > >
> > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > >
> > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > >
> > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > >
> > > Greg
> > >
> > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > Sent: Friday, August 24, 2012 4:27 PM
> > > To: mailto:vantage%40yahoogroups.com
> > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > >
> > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > >
> > > Steven G.
> > >
> > > ________________________________
> > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > Sent: Friday, August 24, 2012 3:35 PM
> > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > >
> > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > >
> > > Thanks
> > >
> > > Greg
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>

system · October 18, 2012, 11:20am

I'll play with it some more and see if I can get it to work.

________________________________
From: hellybell12 <hellybell12@...>
To: vantage@yahoogroups.com
Sent: Thursday, October 18, 2012 10:40 AM
Subject: [Vantage] Re: Email addresses look odd with @name

Â

Are you using the greater than and less than and then full email address? In the BAM List:
<emailaddress1>;
<emailaddress2>;
<emailaddress3>;

In the Bpm hard coded I put the <emailaddress> in quotes
'<emailaddress'
Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.

Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.

--- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
>
>
>
>
> ________________________________
> From: hellybell12 <hellybell12@...>
> To: mailto:vantage%40yahoogroups.com
> Sent: Thursday, October 18, 2012 7:27 AM
> Subject: [Vantage] Re: Email addresses look odd with @name
>
> Ã‚Â
>
> I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> '<Fullemailaddress>'
> Sorry about that.
> Helen
>
> --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> >>
> > Hi All,
> > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > For BAM or Global Alerts:
> > <User@>;
> > <User2@>;
> >
> > For coded BPM email: '<User@>'
> >
> > We put this in place and all is well. I hope this helps someone out there.
> > Have a great day.
> > Helen
> > Saugus MA
> >
> > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > >
> > > If you don't mind, please let us know what they say.
> > >
> > >
> > >
> > > ________________________________
> > > From: Greg Payne <gpayne@>
> > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > Sent: Friday, August 24, 2012 10:15 PM
> > > Subject: [Vantage] Email addresses look odd with @name
> > >
> > >
> > > Ãƒâ€šÃ‚Â
> > > yes, we do and sorry for not changing the subject line.
> > >
> > > I see it already converted in the smtp log though. I put in a call to support.
> > >
> > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > >
> > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > >
> > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > >
> > > Greg
> > >
> > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > Sent: Friday, August 24, 2012 4:27 PM
> > > To: mailto:vantage%40yahoogroups.com
> > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > >
> > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > >
> > > Steven G.
> > >
> > > ________________________________
> > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > Sent: Friday, August 24, 2012 3:35 PM
> > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > >
> > >
> > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > >
> > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > >
> > > Thanks
> > >
> > > Greg
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > > ________________________________
> > > CONFIDENTIALITY NOTICE
> > >
> > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > >
> > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · October 18, 2012, 11:28am

When I enclose the email addresses in <> they format correctly, but when I use "Reply All" the only address that shows up in the reply is the "From" email address.

--- In vantage@yahoogroups.com, "hellybell12" <hellybell12@...> wrote:
>
>
>
>
> Are you using the greater than and less than and then full email address? In the BAM List:
> <emailaddress1>;
> <emailaddress2>;
> <emailaddress3>;
>
> In the Bpm hard coded I put the <emailaddress> in quotes
> '<emailaddress'
> Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.
>
> Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.
>
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> >
> > We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
> >
> >
> >
> >
> > ________________________________
> > From: hellybell12 <hellybell12@>
> > To: vantage@yahoogroups.com
> > Sent: Thursday, October 18, 2012 7:27 AM
> > Subject: [Vantage] Re: Email addresses look odd with @name
> >
> > Ã‚Â
> >
> > I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> > '<Fullemailaddress>'
> > Sorry about that.
> > Helen
> >
> > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > >>
> > > Hi All,
> > > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > > For BAM or Global Alerts:
> > > <User@>;
> > > <User2@>;
> > >
> > > For coded BPM email: '<User@>'
> > >
> > > We put this in place and all is well. I hope this helps someone out there.
> > > Have a great day.
> > > Helen
> > > Saugus MA
> > >
> > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > >
> > > > If you don't mind, please let us know what they say.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: Greg Payne <gpayne@>
> > > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > Subject: [Vantage] Email addresses look odd with @name
> > > >
> > > >
> > > > ÃƒÂ‚Ã‚Â
> > > > yes, we do and sorry for not changing the subject line.
> > > >
> > > > I see it already converted in the smtp log though. I put in a call to support.
> > > >
> > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > > >
> > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > > >
> > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > >
> > > > Greg
> > > >
> > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > To: mailto:vantage%40yahoogroups.com
> > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > >
> > > >
> > > >
> > > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > > >
> > > > Steven G.
> > > >
> > > > ________________________________
> > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > >
> > > >
> > > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > > >
> > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > > >
> > > > Thanks
> > > >
> > > > Greg
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

system · October 18, 2012, 11:37am

Are you saying when you get the email, you can now see the email addresses formated correctly but when you 'reply all' it only replys to the from? How many email addresses are you sending the alert to?
If I try to reply all and I'm the only one on the list, the only field that will populate is the From. try a few emails on one alert?

--- In vantage@yahoogroups.com, "jdt_agm" <dtsosie@...> wrote:
>
>
> When I enclose the email addresses in <> they format correctly, but when I use "Reply All" the only address that shows up in the reply is the "From" email address.
>
> --- In vantage@yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> >
> >
> >
> >
> > Are you using the greater than and less than and then full email address? In the BAM List:
> > <emailaddress1>;
> > <emailaddress2>;
> > <emailaddress3>;
> >
> > In the Bpm hard coded I put the <emailaddress> in quotes
> > '<emailaddress'
> > Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.
> >
> > Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.
> >
> >
> > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > >
> > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: hellybell12 <hellybell12@>
> > > To: vantage@yahoogroups.com
> > > Sent: Thursday, October 18, 2012 7:27 AM
> > > Subject: [Vantage] Re: Email addresses look odd with @name
> > >
> > > Ã‚Â
> > >
> > > I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> > > '<Fullemailaddress>'
> > > Sorry about that.
> > > Helen
> > >
> > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > > >>
> > > > Hi All,
> > > > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > > > For BAM or Global Alerts:
> > > > <User@>;
> > > > <User2@>;
> > > >
> > > > For coded BPM email: '<User@>'
> > > >
> > > > We put this in place and all is well. I hope this helps someone out there.
> > > > Have a great day.
> > > > Helen
> > > > Saugus MA
> > > >
> > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > > >
> > > > > If you don't mind, please let us know what they say.
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: Greg Payne <gpayne@>
> > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > >
> > > > >
> > > > > ÃƒÂ‚Ã‚Â
> > > > > yes, we do and sorry for not changing the subject line.
> > > > >
> > > > > I see it already converted in the smtp log though. I put in a call to support.
> > > > >
> > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > > > >
> > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > > > >
> > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > >
> > > > > Greg
> > > > >
> > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > To: mailto:vantage%40yahoogroups.com
> > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > >
> > > > >
> > > > >
> > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > > > >
> > > > > Steven G.
> > > > >
> > > > > ________________________________
> > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > >
> > > > >
> > > > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > > > >
> > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > > > >
> > > > > Thanks
> > > > >
> > > > > Greg
> > > > >
> > > > > ________________________________
> > > > > CONFIDENTIALITY NOTICE
> > > > >
> > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > >
> > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > >
> > > > > ________________________________
> > > > > CONFIDENTIALITY NOTICE
> > > > >
> > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > >
> > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>

system · October 18, 2012, 1:41pm

D'oh! You're right. I've been testing with just sending an email to myself. Once I included someone else it works as expected.

Thanks for the info.

--- In vantage@yahoogroups.com, "hellybell12" <hellybell12@...> wrote:
>
> Are you saying when you get the email, you can now see the email addresses formatted correctly but when you 'reply all' it only replys to the from? How many email addresses are you sending the alert to?
> If I try to reply all and I'm the only one on the list, the only field that will populate is the From. try a few emails on one alert?
>
> --- In vantage@yahoogroups.com, "jdt_agm" <dtsosie@> wrote:
> >
> >
> > When I enclose the email addresses in <> they format correctly, but when I use "Reply All" the only address that shows up in the reply is the "From" email address.
> >
> > --- In vantage@yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > >
> > >
> > >
> > >
> > > Are you using the greater than and less than and then full email address? In the BAM List:
> > > <emailaddress1>;
> > > <emailaddress2>;
> > > <emailaddress3>;
> > >
> > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > '<emailaddress'
> > > Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.
> > >
> > > Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.
> > >
> > >
> > > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > >
> > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: hellybell12 <hellybell12@>
> > > > To: vantage@yahoogroups.com
> > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > >
> > > > Ã‚Â
> > > >
> > > > I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> > > > '<Fullemailaddress>'
> > > > Sorry about that.
> > > > Helen
> > > >
> > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > > > >>
> > > > > Hi All,
> > > > > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > > > > For BAM or Global Alerts:
> > > > > <User@>;
> > > > > <User2@>;
> > > > >
> > > > > For coded BPM email: '<User@>'
> > > > >
> > > > > We put this in place and all is well. I hope this helps someone out there.
> > > > > Have a great day.
> > > > > Helen
> > > > > Saugus MA
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > > > >
> > > > > > If you don't mind, please let us know what they say.
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <gpayne@>
> > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > >
> > > > > >
> > > > > > ÃƒÂ‚Ã‚Â
> > > > > > yes, we do and sorry for not changing the subject line.
> > > > > >
> > > > > > I see it already converted in the smtp log though. I put in a call to support.
> > > > > >
> > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > > > > >
> > > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > > > > >
> > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > > >
> > > > > >
> > > > > >
> > > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > > > > >
> > > > > > Steven G.
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > > >
> > > > > >
> > > > > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > > > > >
> > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>

system · October 18, 2012, 2:47pm

Awesome!! Glad it worked for you.

--- In vantage@yahoogroups.com, "jdt_agm" <dtsosie@...> wrote:
>
>
> D'oh! You're right. I've been testing with just sending an email to myself. Once I included someone else it works as expected.
>
> Thanks for the info.
>
> --- In vantage@yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> >
> > Are you saying when you get the email, you can now see the email addresses formatted correctly but when you 'reply all' it only replys to the from? How many email addresses are you sending the alert to?
> > If I try to reply all and I'm the only one on the list, the only field that will populate is the From. try a few emails on one alert?
> >
> > --- In vantage@yahoogroups.com, "jdt_agm" <dtsosie@> wrote:
> > >
> > >
> > > When I enclose the email addresses in <> they format correctly, but when I use "Reply All" the only address that shows up in the reply is the "From" email address.
> > >
> > > --- In vantage@yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Are you using the greater than and less than and then full email address? In the BAM List:
> > > > <emailaddress1>;
> > > > <emailaddress2>;
> > > > <emailaddress3>;
> > > >
> > > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > > '<emailaddress'
> > > > Strange its not working for you. we still have a mix, some people are still on Exchange 2003 and some have been moved to 2010 and this email format is working for both.
> > > >
> > > > Maybe because of the vantage version you are on. Heres what I did to troubleshoot this. Look at one of the emails that are not formatted correctly, Look at the header. When I looked at one of ours, I could see that exchange 2010 was putting <> around what it thought was the email address. So I thought since exchange can't figure out where to put < > I will send it the way exchange is trying to format it. This was a problem for us for a long time, it is working great now. I hope this helps.
> > > >
> > > >
> > > > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > > >
> > > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address returned from the Exchange server.Ã‚Â Could you please provide a couple of examples so I can see if there is something I am doing wrong?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: hellybell12 <hellybell12@>
> > > > > To: vantage@yahoogroups.com
> > > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > > >
> > > > > Ã‚Â
> > > > >
> > > > > I just looked at my reply and see that my email address formating has been truncated. It should be: <Fullemailaddress> for BAM and
> > > > > '<Fullemailaddress>'
> > > > > Sorry about that.
> > > > > Helen
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@> wrote:
> > > > > >>
> > > > > > Hi All,
> > > > > > We are on E9 and email was fine with Exchange 2003, when we moved to Exchange 2010 emails will reach it's destination but you cannot reply all. Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > > It does this to the entire email list. I found a solution that is working for us. You have to format the email address as follows:
> > > > > > For BAM or Global Alerts:
> > > > > > <User@>;
> > > > > > <User2@>;
> > > > > >
> > > > > > For coded BPM email: '<User@>'
> > > > > >
> > > > > > We put this in place and all is well. I hope this helps someone out there.
> > > > > > Have a great day.
> > > > > > Helen
> > > > > > Saugus MA
> > > > > >
> > > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > > > > >
> > > > > > > If you don't mind, please let us know what they say.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <gpayne@>
> > > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:vantage%40yahoogroups.com>
> > > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > > >
> > > > > > >
> > > > > > > ÃƒÂ‚Ã‚Â
> > > > > > > yes, we do and sorry for not changing the subject line.
> > > > > > >
> > > > > > > I see it already converted in the smtp log though. I put in a call to support.
> > > > > > >
> > > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:info%40compulink-usa.com>
> > > > > > >
> > > > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com>
> > > > > > >
> > > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but somwhere during an update it started to do what yours is doing and no one could ever figure out why. No other applications have this problem with our email server, only Vantage.
> > > > > > >
> > > > > > > Steven G.
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:gpayne%40compulink-usa.com>>
> > > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:vantage%40yahoogroups.com>>
> > > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > > Is there a way with a BAM or global alert to format the email address so it is an address that can be replied to?
> > > > > > >
> > > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto:mailto:info%40compulink-usa.com>>) when the field just has the email address in it. and it shows as @info
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at (727) 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> >
>

system · May 30, 2013, 1:05pm

I tried this solution when emailing from BPM but i get a error that the
email is not valid
When i send it without the '<>' it send the email but the addresses show up
as 'user@'

here is the code i use

REPEAT:
/*create some email related variables*/
define variable vFrom as character no-undo initial '':U.
define variable vTo as character no-undo initial '':U.
define variable vCC as character no-undo initial '':U.
define variable vSubject as character no-undo initial
'':U.
define variable vBody as character no-undo initial '':U.
define variable CurrentUser AS CHARACTER NO-UNDO
initial '':U.
define variable EntryUser AS CHARACTER NO-UNDO initial
'':U.
define variable hEmailEx as handle no-undo.

run Bpm/BpmEmail.p persistent set hEmailEx.
/*I honestly can't remember why these integer cnt
variables are in here.*/
define variable from_cnt as integer no-undo.
FIND FIRST UserFile WHERE UserFile.dcduserid =
ttCallContextClient.CurrentUserId.
IF AVAIL UserFile THEN
DO:
assign vFrom = UserFile.EMailAddress.
assign CurrentUser = Userfile.Name.
END.

define variable to_cnt as integer no-undo.
FIND FIRST UserFile WHERE UserFile.dcduserid =
ttOrderHed.EntryPerson.
IF AVAIL UserFile THEN
DO:
assign vTo = '<' + UserFile.EMailAddress +
'>'.
assign EntryUser = Userfile.Name.
END.

define variable cc_cnt as integer no-undo.
FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
EmpBasic.EMailAddress <> '' No-Lock.
ASSIGN vCC = vCC + EmpBasic.EMailAddress +
';'.
END.

define variable subject_cnt as integer no-undo.
assign vSubject = 'Notification : Order #: ' +
STRING(OrderNum) + ' - has been scheduled'.

define variable body_cnt as integer no-undo.
assign vBody = "Order has been scheduled by " +
CurrentUser + ":" + CHR(10) + CHR(10)
+ "Customer: " + custName + CHR(10)
+ "Order Number: " + STRING(OrderNum) + CHR(10)
+ "Requested Delivery: " + ReqDate + CHR(10)
+ "Scheduled ShipDate: " + SchedDate + CHR(10)
+ "Comment: " + CHR(10)
+ Comment.

run SendEmail in hEmailEx
(false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).

On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@...> wrote:

> **
>
>
>
>
> Are you using the greater than and less than and then full email address?
> In the BAM List:
> <emailaddress1>;
> <emailaddress2>;
> <emailaddress3>;
>
> In the Bpm hard coded I put the <emailaddress> in quotes
> '<emailaddress'
> Strange its not working for you. we still have a mix, some people are
> still on Exchange 2003 and some have been moved to 2010 and this email
> format is working for both.
>
> Maybe because of the vantage version you are on. Heres what I did to
> troubleshoot this. Look at one of the emails that are not formatted
> correctly, Look at the header. When I looked at one of ours, I could see
> that exchange 2010 was putting <> around what it thought was the email
> address. So I thought since exchange can't figure out where to put < > I
> will send it the way exchange is trying to format it. This was a problem
> for us for a long time, it is working great now. I hope this helps.
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
> >
> > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> problem.ï¿½ I tried your suggestion, but I keep getting an invalid address
> returned from the Exchange server.ï¿½ Could you please provide a couple of
> examples so I can see if there is something I am doing wrong?
> >
> >
> >
> >
> > ________________________________
> > From: hellybell12 <hellybell12@...>
>
> > To: vantage@yahoogroups.com
> > Sent: Thursday, October 18, 2012 7:27 AM
> > Subject: [Vantage] Re: Email addresses look odd with @name
> >
> > ï¿½
> >
> > I just looked at my reply and see that my email address formating has
> been truncated. It should be: <Fullemailaddress> for BAM and
> > '<Fullemailaddress>'
> > Sorry about that.
> > Helen
> >
> > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@>
> wrote:
> > >>
> > > Hi All,
> > > We are on E9 and email was fine with Exchange 2003, when we moved to
> Exchange 2010 emails will reach it's destination but you cannot reply all.
> Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > It does this to the entire email list. I found a solution that is
> working for us. You have to format the email address as follows:
> > > For BAM or Global Alerts:
> > > <User@>;
> > > <User2@>;
> > >
> > > For coded BPM email: '<User@>'
> > >
> > > We put this in place and all is well. I hope this helps someone out
> there.
> > > Have a great day.
> > > Helen
> > > Saugus MA
> > >
> > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@>
> wrote:
> > > >
> > > > If you don't mind, please let us know what they say.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: Greg Payne <gpayne@>
> > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> vantage%40yahoogroups.com>
> > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > Subject: [Vantage] Email addresses look odd with @name
> > > >
> > > >
> > > > ï¿½ï¿½ï¿½
> > > > yes, we do and sorry for not changing the subject line.
> > > >
> > > > I see it already converted in the smtp log though. I put in a call
> to support.
> > > >
> > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> info%40compulink-usa.com>
> > > >
> > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com
> >
> > > >
> > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > >
> > > > Greg
> > > >
> > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > To: mailto:vantage%40yahoogroups.com
> > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> Sales Order entry
> > > >
> > > >
> > > >
> > > > I bet you have an Exchange Server. Ours use to work in 8.03, but
> somwhere during an update it started to do what yours is doing and no one
> could ever figure out why. No other applications have this problem with our
> email server, only Vantage.
> > > >
> > > > Steven G.
> > > >
> > > > ________________________________
> > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> gpayne%40compulink-usa.com>>
> > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:
> vantage%40yahoogroups.com>>
> > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> Sales Order entry
> > > >
> > > >
> > > > Is there a way with a BAM or global alert to format the email
> address so it is an address that can be replied to?
> > > >
> > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:
> mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto
> :mailto:info%40compulink-usa.com>>) when the field just has the email
> address in it. and it shows as @info
> > > >
> > > > Thanks
> > > >
> > > > Greg
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including
> attachments, is privileged and confidential. It is intended only for the
> exclusive use of the addressee. If the reader of this message is not the
> intended recipient, or the employee or agent responsible for delivering it
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify us at (727)
> 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined
> in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> Export of this material is restricted by the Arms Export Control Act (22
> U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including
> attachments, is privileged and confidential. It is intended only for the
> exclusive use of the addressee. If the reader of this message is not the
> intended recipient, or the employee or agent responsible for delivering it
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify us at (727)
> 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined
> in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> Export of this material is restricted by the Arms Export Control Act (22
> U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>

[Non-text portions of this message have been removed]

system · May 30, 2013, 2:35pm

I struggled with this for a long time. Â My lines of code looks like this:
Â
For Each CustCnt WHERE (CustCnt.Company = Customer.Company) ANDÂ (CustCnt.CustNum = Customer.CustNum) ANDÂ (CustCnt.CheckBox02) ANDÂ (NOT CustCnt.Inactive) ANDÂ (NOT CustCnt.NoContact) NO-LOCK:
/* if email address has at least one character + @ + at least one character + . + at least one character */
IF (available custcnt) and (CustCnt.EMailAddress <> "") and ((CustCnt.EMailAddress MATCHES "*.@.*~..*") and (NUM-ENTRIES(CustCnt.EMailAddress, "@") = 2)) THEN DO:
shipemail = "<" + string(CustCnt.EMailAddress) + ">;" + shipemail.

...
...
...
Email-To = shipemail.

Â Â
But if memory serves me, I couldn't get it to work when I tried to go directly to my Exchange Server from Vantage. Â What I finally ended up doing is installing the SMTP Server Feature on my Vantage server (Windows 2008 R2) and setting that up to relay to my Exchange Server. Â After that emails worked fine, I didn't get that weird address problem, and I no longer received stuck emails in the Global Alert Message Error Log.
Â Â
Steven G.

________________________________
From: Ephraim Feldman <effgroups@...>
To: Vantage Yahoo Group <vantage@yahoogroups.com>
Sent: Thursday, May 30, 2013 1:05 PM
Subject: Re: [Vantage] Re: Email addresses look odd with @name

I tried this solution when emailing from BPM but i get a error that the
email is not valid
When i send it without the '<>' it send the email but the addresses show up
as 'user@'

here is the code i use

Â Â Â Â Â Â Â Â Â Â REPEAT:
Â Â Â Â Â Â Â Â Â Â /*create some email related variables*/
Â Â Â Â Â Â Â Â Â Â define variable vFrom as character no-undo initial '':U.
Â Â Â Â Â Â Â Â Â Â define variable vTo as character no-undo initial '':U.
Â Â Â Â Â Â Â Â Â Â define variable vCC as character no-undo initial '':U.
Â Â Â Â Â Â Â Â Â Â define variable vSubject as character no-undo initial
'':U.
Â Â Â Â Â Â Â Â Â Â define variable vBody as character no-undo initial '':U.
Â Â Â Â Â Â Â Â Â Â define variable CurrentUser AS CHARACTER NO-UNDO
initial '':U.
Â Â Â Â Â Â Â Â Â Â define variable EntryUser AS CHARACTER NO-UNDO initial
'':U.
Â Â Â Â Â Â Â Â Â Â define variable hEmailEx as handle no-undo.

Â Â Â Â Â Â Â Â Â Â run Bpm/BpmEmail.p persistent set hEmailEx.
Â Â Â Â Â Â Â Â Â Â /*I honestly can't remember why these integer cnt
variables are in here.*/
Â Â Â Â Â Â Â Â Â Â define variable from_cnt as integer no-undo.
Â Â Â Â Â Â Â Â Â Â FIND FIRST UserFile WHERE UserFile.dcduserid =
ttCallContextClient.CurrentUserId.
Â Â Â Â Â Â Â Â Â Â Â Â IF AVAIL UserFile THEN
Â Â Â Â Â Â Â Â Â Â Â Â Â Â DO:
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â assign vFrom = UserFile.EMailAddress.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â assign CurrentUser = Userfile.Name.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â END.

Â Â Â Â Â Â Â Â Â Â define variable to_cnt as integer no-undo.
Â Â Â Â Â Â Â Â Â Â FIND FIRST UserFile WHERE UserFile.dcduserid =
ttOrderHed.EntryPerson.
Â Â Â Â Â Â Â Â Â Â Â Â IF AVAIL UserFile THEN
Â Â Â Â Â Â Â Â Â Â Â Â Â Â DO:
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â assign vTo = '<' + UserFile.EMailAddress +
'>'.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â assign EntryUser = Userfile.Name.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â END.

Â Â Â Â Â Â Â Â Â Â define variable cc_cnt as integer no-undo.
Â Â Â Â Â Â Â Â Â Â Â Â FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
EmpBasic.EMailAddress <> '' No-Lock.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ASSIGN vCC = vCC + EmpBasic.EMailAddress +
';'.
Â Â Â Â Â Â Â Â Â Â Â Â END.

Â Â Â Â Â Â Â Â Â Â define variable subject_cnt as integer no-undo.
Â Â Â Â Â Â Â Â Â Â assign vSubject = 'Notification : Order #: ' +
STRING(OrderNum) + ' - has been scheduled'.

Â Â Â Â Â Â Â Â Â Â define variable body_cnt as integer no-undo.
Â Â Â Â Â Â Â Â Â Â assign vBody = "Order has been scheduled by " +
CurrentUser + ":" + CHR(10) + CHR(10)
Â Â Â Â Â Â Â Â Â Â + "Customer: " + custName + CHR(10)
Â Â Â Â Â Â Â Â Â Â + "Order Number: " + STRING(OrderNum) + CHR(10)
Â Â Â Â Â Â Â Â Â Â + "Requested Delivery: " + ReqDate + CHR(10)
Â Â Â Â Â Â Â Â Â Â + "Scheduled ShipDate: " + SchedDate + CHR(10)
Â Â Â Â Â Â Â Â Â Â + "Comment: " + CHR(10)
Â Â Â Â Â Â Â Â Â Â + Comment.

run SendEmail in hEmailEx
(false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).

On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@...> wrote:

> **
>
>
>
>
> Are you using the greater than and less than and then full email address?
> In the BAM List:
> <emailaddress1>;
> <emailaddress2>;
> <emailaddress3>;
>
> In the Bpm hard coded I put the <emailaddress> in quotes
> '<emailaddress'
> Strange its not working for you. we still have a mix, some people are
> still on Exchange 2003 and some have been moved to 2010 and this email
> format is working for both.
>
> Maybe because of the vantage version you are on. Heres what I did to
> troubleshoot this. Look at one of the emails that are not formatted
> correctly, Look at the header. When I looked at one of ours, I could see
> that exchange 2010 was putting <> around what it thought was the email
> address. So I thought since exchange can't figure out where to put < > I
> will send it the way exchange is trying to format it. This was a problem
> for us for a long time, it is working great now. I hope this helps.
>
> --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
> >
> > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> problem.Ã‚Â I tried your suggestion, but I keep getting an invalid address
> returned from the Exchange server.Ã‚Â Could you please provide a couple of
> examples so I can see if there is something I am doing wrong?
> >
> >
> >
> >
> > ________________________________
> > From: hellybell12 <hellybell12@...>
>
> > To: vantage@yahoogroups.com
> > Sent: Thursday, October 18, 2012 7:27 AM
> > Subject: [Vantage] Re: Email addresses look odd with @name
> >
> > Ã‚
> >
> > I just looked at my reply and see that my email address formating has
> been truncated. It should be: <Fullemailaddress> for BAM and
> > '<Fullemailaddress>'
> > Sorry about that.
> > Helen
> >
> > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@>
> wrote:
> > >>
> > > Hi All,
> > > We are on E9 and email was fine with Exchange 2003, when we moved to
> Exchange 2010 emails will reach it's destination but you cannot reply all.
> Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > It does this to the entire email list. I found a solution that is
> working for us. You have to format the email address as follows:
> > > For BAM or Global Alerts:
> > > <User@>;
> > > <User2@>;
> > >
> > > For coded BPM email: '<User@>'
> > >
> > > We put this in place and all is well. I hope this helps someone out
> there.
> > > Have a great day.
> > > Helen
> > > Saugus MA
> > >
> > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@>
> wrote:
> > > >
> > > > If you don't mind, please let us know what they say.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: Greg Payne <gpayne@>
> > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> vantage%40yahoogroups.com>
> > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > Subject: [Vantage] Email addresses look odd with @name
> > > >
> > > >
> > > > Ãƒâ€šÃ‚
> > > > yes, we do and sorry for not changing the subject line.
> > > >
> > > > I see it already converted in the smtp log though. I put in a call
> to support.
> > > >
> > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> info%40compulink-usa.com>
> > > >
> > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com
> >
> > > >
> > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > >
> > > > Greg
> > > >
> > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > To: mailto:vantage%40yahoogroups.com
> > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> Sales Order entry
> > > >
> > > >
> > > >
> > > > I bet you have an Exchange Server. Ours use to work in 8.03, but
> somwhere during an update it started to do what yours is doing and no one
> could ever figure out why. No other applications have this problem with our
> email server, only Vantage.
> > > >
> > > > Steven G.
> > > >
> > > > ________________________________
> > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> gpayne%40compulink-usa.com>>
> > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:
> vantage%40yahoogroups.com>>
> > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> Sales Order entry
> > > >
> > > >
> > > > Is there a way with a BAM or global alert to format the email
> address so it is an address that can be replied to?
> > > >
> > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:
> mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto
> :mailto:info%40compulink-usa.com>>) when the field just has the email
> address in it. and it shows as @info
> > > >
> > > > Thanks
> > > >
> > > > Greg
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including
> attachments, is privileged and confidential. It is intended only for the
> exclusive use of the addressee. If the reader of this message is not the
> intended recipient, or the employee or agent responsible for delivering it
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify us at (727)
> 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined
> in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> Export of this material is restricted by the Arms Export Control Act (22
> U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > > ________________________________
> > > > CONFIDENTIALITY NOTICE
> > > >
> > > > The information contained in this communication, including
> attachments, is privileged and confidential. It is intended only for the
> exclusive use of the addressee. If the reader of this message is not the
> intended recipient, or the employee or agent responsible for delivering it
> to the intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify us at (727)
> 578-6258 and immediately delete the communication.
> > > >
> > > > "This (document/presentation) may contain technical data as defined
> in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> Export of this material is restricted by the Arms Export Control Act (22
> U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> prior approval form the U.S. Department of State."
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>Â
>

[Non-text portions of this message have been removed]

------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note:Â You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links

[Non-text portions of this message have been removed]

system · May 30, 2013, 5:10pm

We are on 9.05.701 and I have been working with BAM emailing recently and I have seen the same thing. The email gets sent, but the address in outlook displays username@ the same as you. We use a local smtp server on the APP server that then relays to Exchange.

I hope this information at least makes you feel comfortable that your issue is not just isolated to your site.

Cheers
Simon Hall

--- In vantage@yahoogroups.com, Ephraim Feldman <effgroups@...> wrote:
>
> I tried this solution when emailing from BPM but i get a error that the
> email is not valid
> When i send it without the '<>' it send the email but the addresses show up
> as 'user@'
>
>
> here is the code i use
>
> REPEAT:
> /*create some email related variables*/
> define variable vFrom as character no-undo initial '':U.
> define variable vTo as character no-undo initial '':U.
> define variable vCC as character no-undo initial '':U.
> define variable vSubject as character no-undo initial
> '':U.
> define variable vBody as character no-undo initial '':U.
> define variable CurrentUser AS CHARACTER NO-UNDO
> initial '':U.
> define variable EntryUser AS CHARACTER NO-UNDO initial
> '':U.
> define variable hEmailEx as handle no-undo.
>
> run Bpm/BpmEmail.p persistent set hEmailEx.
> /*I honestly can't remember why these integer cnt
> variables are in here.*/
> define variable from_cnt as integer no-undo.
> FIND FIRST UserFile WHERE UserFile.dcduserid =
> ttCallContextClient.CurrentUserId.
> IF AVAIL UserFile THEN
> DO:
> assign vFrom = UserFile.EMailAddress.
> assign CurrentUser = Userfile.Name.
> END.
>
> define variable to_cnt as integer no-undo.
> FIND FIRST UserFile WHERE UserFile.dcduserid =
> ttOrderHed.EntryPerson.
> IF AVAIL UserFile THEN
> DO:
> assign vTo = '<' + UserFile.EMailAddress +
> '>'.
> assign EntryUser = Userfile.Name.
> END.
>
> define variable cc_cnt as integer no-undo.
> FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
> AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
> EmpBasic.EMailAddress <> '' No-Lock.
> ASSIGN vCC = vCC + EmpBasic.EMailAddress +
> ';'.
> END.
>
> define variable subject_cnt as integer no-undo.
> assign vSubject = 'Notification : Order #: ' +
> STRING(OrderNum) + ' - has been scheduled'.
>
> define variable body_cnt as integer no-undo.
> assign vBody = "Order has been scheduled by " +
> CurrentUser + ":" + CHR(10) + CHR(10)
> + "Customer: " + custName + CHR(10)
> + "Order Number: " + STRING(OrderNum) + CHR(10)
> + "Requested Delivery: " + ReqDate + CHR(10)
> + "Scheduled ShipDate: " + SchedDate + CHR(10)
> + "Comment: " + CHR(10)
> + Comment.
>
> run SendEmail in hEmailEx
> (false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).
>
>
> On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@...> wrote:
>
> > **
> >
> >
> >
> >
> > Are you using the greater than and less than and then full email address?
> > In the BAM List:
> > <emailaddress1>;
> > <emailaddress2>;
> > <emailaddress3>;
> >
> > In the Bpm hard coded I put the <emailaddress> in quotes
> > '<emailaddress'
> > Strange its not working for you. we still have a mix, some people are
> > still on Exchange 2003 and some have been moved to 2010 and this email
> > format is working for both.
> >
> > Maybe because of the vantage version you are on. Heres what I did to
> > troubleshoot this. Look at one of the emails that are not formatted
> > correctly, Look at the header. When I looked at one of ours, I could see
> > that exchange 2010 was putting <> around what it thought was the email
> > address. So I thought since exchange can't figure out where to put < > I
> > will send it the way exchange is trying to format it. This was a problem
> > for us for a long time, it is working great now. I hope this helps.
> >
> > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > >
> > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> > problem.Ã‚ I tried your suggestion, but I keep getting an invalid address
> > returned from the Exchange server.Ã‚ Could you please provide a couple of
> > examples so I can see if there is something I am doing wrong?
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: hellybell12 <hellybell12@>
> >
> > > To: vantage@yahoogroups.com
> > > Sent: Thursday, October 18, 2012 7:27 AM
> > > Subject: [Vantage] Re: Email addresses look odd with @name
> > >
> > > Ã‚
> > >
> > > I just looked at my reply and see that my email address formating has
> > been truncated. It should be: <Fullemailaddress> for BAM and
> > > '<Fullemailaddress>'
> > > Sorry about that.
> > > Helen
> > >
> > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@>
> > wrote:
> > > >>
> > > > Hi All,
> > > > We are on E9 and email was fine with Exchange 2003, when we moved to
> > Exchange 2010 emails will reach it's destination but you cannot reply all.
> > Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > It does this to the entire email list. I found a solution that is
> > working for us. You have to format the email address as follows:
> > > > For BAM or Global Alerts:
> > > > <User@>;
> > > > <User2@>;
> > > >
> > > > For coded BPM email: '<User@>'
> > > >
> > > > We put this in place and all is well. I hope this helps someone out
> > there.
> > > > Have a great day.
> > > > Helen
> > > > Saugus MA
> > > >
> > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@>
> > wrote:
> > > > >
> > > > > If you don't mind, please let us know what they say.
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: Greg Payne <gpayne@>
> > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> > vantage%40yahoogroups.com>
> > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > >
> > > > >
> > > > > ÃƒÂ‚Ã‚
> > > > > yes, we do and sorry for not changing the subject line.
> > > > >
> > > > > I see it already converted in the smtp log though. I put in a call
> > to support.
> > > > >
> > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> > info%40compulink-usa.com>
> > > > >
> > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com
> > >
> > > > >
> > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > >
> > > > > Greg
> > > > >
> > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> > 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > To: mailto:vantage%40yahoogroups.com
> > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > Sales Order entry
> > > > >
> > > > >
> > > > >
> > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but
> > somwhere during an update it started to do what yours is doing and no one
> > could ever figure out why. No other applications have this problem with our
> > email server, only Vantage.
> > > > >
> > > > > Steven G.
> > > > >
> > > > > ________________________________
> > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> > gpayne%40compulink-usa.com>>
> > > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> > vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:
> > vantage%40yahoogroups.com>>
> > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > Sales Order entry
> > > > >
> > > > >
> > > > > Is there a way with a BAM or global alert to format the email
> > address so it is an address that can be replied to?
> > > > >
> > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:
> > mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto
> > :mailto:info%40compulink-usa.com>>) when the field just has the email
> > address in it. and it shows as @info
> > > > >
> > > > > Thanks
> > > > >
> > > > > Greg
> > > > >
> > > > > ________________________________
> > > > > CONFIDENTIALITY NOTICE
> > > > >
> > > > > The information contained in this communication, including
> > attachments, is privileged and confidential. It is intended only for the
> > exclusive use of the addressee. If the reader of this message is not the
> > intended recipient, or the employee or agent responsible for delivering it
> > to the intended recipient, you are hereby notified that any dissemination,
> > distribution or copying of this communication is strictly prohibited. If
> > you have received this communication in error, please notify us at (727)
> > 578-6258 and immediately delete the communication.
> > > > >
> > > > > "This (document/presentation) may contain technical data as defined
> > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > Export of this material is restricted by the Arms Export Control Act (22
> > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > prior approval form the U.S. Department of State."
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > >
> > > > > ________________________________
> > > > > CONFIDENTIALITY NOTICE
> > > > >
> > > > > The information contained in this communication, including
> > attachments, is privileged and confidential. It is intended only for the
> > exclusive use of the addressee. If the reader of this message is not the
> > intended recipient, or the employee or agent responsible for delivering it
> > to the intended recipient, you are hereby notified that any dissemination,
> > distribution or copying of this communication is strictly prohibited. If
> > you have received this communication in error, please notify us at (727)
> > 578-6258 and immediately delete the communication.
> > > > >
> > > > > "This (document/presentation) may contain technical data as defined
> > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > Export of this material is restricted by the Arms Export Control Act (22
> > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > prior approval form the U.S. Department of State."
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>

system · July 31, 2013, 2:36am

A little further information. When you click on the @name email address in outlook you see that display name shows the name@ and the email address field shows domain name then a space and the full email address.

Looking at the epicor-log in the oe102a_wrk folder you can see the data section of the responses show the To: name@domain <name@domain>

I think the latter data is coming from our exchange server,but not sure. I'll need to look further and keep everyone up to date. Is anyone else experiencing this issue?

Cheers
Simon Hall

--- In vantage@yahoogroups.com, "s1mhall" <s1mhall@...> wrote:
>
> We are on 9.05.701 and I have been working with BAM emailing recently and I have seen the same thing. The email gets sent, but the address in outlook displays username@ the same as you. We use a local smtp server on the APP server that then relays to Exchange.
>
> I hope this information at least makes you feel comfortable that your issue is not just isolated to your site.
>
> Cheers
> Simon Hall
>
> --- In vantage@yahoogroups.com, Ephraim Feldman <effgroups@> wrote:
> >
> > I tried this solution when emailing from BPM but i get a error that the
> > email is not valid
> > When i send it without the '<>' it send the email but the addresses show up
> > as 'user@'
> >
> >
> > here is the code i use
> >
> > REPEAT:
> > /*create some email related variables*/
> > define variable vFrom as character no-undo initial '':U.
> > define variable vTo as character no-undo initial '':U.
> > define variable vCC as character no-undo initial '':U.
> > define variable vSubject as character no-undo initial
> > '':U.
> > define variable vBody as character no-undo initial '':U.
> > define variable CurrentUser AS CHARACTER NO-UNDO
> > initial '':U.
> > define variable EntryUser AS CHARACTER NO-UNDO initial
> > '':U.
> > define variable hEmailEx as handle no-undo.
> >
> > run Bpm/BpmEmail.p persistent set hEmailEx.
> > /*I honestly can't remember why these integer cnt
> > variables are in here.*/
> > define variable from_cnt as integer no-undo.
> > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > ttCallContextClient.CurrentUserId.
> > IF AVAIL UserFile THEN
> > DO:
> > assign vFrom = UserFile.EMailAddress.
> > assign CurrentUser = Userfile.Name.
> > END.
> >
> > define variable to_cnt as integer no-undo.
> > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > ttOrderHed.EntryPerson.
> > IF AVAIL UserFile THEN
> > DO:
> > assign vTo = '<' + UserFile.EMailAddress +
> > '>'.
> > assign EntryUser = Userfile.Name.
> > END.
> >
> > define variable cc_cnt as integer no-undo.
> > FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
> > AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
> > EmpBasic.EMailAddress <> '' No-Lock.
> > ASSIGN vCC = vCC + EmpBasic.EMailAddress +
> > ';'.
> > END.
> >
> > define variable subject_cnt as integer no-undo.
> > assign vSubject = 'Notification : Order #: ' +
> > STRING(OrderNum) + ' - has been scheduled'.
> >
> > define variable body_cnt as integer no-undo.
> > assign vBody = "Order has been scheduled by " +
> > CurrentUser + ":" + CHR(10) + CHR(10)
> > + "Customer: " + custName + CHR(10)
> > + "Order Number: " + STRING(OrderNum) + CHR(10)
> > + "Requested Delivery: " + ReqDate + CHR(10)
> > + "Scheduled ShipDate: " + SchedDate + CHR(10)
> > + "Comment: " + CHR(10)
> > + Comment.
> >
> > run SendEmail in hEmailEx
> > (false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).
> >
> >
> > On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@> wrote:
> >
> > > **
> > >
> > >
> > >
> > >
> > > Are you using the greater than and less than and then full email address?
> > > In the BAM List:
> > > <emailaddress1>;
> > > <emailaddress2>;
> > > <emailaddress3>;
> > >
> > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > '<emailaddress'
> > > Strange its not working for you. we still have a mix, some people are
> > > still on Exchange 2003 and some have been moved to 2010 and this email
> > > format is working for both.
> > >
> > > Maybe because of the vantage version you are on. Heres what I did to
> > > troubleshoot this. Look at one of the emails that are not formatted
> > > correctly, Look at the header. When I looked at one of ours, I could see
> > > that exchange 2010 was putting <> around what it thought was the email
> > > address. So I thought since exchange can't figure out where to put < > I
> > > will send it the way exchange is trying to format it. This was a problem
> > > for us for a long time, it is working great now. I hope this helps.
> > >
> > > --- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@> wrote:
> > > >
> > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> > > problem.Ã‚ I tried your suggestion, but I keep getting an invalid address
> > > returned from the Exchange server.Ã‚ Could you please provide a couple of
> > > examples so I can see if there is something I am doing wrong?
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: hellybell12 <hellybell12@>
> > >
> > > > To: vantage@yahoogroups.com
> > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > >
> > > > Ã‚
> > > >
> > > > I just looked at my reply and see that my email address formating has
> > > been truncated. It should be: <Fullemailaddress> for BAM and
> > > > '<Fullemailaddress>'
> > > > Sorry about that.
> > > > Helen
> > > >
> > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@>
> > > wrote:
> > > > >>
> > > > > Hi All,
> > > > > We are on E9 and email was fine with Exchange 2003, when we moved to
> > > Exchange 2010 emails will reach it's destination but you cannot reply all.
> > > Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > It does this to the entire email list. I found a solution that is
> > > working for us. You have to format the email address as follows:
> > > > > For BAM or Global Alerts:
> > > > > <User@>;
> > > > > <User2@>;
> > > > >
> > > > > For coded BPM email: '<User@>'
> > > > >
> > > > > We put this in place and all is well. I hope this helps someone out
> > > there.
> > > > > Have a great day.
> > > > > Helen
> > > > > Saugus MA
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@>
> > > wrote:
> > > > > >
> > > > > > If you don't mind, please let us know what they say.
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <gpayne@>
> > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> > > vantage%40yahoogroups.com>
> > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > >
> > > > > >
> > > > > > ÃƒÂ‚Ã‚
> > > > > > yes, we do and sorry for not changing the subject line.
> > > > > >
> > > > > > I see it already converted in the smtp log though. I put in a call
> > > to support.
> > > > > >
> > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> > > info%40compulink-usa.com>
> > > > > >
> > > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com
> > > >
> > > > > >
> > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> > > 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > > Sales Order entry
> > > > > >
> > > > > >
> > > > > >
> > > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but
> > > somwhere during an update it started to do what yours is doing and no one
> > > could ever figure out why. No other applications have this problem with our
> > > email server, only Vantage.
> > > > > >
> > > > > > Steven G.
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> > > gpayne%40compulink-usa.com>>
> > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> > > vantage%40yahoogroups.com>" <mailto:vantage%40yahoogroups.com<mailto:
> > > vantage%40yahoogroups.com>>
> > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > > Sales Order entry
> > > > > >
> > > > > >
> > > > > > Is there a way with a BAM or global alert to format the email
> > > address so it is an address that can be replied to?
> > > > > >
> > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto:
> > > mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto
> > > :mailto:info%40compulink-usa.com>>) when the field just has the email
> > > address in it. and it shows as @info
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including
> > > attachments, is privileged and confidential. It is intended only for the
> > > exclusive use of the addressee. If the reader of this message is not the
> > > intended recipient, or the employee or agent responsible for delivering it
> > > to the intended recipient, you are hereby notified that any dissemination,
> > > distribution or copying of this communication is strictly prohibited. If
> > > you have received this communication in error, please notify us at (727)
> > > 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined
> > > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > > Export of this material is restricted by the Arms Export Control Act (22
> > > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > > prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including
> > > attachments, is privileged and confidential. It is intended only for the
> > > exclusive use of the addressee. If the reader of this message is not the
> > > intended recipient, or the employee or agent responsible for delivering it
> > > to the intended recipient, you are hereby notified that any dissemination,
> > > distribution or copying of this communication is strictly prohibited. If
> > > you have received this communication in error, please notify us at (727)
> > > 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined
> > > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > > Export of this material is restricted by the Arms Export Control Act (22
> > > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > > prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

system · July 31, 2013, 11:35am

we worked with MS Exchange support and he could not solve, so I gave up on it.

Our other application uses a Linux postfix mail server and Exchange doesn't mangle the address. Maybe I will "filter" the Epicor mail thru there and see if it is any better. I recall a post on using the IIS smtp server that was working for someone.

Greg

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of s1mhall
Sent: Wednesday, July 31, 2013 2:36 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Email addresses look odd with @name

A little further information. When you click on the @name email address in outlook you see that display name shows the name@ and the email address field shows domain name then a space and the full email address.

Looking at the epicor-log in the oe102a_wrk folder you can see the data section of the responses show the To: name@domain <name@domain>

I think the latter data is coming from our exchange server,but not sure. I'll need to look further and keep everyone up to date. Is anyone else experiencing this issue?

Cheers
Simon Hall

--- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "s1mhall" <s1mhall@...<mailto:s1mhall@...>> wrote:
>
> We are on 9.05.701 and I have been working with BAM emailing recently and I have seen the same thing. The email gets sent, but the address in outlook displays username@ the same as you. We use a local smtp server on the APP server that then relays to Exchange.
>
> I hope this information at least makes you feel comfortable that your issue is not just isolated to your site.
>
> Cheers
> Simon Hall
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Ephraim Feldman <effgroups@> wrote:
> >
> > I tried this solution when emailing from BPM but i get a error that the
> > email is not valid
> > When i send it without the '<>' it send the email but the addresses show up
> > as 'user@'
> >
> >
> > here is the code i use
> >
> > REPEAT:
> > /*create some email related variables*/
> > define variable vFrom as character no-undo initial '':U.
> > define variable vTo as character no-undo initial '':U.
> > define variable vCC as character no-undo initial '':U.
> > define variable vSubject as character no-undo initial
> > '':U.
> > define variable vBody as character no-undo initial '':U.
> > define variable CurrentUser AS CHARACTER NO-UNDO
> > initial '':U.
> > define variable EntryUser AS CHARACTER NO-UNDO initial
> > '':U.
> > define variable hEmailEx as handle no-undo.
> >
> > run Bpm/BpmEmail.p persistent set hEmailEx.
> > /*I honestly can't remember why these integer cnt
> > variables are in here.*/
> > define variable from_cnt as integer no-undo.
> > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > ttCallContextClient.CurrentUserId.
> > IF AVAIL UserFile THEN
> > DO:
> > assign vFrom = UserFile.EMailAddress.
> > assign CurrentUser = Userfile.Name.
> > END.
> >
> > define variable to_cnt as integer no-undo.
> > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > ttOrderHed.EntryPerson.
> > IF AVAIL UserFile THEN
> > DO:
> > assign vTo = '<' + UserFile.EMailAddress +
> > '>'.
> > assign EntryUser = Userfile.Name.
> > END.
> >
> > define variable cc_cnt as integer no-undo.
> > FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
> > AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
> > EmpBasic.EMailAddress <> '' No-Lock.
> > ASSIGN vCC = vCC + EmpBasic.EMailAddress +
> > ';'.
> > END.
> >
> > define variable subject_cnt as integer no-undo.
> > assign vSubject = 'Notification : Order #: ' +
> > STRING(OrderNum) + ' - has been scheduled'.
> >
> > define variable body_cnt as integer no-undo.
> > assign vBody = "Order has been scheduled by " +
> > CurrentUser + ":" + CHR(10) + CHR(10)
> > + "Customer: " + custName + CHR(10)
> > + "Order Number: " + STRING(OrderNum) + CHR(10)
> > + "Requested Delivery: " + ReqDate + CHR(10)
> > + "Scheduled ShipDate: " + SchedDate + CHR(10)
> > + "Comment: " + CHR(10)
> > + Comment.
> >
> > run SendEmail in hEmailEx
> > (false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).
> >
> >
> > On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@> wrote:
> >
> > > **
> > >
> > >
> > >
> > >
> > > Are you using the greater than and less than and then full email address?
> > > In the BAM List:
> > > <emailaddress1>;
> > > <emailaddress2>;
> > > <emailaddress3>;
> > >
> > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > '<emailaddress'
> > > Strange its not working for you. we still have a mix, some people are
> > > still on Exchange 2003 and some have been moved to 2010 and this email
> > > format is working for both.
> > >
> > > Maybe because of the vantage version you are on. Heres what I did to
> > > troubleshoot this. Look at one of the emails that are not formatted
> > > correctly, Look at the header. When I looked at one of ours, I could see
> > > that exchange 2010 was putting <> around what it thought was the email
> > > address. So I thought since exchange can't figure out where to put < > I
> > > will send it the way exchange is trying to format it. This was a problem
> > > for us for a long time, it is working great now. I hope this helps.
> > >
> > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, Steven Gotschall <sgotschall@> wrote:
> > > >
> > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> > > problem.Ã‚ I tried your suggestion, but I keep getting an invalid address
> > > returned from the Exchange server.Ã‚ Could you please provide a couple of
> > > examples so I can see if there is something I am doing wrong?
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: hellybell12 <hellybell12@>
> > >
> > > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > >
> > > > Ã‚
> > > >
> > > > I just looked at my reply and see that my email address formating has
> > > been truncated. It should be: <Fullemailaddress> for BAM and
> > > > '<Fullemailaddress>'
> > > > Sorry about that.
> > > > Helen
> > > >
> > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12" <hellybell12@>
> > > wrote:
> > > > >>
> > > > > Hi All,
> > > > > We are on E9 and email was fine with Exchange 2003, when we moved to
> > > Exchange 2010 emails will reach it's destination but you cannot reply all.
> > > Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > It does this to the entire email list. I found a solution that is
> > > working for us. You have to format the email address as follows:
> > > > > For BAM or Global Alerts:
> > > > > <User@>;
> > > > > <User2@>;
> > > > >
> > > > > For coded BPM email: '<User@>'
> > > > >
> > > > > We put this in place and all is well. I hope this helps someone out
> > > there.
> > > > > Have a great day.
> > > > > Helen
> > > > > Saugus MA
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall <sgotschall@>
> > > wrote:
> > > > > >
> > > > > > If you don't mind, please let us know what they say.
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <gpayne@>
> > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
<mailto:%0b>> > > vantage%40yahoogroups.com>
> > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > >
> > > > > >
> > > > > > Ãƒ'Ã‚
> > > > > > yes, we do and sorry for not changing the subject line.
> > > > > >
> > > > > > I see it already converted in the smtp log though. I put in a call
> > > to support.
> > > > > >
> > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
<mailto:%0b>> > > info%40compulink-usa.com>
> > > > > >
> > > > > > To: mailto:mese%40compulink-usa.com <mailto:mese%40compulink-usa.com
<mailto:mese%40compulink-usa.com%0b>> > > >
> > > > > >
> > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> > > 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > > Sales Order entry
> > > > > >
> > > > > >
> > > > > >
> > > > > > I bet you have an Exchange Server. Ours use to work in 8.03, but
> > > somwhere during an update it started to do what yours is doing and no one
> > > could ever figure out why. No other applications have this problem with our
> > > email server, only Vantage.
> > > > > >
> > > > > > Steven G.
> > > > > >
> > > > > > ________________________________
> > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
<mailto:gpayne%40compulink-usa.com%3cmailto:%0b>> > > gpayne%40compulink-usa.com>>
> > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> > > vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com%3cmailto:%0b%3e%20%3e%20%3e%20vantage%40yahoogroups.com%3e>" <mailto:vantage%40yahoogroups.com<mailto:
<mailto:vantage%40yahoogroups.com%3cmailto:%0b>> > > vantage%40yahoogroups.com>>
> > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button in
> > > Sales Order entry
> > > > > >
> > > > > >
> > > > > > Is there a way with a BAM or global alert to format the email
> > > address so it is an address that can be replied to?
> > > > > >
> > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com<mailto<mailto:info%40compulink-usa.com%3cmailto>:
> > > mailto:info%40compulink-usa.com<mailto:info%40compulink-usa.com%3cmailto<mailto:info%40compulink-usa.com%3cmailto:info%40compulink-usa.com%3cmailto>
> > > :mailto:info%40compulink-usa.com>>) when the field just has the email
> > > address in it. and it shows as @info
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > Greg
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including
> > > attachments, is privileged and confidential. It is intended only for the
> > > exclusive use of the addressee. If the reader of this message is not the
> > > intended recipient, or the employee or agent responsible for delivering it
> > > to the intended recipient, you are hereby notified that any dissemination,
> > > distribution or copying of this communication is strictly prohibited. If
> > > you have received this communication in error, please notify us at (727)
> > > 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined
> > > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > > Export of this material is restricted by the Arms Export Control Act (22
> > > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > > prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > > ________________________________
> > > > > > CONFIDENTIALITY NOTICE
> > > > > >
> > > > > > The information contained in this communication, including
> > > attachments, is privileged and confidential. It is intended only for the
> > > exclusive use of the addressee. If the reader of this message is not the
> > > intended recipient, or the employee or agent responsible for delivering it
> > > to the intended recipient, you are hereby notified that any dissemination,
> > > distribution or copying of this communication is strictly prohibited. If
> > > you have received this communication in error, please notify us at (727)
> > > 578-6258 and immediately delete the communication.
> > > > > >
> > > > > > "This (document/presentation) may contain technical data as defined
> > > in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10.
> > > Export of this material is restricted by the Arms Export Control Act (22
> > > U.S.C. 2751 et seq.) and may not be exported to foreign persons without
> > > prior approval form the U.S. Department of State."
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > [Non-text portions of this message have been removed]
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

________________________________
CONFIDENTIALITY NOTICE

The information contained in this communication, including attachments, is privileged and confidential. It is intended only for the exclusive use of the addressee. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us at 727-578-6280 and immediately delete the communication.

"This (document/presentation) may contain technical data as defined in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons without prior approval form the U.S. Department of State."

[Non-text portions of this message have been removed]

system · July 31, 2013, 11:46am

The email addresses need to be supplied with a trailing >; Example: test@
test.com>;
see if that helps

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*

On Wed, Jul 31, 2013 at 11:35 AM, Greg Payne <gpayne@...>wrote:

> **
>
>
> we worked with MS Exchange support and he could not solve, so I gave up on
> it.
>
> Our other application uses a Linux postfix mail server and Exchange
> doesn't mangle the address. Maybe I will "filter" the Epicor mail thru
> there and see if it is any better. I recall a post on using the IIS smtp
> server that was working for someone.
>
> Greg
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of s1mhall
> Sent: Wednesday, July 31, 2013 2:36 AM
> To: vantage@yahoogroups.com
>
> Subject: [Vantage] Re: Email addresses look odd with @name
>
> A little further information. When you click on the @name email address in
> outlook you see that display name shows the name@ and the email address
> field shows domain name then a space and the full email address.
>
> Looking at the epicor-log in the oe102a_wrk folder you can see the data
> section of the responses show the To: name@domain <name@domain>
>
> I think the latter data is coming from our exchange server,but not sure.
> I'll need to look further and keep everyone up to date. Is anyone else
> experiencing this issue?
>
> Cheers
> Simon Hall
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> "s1mhall" <s1mhall@...<mailto:s1mhall@...>> wrote:
> >
> > We are on 9.05.701 and I have been working with BAM emailing recently
> and I have seen the same thing. The email gets sent, but the address in
> outlook displays username@ the same as you. We use a local smtp server on
> the APP server that then relays to Exchange.
> >
> > I hope this information at least makes you feel comfortable that your
> issue is not just isolated to your site.
> >
> > Cheers
> > Simon Hall
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> Ephraim Feldman <effgroups@> wrote:
> > >
> > > I tried this solution when emailing from BPM but i get a error that the
> > > email is not valid
> > > When i send it without the '<>' it send the email but the addresses
> show up
> > > as 'user@'
> > >
> > >
> > > here is the code i use
> > >
> > > REPEAT:
> > > /*create some email related variables*/
> > > define variable vFrom as character no-undo initial '':U.
> > > define variable vTo as character no-undo initial '':U.
> > > define variable vCC as character no-undo initial '':U.
> > > define variable vSubject as character no-undo initial
> > > '':U.
> > > define variable vBody as character no-undo initial '':U.
> > > define variable CurrentUser AS CHARACTER NO-UNDO
> > > initial '':U.
> > > define variable EntryUser AS CHARACTER NO-UNDO initial
> > > '':U.
> > > define variable hEmailEx as handle no-undo.
> > >
> > > run Bpm/BpmEmail.p persistent set hEmailEx.
> > > /*I honestly can't remember why these integer cnt
> > > variables are in here.*/
> > > define variable from_cnt as integer no-undo.
> > > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > > ttCallContextClient.CurrentUserId.
> > > IF AVAIL UserFile THEN
> > > DO:
> > > assign vFrom = UserFile.EMailAddress.
> > > assign CurrentUser = Userfile.Name.
> > > END.
> > >
> > > define variable to_cnt as integer no-undo.
> > > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > > ttOrderHed.EntryPerson.
> > > IF AVAIL UserFile THEN
> > > DO:
> > > assign vTo = '<' + UserFile.EMailAddress +
> > > '>'.
> > > assign EntryUser = Userfile.Name.
> > > END.
> > >
> > > define variable cc_cnt as integer no-undo.
> > > FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
> > > AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
> > > EmpBasic.EMailAddress <> '' No-Lock.
> > > ASSIGN vCC = vCC + EmpBasic.EMailAddress +
> > > ';'.
> > > END.
> > >
> > > define variable subject_cnt as integer no-undo.
> > > assign vSubject = 'Notification : Order #: ' +
> > > STRING(OrderNum) + ' - has been scheduled'.
> > >
> > > define variable body_cnt as integer no-undo.
> > > assign vBody = "Order has been scheduled by " +
> > > CurrentUser + ":" + CHR(10) + CHR(10)
> > > + "Customer: " + custName + CHR(10)
> > > + "Order Number: " + STRING(OrderNum) + CHR(10)
> > > + "Requested Delivery: " + ReqDate + CHR(10)
> > > + "Scheduled ShipDate: " + SchedDate + CHR(10)
> > > + "Comment: " + CHR(10)
> > > + Comment.
> > >
> > > run SendEmail in hEmailEx
> > > (false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).
> > >
> > >
> > > On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@> wrote:
> > >
> > > > **
> > > >
> > > >
> > > >
> > > >
> > > > Are you using the greater than and less than and then full email
> address?
> > > > In the BAM List:
> > > > <emailaddress1>;
> > > > <emailaddress2>;
> > > > <emailaddress3>;
> > > >
> > > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > > '<emailaddress'
> > > > Strange its not working for you. we still have a mix, some people are
> > > > still on Exchange 2003 and some have been moved to 2010 and this
> email
> > > > format is working for both.
> > > >
> > > > Maybe because of the vantage version you are on. Heres what I did to
> > > > troubleshoot this. Look at one of the emails that are not formatted
> > > > correctly, Look at the header. When I looked at one of ours, I could
> see
> > > > that exchange 2010 was putting <> around what it thought was the
> email
> > > > address. So I thought since exchange can't figure out where to put <
> > I
> > > > will send it the way exchange is trying to format it. This was a
> problem
> > > > for us for a long time, it is working great now. I hope this helps.
> > > >
> > > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> Steven Gotschall <sgotschall@> wrote:
> > > > >
> > > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> > > > problem.ï¿½ I tried your suggestion, but I keep getting an invalid
> address
> > > > returned from the Exchange server.ï¿½ Could you please provide a
> couple of
> > > > examples so I can see if there is something I am doing wrong?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: hellybell12 <hellybell12@>
> > > >
> > > > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
>
> > > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > > >
> > > > > ï¿½
> > > > >
> > > > > I just looked at my reply and see that my email address formating
> has
> > > > been truncated. It should be: <Fullemailaddress> for BAM and
> > > > > '<Fullemailaddress>'
> > > > > Sorry about that.
> > > > > Helen
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12"
> <hellybell12@>
> > > > wrote:
> > > > > >>
> > > > > > Hi All,
> > > > > > We are on E9 and email was fine with Exchange 2003, when we
> moved to
> > > > Exchange 2010 emails will reach it's destination but you cannot
> reply all.
> > > > Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > > It does this to the entire email list. I found a solution that is
> > > > working for us. You have to format the email address as follows:
> > > > > > For BAM or Global Alerts:
> > > > > > <User@>;
> > > > > > <User2@>;
> > > > > >
> > > > > > For coded BPM email: '<User@>'
> > > > > >
> > > > > > We put this in place and all is well. I hope this helps someone
> out
> > > > there.
> > > > > > Have a great day.
> > > > > > Helen
> > > > > > Saugus MA
> > > > > >
> > > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall
> <sgotschall@>
> > > > wrote:
> > > > > > >
> > > > > > > If you don't mind, please let us know what they say.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <gpayne@>
> > > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> <mailto:%0b>> > > vantage%40yahoogroups.com>
>
> > > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > > >
> > > > > > >
> > > > > > > ï¿½'ï¿½
> > > > > > > yes, we do and sorry for not changing the subject line.
> > > > > > >
> > > > > > > I see it already converted in the smtp log though. I put in a
> call
> > > > to support.
> > > > > > >
> > > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> <mailto:%0b>> > > info%40compulink-usa.com>
>
> > > > > > >
> > > > > > > To: mailto:mese%40compulink-usa.com <mailto:
> mese%40compulink-usa.com
> <mailto:mese%40compulink-usa.com%0b>> > > >
>
> > > > > > >
> > > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> > > > 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process
> button in
> > > > Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I bet you have an Exchange Server. Ours use to work in 8.03,
> but
> > > > somwhere during an update it started to do what yours is doing and
> no one
> > > > could ever figure out why. No other applications have this problem
> with our
> > > > email server, only Vantage.
> > > > > > >
> > > > > > > Steven G.
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> <mailto:gpayne%40compulink-usa.com%3cmailto:%0b>> > > gpayne%
> 40compulink-usa.com>>
> > > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> > > > vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com%3cmailto
> :%0b%3e%20%3e%20%3e%20vantage%40yahoogroups.com%3e>" <mailto:
> vantage%40yahoogroups.com<mailto:
> <mailto:vantage%40yahoogroups.com%3cmailto:%0b>> > > vantage%
> 40yahoogroups.com>>
>
> > > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button
> in
> > > > Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > > Is there a way with a BAM or global alert to format the email
> > > > address so it is an address that can be replied to?
> > > > > > >
> > > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com
> <mailto<mailto:info%40compulink-usa.com%3cmailto>:
> > > > mailto:info%40compulink-usa.com<mailto:
> info%40compulink-usa.com%3cmailto<mailto:info%40compulink-usa.com%3cmailto
> :info%40compulink-usa.com%3cmailto>
>
> > > > :mailto:info%40compulink-usa.com>>) when the field just has the
> email
> > > > address in it. and it shows as @info
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including
> > > > attachments, is privileged and confidential. It is intended only for
> the
> > > > exclusive use of the addressee. If the reader of this message is not
> the
> > > > intended recipient, or the employee or agent responsible for
> delivering it
> > > > to the intended recipient, you are hereby notified that any
> dissemination,
> > > > distribution or copying of this communication is strictly
> prohibited. If
> > > > you have received this communication in error, please notify us at
> (727)
> > > > 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as
> defined
> > > > in the International Traffic In Arms Regulations (ITAR) 22 CFR
> 120.10.
> > > > Export of this material is restricted by the Arms Export Control Act
> (22
> > > > U.S.C. 2751 et seq.) and may not be exported to foreign persons
> without
> > > > prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including
> > > > attachments, is privileged and confidential. It is intended only for
> the
> > > > exclusive use of the addressee. If the reader of this message is not
> the
> > > > intended recipient, or the employee or agent responsible for
> delivering it
> > > > to the intended recipient, you are hereby notified that any
> dissemination,
> > > > distribution or copying of this communication is strictly
> prohibited. If
> > > > you have received this communication in error, please notify us at
> (727)
> > > > 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as
> defined
> > > > in the International Traffic In Arms Regulations (ITAR) 22 CFR
> 120.10.
> > > > Export of this material is restricted by the Arms Export Control Act
> (22
> > > > U.S.C. 2751 et seq.) and may not be exported to foreign persons
> without
> > > > prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
> ________________________________
> CONFIDENTIALITY NOTICE
>
> The information contained in this communication, including attachments, is
> privileged and confidential. It is intended only for the exclusive use of
> the addressee. If the reader of this message is not the intended recipient,
> or the employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this communication in error, please notify us at 727-578-6280 and
> immediately delete the communication.
>
>
> "This (document/presentation) may contain technical data as defined in the
> International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of
> this material is restricted by the Arms Export Control Act (22 U.S.C. 2751
> et seq.) and may not be exported to foreign persons without prior approval
> form the U.S. Department of State."
>
> [Non-text portions of this message have been removed]
>
>
>

[Non-text portions of this message have been removed]

system · July 31, 2013, 12:10pm

Nice Jose, I always wondered how to get around that little annoyance. Thanks.

________________________________
From: Jose Gomez <jose@...>
To: Vantage <vantage@yahoogroups.com>
Sent: Wednesday, July 31, 2013 11:45 AM
Subject: Re: [Vantage] Re: Email addresses look odd with @name

The email addresses need to be supplied with a trailing >;Â Â Example: test@
test.com>;
see if that helps

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez>Â <http://www.facebook.com/josegomez>
Â <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
Â <http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
Â <http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*

On Wed, Jul 31, 2013 at 11:35 AM, Greg Payne <gpayne@...>wrote:

> **
>
>
> we worked with MS Exchange support and he could not solve, so I gave up on
> it.
>
> Our other application uses a Linux postfix mail server and Exchange
> doesn't mangle the address. Maybe I will "filter" the Epicor mail thru
> there and see if it is any better. I recall a post on using the IIS smtp
> server that was working for someone.
>
> Greg
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of s1mhall
> Sent: Wednesday, July 31, 2013 2:36 AM
> To: vantage@yahoogroups.com
>
> Subject: [Vantage] Re: Email addresses look odd with @name
>
> A little further information. When you click on the @name email address in
> outlook you see that display name shows the name@ and the email address
> field shows domain name then a space and the full email address.
>
> Looking at the epicor-log in the oe102a_wrk folder you can see the data
> section of the responses show the To: name@domain <name@domain>
>
> I think the latter data is coming from our exchange server,but not sure.
> I'll need to look further and keep everyone up to date. Is anyone else
> experiencing this issue?
>
> Cheers
> Simon Hall
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> "s1mhall" <s1mhall@...<mailto:s1mhall@...>> wrote:
> >
> > We are on 9.05.701 and I have been working with BAM emailing recently
> and I have seen the same thing. The email gets sent, but the address in
> outlook displays username@ the same as you. We use a local smtp server on
> the APP server that then relays to Exchange.
> >
> > I hope this information at least makes you feel comfortable that your
> issue is not just isolated to your site.
> >
> > Cheers
> > Simon Hall
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> Ephraim Feldman <effgroups@> wrote:
> > >
> > > I tried this solution when emailing from BPM but i get a error that the
> > > email is not valid
> > > When i send it without the '<>' it send the email but the addresses
> show up
> > > as 'user@'
> > >
> > >
> > > here is the code i use
> > >
> > > REPEAT:
> > > /*create some email related variables*/
> > > define variable vFrom as character no-undo initial '':U.
> > > define variable vTo as character no-undo initial '':U.
> > > define variable vCC as character no-undo initial '':U.
> > > define variable vSubject as character no-undo initial
> > > '':U.
> > > define variable vBody as character no-undo initial '':U.
> > > define variable CurrentUser AS CHARACTER NO-UNDO
> > > initial '':U.
> > > define variable EntryUser AS CHARACTER NO-UNDO initial
> > > '':U.
> > > define variable hEmailEx as handle no-undo.
> > >
> > > run Bpm/BpmEmail.p persistent set hEmailEx.
> > > /*I honestly can't remember why these integer cnt
> > > variables are in here.*/
> > > define variable from_cnt as integer no-undo.
> > > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > > ttCallContextClient.CurrentUserId.
> > > IF AVAIL UserFile THEN
> > > DO:
> > > assign vFrom = UserFile.EMailAddress.
> > > assign CurrentUser = Userfile.Name.
> > > END.
> > >
> > > define variable to_cnt as integer no-undo.
> > > FIND FIRST UserFile WHERE UserFile.dcduserid =
> > > ttOrderHed.EntryPerson.
> > > IF AVAIL UserFile THEN
> > > DO:
> > > assign vTo = '<' + UserFile.EMailAddress +
> > > '>'.
> > > assign EntryUser = Userfile.Name.
> > > END.
> > >
> > > define variable cc_cnt as integer no-undo.
> > > FOR EACH EmpBasic WHERE EmpBasic.Company = CUR-COMP
> > > AND EmpBasic.EmpStatus = 'A' AND EmpBasic.CheckBox02 AND
> > > EmpBasic.EMailAddress <> '' No-Lock.
> > > ASSIGN vCC = vCC + EmpBasic.EMailAddress +
> > > ';'.
> > > END.
> > >
> > > define variable subject_cnt as integer no-undo.
> > > assign vSubject = 'Notification : Order #: ' +
> > > STRING(OrderNum) + ' - has been scheduled'.
> > >
> > > define variable body_cnt as integer no-undo.
> > > assign vBody = "Order has been scheduled by " +
> > > CurrentUser + ":" + CHR(10) + CHR(10)
> > > + "Customer: " + custName + CHR(10)
> > > + "Order Number: " + STRING(OrderNum) + CHR(10)
> > > + "Requested Delivery: " + ReqDate + CHR(10)
> > > + "Scheduled ShipDate: " + SchedDate + CHR(10)
> > > + "Comment: " + CHR(10)
> > > + Comment.
> > >
> > > run SendEmail in hEmailEx
> > > (false,CUR-COMP,vFrom,vTo,vCC,vSubject,vBody,"":U).
> > >
> > >
> > > On Thu, Oct 18, 2012 at 10:40 AM, hellybell12 <hellybell12@> wrote:
> > >
> > > > **
> > > >
> > > >
> > > >
> > > >
> > > > Are you using the greater than and less than and then full email
> address?
> > > > In the BAM List:
> > > > <emailaddress1>;
> > > > <emailaddress2>;
> > > > <emailaddress3>;
> > > >
> > > > In the Bpm hard coded I put the <emailaddress> in quotes
> > > > '<emailaddress'
> > > > Strange its not working for you. we still have a mix, some people are
> > > > still on Exchange 2003 and some have been moved to 2010 and this
> email
> > > > format is working for both.
> > > >
> > > > Maybe because of the vantage version you are on. Heres what I did to
> > > > troubleshoot this. Look at one of the emails that are not formatted
> > > > correctly, Look at the header. When I looked at one of ours, I could
> see
> > > > that exchange 2010 was putting <> around what it thought was the
> email
> > > > address. So I thought since exchange can't figure out where to put <
> > I
> > > > will send it the way exchange is trying to format it. This was a
> problem
> > > > for us for a long time, it is working great now. I hope this helps.
> > > >
> > > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>,
> Steven Gotschall <sgotschall@> wrote:
> > > > >
> > > > > We are on Vantage 8.03.408a with Exchange 2007 and we have the same
> > > > problem.Ã‚ I tried your suggestion, but I keep getting an invalid
> address
> > > > returned from the Exchange server.Ã‚ Could you please provide a
> couple of
> > > > examples so I can see if there is something I am doing wrong?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: hellybell12 <hellybell12@>
> > > >
> > > > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
>
> > > > > Sent: Thursday, October 18, 2012 7:27 AM
> > > > > Subject: [Vantage] Re: Email addresses look odd with @name
> > > > >
> > > > > Ã‚
> > > > >
> > > > > I just looked at my reply and see that my email address formating
> has
> > > > been truncated. It should be: <Fullemailaddress> for BAM and
> > > > > '<Fullemailaddress>'
> > > > > Sorry about that.
> > > > > Helen
> > > > >
> > > > > --- In mailto:vantage%40yahoogroups.com, "hellybell12"
> <hellybell12@>
> > > > wrote:
> > > > > >>
> > > > > > Hi All,
> > > > > > We are on E9 and email was fine with Exchange 2003, when we
> moved to
> > > > Exchange 2010 emails will reach it's destination but you cannot
> reply all.
> > > > Emails are delivered and look similar to: 'User@'<Company.com;User@>
> > > > > > It does this to the entire email list. I found a solution that is
> > > > working for us. You have to format the email address as follows:
> > > > > > For BAM or Global Alerts:
> > > > > > <User@>;
> > > > > > <User2@>;
> > > > > >
> > > > > > For coded BPM email: '<User@>'
> > > > > >
> > > > > > We put this in place and all is well. I hope this helps someone
> out
> > > > there.
> > > > > > Have a great day.
> > > > > > Helen
> > > > > > Saugus MA
> > > > > >
> > > > > > --- In mailto:vantage%40yahoogroups.com, Steven Gotschall
> <sgotschall@>
> > > > wrote:
> > > > > > >
> > > > > > > If you don't mind, please let us know what they say.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <gpayne@>
> > > > > > > To: "mailto:vantage%40yahoogroups.com" <mailto:
> <mailto:%0b>> > > vantage%40yahoogroups.com>
>
> > > > > > > Sent: Friday, August 24, 2012 10:15 PM
> > > > > > > Subject: [Vantage] Email addresses look odd with @name
> > > > > > >
> > > > > > >
> > > > > > > Ãƒ'Ã‚
> > > > > > > yes, we do and sorry for not changing the subject line.
> > > > > > >
> > > > > > > I see it already converted in the smtp log though. I put in a
> call
> > > > to support.
> > > > > > >
> > > > > > > 08/24/12 17:18:54 SendCommand: From: Epicor Info <mailto:
> <mailto:%0b>> > > info%40compulink-usa.com>
>
> > > > > > >
> > > > > > > To: mailto:mese%40compulink-usa.com <mailto:
> mese%40compulink-usa.com
>Â <mailto:mese%40compulink-usa.com%0b>> > > >
>
> > > > > > >
> > > > > > > CC: mailto:info%40compulink.com <mailto:info%40compulink.com>
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > From: mailto:vantage%40yahoogroups.com [mailto:mailto:vantage%
> > > > 40yahoogroups.com] On Behalf Of Steven Gotschall
> > > > > > > Sent: Friday, August 24, 2012 4:27 PM
> > > > > > > To: mailto:vantage%40yahoogroups.com
> > > > > > > Subject: Re: [Vantage] RE: Re: Epicor 9 - Ready to Process
> button in
> > > > Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > I bet you have an Exchange Server. Ours use to work in 8.03,
> but
> > > > somwhere during an update it started to do what yours is doing and
> no one
> > > > could ever figure out why. No other applications have this problem
> with our
> > > > email server, only Vantage.
> > > > > > >
> > > > > > > Steven G.
> > > > > > >
> > > > > > > ________________________________
> > > > > > > From: Greg Payne <mailto:gpayne%40compulink-usa.com<mailto:
> <mailto:gpayne%40compulink-usa.com%3cmailto:%0b>> > > gpayne%
> 40compulink-usa.com>>
> > > > > > > To: "mailto:vantage%40yahoogroups.com<mailto:
> > > > vantage%40yahoogroups.com><mailto:vantage%40yahoogroups.com%3cmailto
> :%0b%3e%20%3e%20%3e%20vantage%40yahoogroups.com%3e>" <mailto:
> vantage%40yahoogroups.com<mailto:
> <mailto:vantage%40yahoogroups.com%3cmailto:%0b>> > > vantage%
> 40yahoogroups.com>>
>
> > > > > > > Sent: Friday, August 24, 2012 3:35 PM
> > > > > > > Subject: [Vantage] RE: Re: Epicor 9 - Ready to Process button
> in
> > > > Sales Order entry
> > > > > > >
> > > > > > >
> > > > > > > Is there a way with a BAM or global alert to format the email
> > > > address so it is an address that can be replied to?
> > > > > > >
> > > > > > > I get (compulink-usa.com mailto:info%40compulink-usa.com
> <mailto<mailto:info%40compulink-usa.com%3cmailto>:
> > > > mailto:info%40compulink-usa.com<mailto:
> info%40compulink-usa.com%3cmailto<mailto:info%40compulink-usa.com%3cmailto
> :info%40compulink-usa.com%3cmailto>
>
> > > > :mailto:info%40compulink-usa.com>>) when the field just has the
> email
> > > > address in it. and it shows as @info
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Greg
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including
> > > > attachments, is privileged and confidential. It is intended only for
> the
> > > > exclusive use of the addressee. If the reader of this message is not
> the
> > > > intended recipient, or the employee or agent responsible for
> delivering it
> > > > to the intended recipient, you are hereby notified that any
> dissemination,
> > > > distribution or copying of this communication is strictly
> prohibited. If
> > > > you have received this communication in error, please notify us at
> (727)
> > > > 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as
> defined
> > > > in the International Traffic In Arms Regulations (ITAR) 22 CFR
> 120.10.
> > > > Export of this material is restricted by the Arms Export Control Act
> (22
> > > > U.S.C. 2751 et seq.) and may not be exported to foreign persons
> without
> > > > prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > > ________________________________
> > > > > > > CONFIDENTIALITY NOTICE
> > > > > > >
> > > > > > > The information contained in this communication, including
> > > > attachments, is privileged and confidential. It is intended only for
> the
> > > > exclusive use of the addressee. If the reader of this message is not
> the
> > > > intended recipient, or the employee or agent responsible for
> delivering it
> > > > to the intended recipient, you are hereby notified that any
> dissemination,
> > > > distribution or copying of this communication is strictly
> prohibited. If
> > > > you have received this communication in error, please notify us at
> (727)
> > > > 578-6258 and immediately delete the communication.
> > > > > > >
> > > > > > > "This (document/presentation) may contain technical data as
> defined
> > > > in the International Traffic In Arms Regulations (ITAR) 22 CFR
> 120.10.
> > > > Export of this material is restricted by the Arms Export Control Act
> (22
> > > > U.S.C. 2751 et seq.) and may not be exported to foreign persons
> without
> > > > prior approval form the U.S. Department of State."
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
> ________________________________
> CONFIDENTIALITY NOTICE
>
> The information contained in this communication, including attachments, is
> privileged and confidential. It is intended only for the exclusive use of
> the addressee. If the reader of this message is not the intended recipient,
> or the employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. If you have received
> this communication in error, please notify us at 727-578-6280 and
> immediately delete the communication.
>
>
> "This (document/presentation) may contain technical data as defined in the
> International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of
> this material is restricted by the Arms Export Control Act (22 U.S.C. 2751
> et seq.) and may not be exported to foreign persons without prior approval
> form the U.S. Department of State."
>
> [Non-text portions of this message have been removed]
>
>Â
>

[Non-text portions of this message have been removed]

------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note:Â You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links

[Non-text portions of this message have been removed]