[quote user="stuzz78"]
Just to confirm that I have the message path correct, Mecury sends messages to the ISP. ISP sends message to recipient. Recipient sends failure back to ISP. Mercury received failure from ISP. Right?
[/quote]
Maybe. The last two steps, I think, are your problem. What was the return address on the mail you sent out? Assuming it left your queue (check the core process window to see they've been processed), the mail is out of your hands and the failure will be coming back from some other host - maybe your ISP, maybe a domain's MX. The address to which that notice will be sent has to be valid. If your ISP's mail account is the sender, it'll go into your ISP's POP3 box like you say where it will be picked up. And since you've just told us that it works with webmail, something is obviously wrong with your outgoing job's return address. What was it? Check it first.
[quote user="stuzz78"]
I rang the ISP and there isn't a problem at their end. As a test, I logged into the server that Mercury checks via the ISP's Webmail service. From there I sent a message to a bogus address and received a failure instantly, and when Mercury did it's next poll for new mail it received the failure notification as it would any normal email.
From that I get the impression that the ISP's mail server work fine, but for some reason it doesn't generate failutre notification for email it's receives via Mercury. If nothing else that confirms that I don't have any filters in Mercury that deletes failures instead of receiving them (right?).
[/quote]
There are a couple of other sneaky possibilities that might cause this. But I'll bet the return address is the problem. For instance, it could be that the webmail facility injects mail using the sendmail command and is therefore immune to SMTP-level rejection so that the ISP smarthost is forced to generate a DSN. Check your queue and make sure it's empty before testing again to make sure that the job really got submitted.
Cheers,
Sabahattin
<P>[quote user="stuzz78"]&nbsp;&nbsp;</P>
<P>Just to confirm that I have the message path correct, Mecury sends messages to the ISP.&nbsp; ISP sends message to recipient.&nbsp; Recipient sends failure back to ISP.&nbsp; Mercury received failure from ISP.&nbsp; Right?</P>
<P>[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P>Maybe.&nbsp; The last two steps, I think, are your problem.&nbsp; What was the return address on the mail you sent out?&nbsp; Assuming it left your queue (check the core process window to see they've been processed), the mail is out of your hands and the failure will be coming back from some other host - maybe your ISP, maybe a domain's MX.&nbsp; The address to which that notice will be sent has to be valid.&nbsp; If your ISP's mail account is the sender, it'll go into your ISP's POP3 box like you say where it will be picked up.&nbsp; And since you've just told us that&nbsp;it works with webmail, something is obviously wrong with your outgoing job's return address.&nbsp; What was it?&nbsp; Check it first.</P>
<P mce_keep="true">&nbsp;</P>
<P>&nbsp;&nbsp;[quote user="stuzz78"]&nbsp;&nbsp;</P>
<P>&nbsp;&nbsp;I rang the ISP and there isn't a problem at their end.&nbsp; As&nbsp;a test, I logged into the server that Mercury checks via&nbsp;the ISP's Webmail service.&nbsp; From there I sent a message to a bogus address and received a failure instantly, and when Mercury did it's next poll for new mail it received the failure notification as it would any normal email.</P>
<P>From that I get the impression that the ISP's mail server work fine, but for some reason it doesn't generate failutre notification for email it's receives via Mercury. If nothing else that confirms that I don't have any filters in Mercury that deletes failures instead of receiving them (right?).</P>
<P>[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P>There are a couple of other sneaky possibilities&nbsp;that might cause this.&nbsp; But I'll bet&nbsp;the return address is the problem.&nbsp; For instance, it could be that the webmail facility injects mail using the sendmail command and is therefore immune to SMTP-level rejection so that the ISP smarthost is forced to generate a DSN.&nbsp; Check your queue and make sure it's empty before testing again to make sure that the job really got submitted.</P>
<P mce_keep="true">&nbsp;</P>
<P>Cheers,</P>
<P>Sabahattin</P>
<P mce_keep="true">&nbsp;</P>
