| View previous topic :: View next topic |
| Author |
Message |
gonebylunchtime@gmail.com Guest
|
Posted: Wed Sep 21, 2005 12:15 am Post subject: SMTP Mail problems with Indy 10 |
|
|
The following code worked fine under Indy 9/Delphi 5. I have ported it
to Indy 10/Delphi 2005 and I get an error:
EidSMTPReplyError <a@b.com> Recipient Address rejected: Access Denied
with WebUpdateForm.EmailReportMessage do
begin
Body.Clear ;
Body.Add ('User error report is attached.') ;
From.Text := 'a@b.com' ;
Recipients.EMailAddresses := 'a@b.com' ;
Subject := 'Error report' ;
ReceiptRecipient.Text := '';
TIdAttachmentFile.Create (MessageParts,
GetExecutablePath + ReportFileID);
TIdAttachmentFile.Create (MessageParts,
CurrentProject) ;
end;
with WebUpdateForm.EmailReportSMTP do
begin
AuthType := atNone ; // changed d2005
port
Username := '' ;
Password := '' ;
Host := 'smtp.acqura.com' ;
Connect;
try
try
Send (WebUpdateForm.EmailReportMessage) ;
except
end ;
finally
Disconnect;
WebUpdateForm.EmailReportMessage.MessageParts.Items [1].Free ;
WebUpdateForm.EmailReportMessage.MessageParts.Items [0].Free ;
end ;
end ;
I've tried other AuthTypes. The other thing I tried to do was add a
TidLogFile and connect it up. Any example code of how you do that
would be appreciated.
|
|
| Back to top |
|
 |
gonebylunchtime@gmail.com Guest
|
Posted: Thu Sep 22, 2005 1:43 am Post subject: Re: SMTP Mail problems with Indy 10 |
|
|
I suspect it's to do with authorization. It woks with some mail
servers but not the particular one I am trying to use. I get the
feeling after a poke around that Indy is recognised by some mail
servers as a spam sender. I still don't know how to get around it
though...
The Indy 9 code works fine without a password and username, provided
the destination address is in the same domain as the smtp server (which
it is). D2005/Indy 10 fails however.
|
|
| Back to top |
|
 |
gonebylunchtime@gmail.com Guest
|
Posted: Mon Sep 26, 2005 11:23 pm Post subject: Re: SMTP Mail problems with Indy 10 |
|
|
I just updated the Indy 10 sources to the current snapshot and it still
fails, but with Error 554 (message is probably spam or some such)
|
|
| Back to top |
|
 |
|