Â
ShipCCemail = "<Shipping_Notifications@...>;".
or
ShipCCemail = ShipCCemail + "<" + SalesRep.EMailAddress + ">;".
Â
Steven G.
________________________________
From: Greg Payne <gpayne@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Wednesday, July 31, 2013 11:35 AM
Subject: RE: [Vantage] Re: Email addresses look odd with @name
Â
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]