Uh, thanks. Now I see what is the problem there. I'm using Indy 9 and
I've to modify the relay code in my app according to what you mentioned.
Sounds like the point that were missing =).
/Ari
Remy Lebeau (TeamB) wrote:
> "API" <ari.pikivirta@kolumbus.fi> wrote in message
> news:45ae4f01@newsgroups.borland.com...
>
>> I've smtp relay working nice if there is only recipients of 1 domain
>> in the recipient list of the idmessage. in case of different domains
>> in the recipient list - the first's mx server refuses to relay to
> the
>> rest of recipients..
>
> Do all of the failing recipients belong to the same domain that is
> failing the relay? If you are using TIdSMTPRelay, then it is supposed
> to be separating the recipients by domain and then relaying each group
> to the appropriate domain's SMTP server individually. Are you saying
> that is not happening?
>
>> what i want is to get all recipients listed in the mail the user
> gets
>> as they all are really recipients. I no that this is possible to
> achieve
>> by sending the mail individually to all with same domain as
> recipient,
>
> That is exactly what TIdSMTPRelay does.
>
>> but then the "to" -list is not correct.
>
> Yes, it is. When TIdSMTPRely sends a message, the RCPT TO command
> that is sent to each SMTP server is based on the parsed recipient
> domains, but the actual message data comes from TIdMessage normally.
> If there are recipients from multiple domains listed in the
> TIdMessage.Recipients property, the TO header of the message data will
> contain them all even though the message is sent to only some of the
> recipients at a time.
>
>
> Gambit
