Re: Austin cut off.



On 27/09/2007 21:29, Guy King wrote:
Any idea why I got this?

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

austin@xxxxxxxxxxxxxxxxxxxx
Unrouteable address

a bit of furtling appears to reveal that a serpent domain dozen have any MX (i.e. mail exchanger) records defined, hence bouncy emus

C:\Documents and Settings\Andy>nslookup
Default Server: openwrt.lan
Address: 192.168.1.1

> set type=mx
> ddol-las.fsnet.co.uk
Server: openwrt.lan
Address: 192.168.1.1

fsnet.co.uk
primary name server = pridns1.svr.pol.co.uk
responsible mail addr = hostmaster.planet.net.uk
serial = 945346651
refresh = 3600 (1 hour)
retry = 1800 (30 mins)
expire = 604800 (7 days)
default TTL = 14400 (4 hours)
.



Relevant Pages

  • RE: Your message did not reach some or all of the intended recipie
    ... recipients' email addresses, and try again to check if the issue can be ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... >> 6) Do you have Recovery Storage group enabled on the SBS server? ...
    (microsoft.public.windows.server.sbs)
  • RE: Event 32090 when Faxing To Multiple Recipients
    ... Number of Recipients: 5. ... Step 2: Please check the Group Policy on SBS Server: ... After the report is created, select the report in the left panel and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Should ISPs send bounceback on mail to non-existent address?
    ... >>very easy to detect such attacks. ... >- Sympatico has told me that it simply DISCARDS AND IGNORES any incoming ... Exchange Server 5.5 or older. ... recipients address during the SMTP phase hence can genreate those 5xx ...
    (comp.mail.misc)
  • Re: Exchange in a Child domain
    ... Service (RUS) problem. ... Do your recipients have valid e-mail addresses, ... MVP - Exchange ... in the child domain on the parent domain Exchange Server. ...
    (microsoft.public.exchange.setup)
  • Re: 554 SMTP synchronisation error - when users send large numbers of messages
    ... Again, I believe the problem is with your ISP's SMTP server, that is I believe it is that server that is issuing the 554, but I wouldn't be able to say for sure without looking at the SMTP protocol logs. ... I mean our Exchange server by 'the server' - we have a simple set up - one Exchnage server that functions as mail store & SMTP box and another exchange server that handles webmail. ... An earlier test I did was to get my user's original message and recipient list and resend it from another account with a please-ignore-this-test preamble - all recipients were BCC'd. ...
    (microsoft.public.exchange.admin)