Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
mtfa65  
#1 Posted : Friday, January 24, 2014 9:20:19 AM(UTC)
mtfa65

Rank: Newbie

Groups: Registered
Joined: 1/16/2014(UTC)
Posts: 8
Iran (Islamic Republic Of)

Thanks: 1 times
Hi,
I made a application and use then Easendmailobj and Eagetmailobj and:
When I use then Eagetmailobj and Easendmailobj in my computer in no problem.
But When I use then application in other computer or system and when use the Easendmail for send email I got then message:
Now what should i do???
Error when use the Easendmailobj
Thanks.
ivan  
#2 Posted : Friday, January 24, 2014 9:50:47 PM(UTC)
ivan

Rank: Administration

Groups: Administrators
Joined: 11/11/2010(UTC)
Posts: 1,014

Thanks: 9 times
Was thanked: 41 time(s) in 41 post(s)


because EASendMail and EAGetMail are activex object, you MUST use

Regsvr32 "c:\my folder\EASendMailObj.dll"
Regsvr32 "c:\my folder\EAGetMailObj.dll"

to register dll as activex object.

Or you can save the following content to a file:

Code:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <file name="EASendMailObj.dll" hashalg="SHA1">
    <comClass clsid="{DF8A4FE2-221A-4504-987A-3FD4720DB929}" tlbid="{8B5A2BD0-5638-4CCA-A7FF-91B9E6768AC4}" description="Mail Class"></comClass>
    <comClass clsid="{FF80631D-E750-4C67-AFC3-5170AB72518B}" tlbid="{8B5A2BD0-5638-4CCA-A7FF-91B9E6768AC4}" description="FastSender Class"></comClass>
    <comClass clsid="{EAFC4EAA-9390-492A-8E53-E179527780F6}" tlbid="{8B5A2BD0-5638-4CCA-A7FF-91B9E6768AC4}" description="Certificate Class"></comClass>
    <comClass clsid="{036C2F8C-8D3C-4F4B-9B36-3B6F1D29C0B4}" tlbid="{8B5A2BD0-5638-4CCA-A7FF-91B9E6768AC4}" description="CertificateCollection Class"></comClass>
    <typelib tlbid="{8B5A2BD0-5638-4CCA-A7FF-91B9E6768AC4}" version="1.0" helpdir="" flags="HASDISKIMAGE"></typelib>
  </file>
 <file name="EAGetMailObj.dll" hashalg="SHA1">
    <comClass clsid="{953EFD7C-8FCE-4D9C-9BD9-E6F19A1B7FC9}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="MailClient Class"></comClass>
    <comClass clsid="{AD59203B-0C25-4192-98F2-C680D6A16738}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="Attachment Class"></comClass>
    <comClass clsid="{76BB6AA2-49D5-4452-97A0-C5F7B8910D12}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="Certificate Class"></comClass>
    <comClass clsid="{3F46EBC3-9D7F-4F73-B779-F2FC6C0B6EE7}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="HeaderCollection Class"></comClass>
    <comClass clsid="{206AF1CC-DF89-4E4E-96EB-40D7641FACFD}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="HeaderItem Class"></comClass>
    <comClass clsid="{C06966A4-9F1D-497F-84B9-9204F31994A3}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="Imap4Folder Class"></comClass>
    <comClass clsid="{AE30137E-07C8-403F-8772-07AF79C1DD2E}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="Mail Class"></comClass>
    <comClass clsid="{D6DA04B9-6D72-424A-9582-9752409AAD9C}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="MailAddress Class"></comClass>
    <comClass clsid="{CFED4866-F709-481F-89C1-4D1BF0F830D3}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="MailInfo Class"></comClass>
    <comClass clsid="{65ACB9B1-68E6-460B-9738-720E0E3A6DD3}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="MailServer Class"></comClass>
    <comClass clsid="{029033B3-0CFF-452E-8832-8101FDE8D0B4}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="MailReport Class"></comClass>
    <comClass clsid="{8B092B61-AE66-4413-B4D0-6B97FBE6DA08}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="Tools Class"></comClass>
    <comClass clsid="{440B896B-8AAD-4FEE-8F39-066F79F73E5C}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="UIDLManager Class"></comClass>
    <comClass clsid="{7096722C-E10D-42D9-A284-1E582D2B27B3}" tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" description="UIDLItem Class"></comClass>
    <typelib tlbid="{5FA52C10-18FC-4D81-8542-50F9A2DC60A3}" resourceid="1" version="1.0" helpdir="" flags="HASDISKIMAGE"></typelib>
  </file> 
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>


for example, if your application is project1.exe

then save above content to project1.exe.manifest
and put project1.exe, project1.exe.manifest, EASendMailObj.dll, EAGetMailObj.dll to the same folder, then it is ok.


Using Registration-free COM with EASendMail ActiveX Object in Delphi 7
Delphi 7 doesn't support embedded manifest, you can compile your application to exe file and use external manifest (yourappname.exe.manifest) directly.

Copy yourapp.exe, yourapp.exe.manifest and EASendMailObj.dll to the same folder on target machine, your application can use EASendMail ActiveX Object directly without COM-registration.

Using Registration-free COM with EASendMail ActiveX Object in Delphi XE or later version
It supports embedded manifest, please go to "Project -> Options -> Application" and set "Runtime Themes" to "Use > custom manifest", then specify the path to yourappname.exe.manifest file.

Alternatively, go into the Project Options, in the "Application" section, and set the "Runtime Themes" option to "none", then use external (yourappname.exe.manifest) directly.

Copy yourapp.exe, yourapp.exe.manifest and EASendMailObj.dll to the same folder on target machine, your application can use EASendMail ActiveX Object directly without COM-registration.


mtfa65  
#3 Posted : Tuesday, January 28, 2014 8:46:57 AM(UTC)
mtfa65

Rank: Newbie

Groups: Registered
Joined: 1/16/2014(UTC)
Posts: 8
Iran (Islamic Republic Of)

Thanks: 1 times
hi, thanks youre answer.
but yore Explanation for use the project.exe , project1.exe.manifest is very hard, and use then registe dll in svr32 is very easy, and I use first method, and very very good.
I have a question:
I am from iran and my writen language is persian, when i send email with delphi and by persian language,font email recived is Illegible, What should i do???
for example:
for "سلام" after send to mail, font email recived is "ÓáÇã " but when i use "سلام" in source (example:oSmtp.BodyText:='سلام';) No problem can be.
what should i do???
thanks.
ivan  
#4 Posted : Wednesday, January 29, 2014 12:17:25 AM(UTC)
ivan

Rank: Administration

Groups: Administrators
Joined: 11/11/2010(UTC)
Posts: 1,014

Thanks: 9 times
Was thanked: 41 time(s) in 41 post(s)

Hi, please try to use

oSmtp.Charset = "windows-1256"
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2019, Yet Another Forum.NET
This page was generated in 0.066 seconds.

EXPLORE TUTORIALS

© All Rights Reserved, AdminSystem Software Limited.