Time-out period for outgoing mail w/ bad domain?

It seems that when a user addresses an email and misspells the domain name, it takes 24 hours for the user to get a message back stating that the domain is not available.

I can’t seem to find a setting anywhere that would shorten that time frame?

Any ideas?

Subject: Time-out period for outgoing mail w/ bad domain?

Look in the admin help for :

MAILTIMEOUT=d (where d is in days)

– or –

MAILTIMEOUTMINUTES=m (where m is in minutes if you want to specify < 1 day)

Default is 24 hrs (1 day).

Subject: Time-out period for outgoing mail w/ bad domain?

In R5… not sure about ND6

http://www.drcc.com/A55711/ref/notesini.nsf/all/41C3DEF127FFF388C125668A004222AF

(Great Website!!!)

Subject: RE: Time-out period for outgoing mail w/ bad domain?

Not sure I like shortening the mail router time out - mail can queue for quite lengthy periods for legitimate reasons. That’s the whole point of the store and forward nature of SMTP.

Actually, what you will find is that mail addressed to a completely bogus Internet domain will bounce immediately with a bounce message like this:

No route found to domain no.such.domain from server YOURDOMINOHOST/YOURDOMAIN. Check DNS configuration.

Try it - just address an email to nobody@no.such.domain and see how long it takes to come back to you.

Where messages queue for long periods because the user has misspelled the domain, you will find that the misspelled domain in question does actually exist, but has no MX.

Unfortunately it is a common spammers trick to register a domain that is similar to a real one, with some minor misspelling. These are usually used to host web sites, not for mail and so rarely have MX set up.

But this should be a rare cause of queuing mail. If I were you I would leave the mail router timeout where it is, rely on the router to bounce messages addressed to invalid domains and just not worry about the occasional mail that queues for a day because of what I wrote above.

HTH

Subject: RE: Time-out period for outgoing mail w/ bad domain?

I hear what you’re saying, but no matter what domain I send the email to, it takes 24 hours to get the bounce back, if the domain is bad. I can send to asdljal;sdj@asodijf.com and it takes 24 hours for the server to tell me it’s bad.

Subject: I get an instant bounce from the server w/ the above described message.

Subject: RE: I get an instant bounce from the server w/ the above described message.

I don’t…it takes a day for mine to bounce back as well.

Subject: Time to compare configurations, because it has always worked for me.

Subject: RE: Time to compare configurations, because it has always worked for me.

Yes, it is time to compare configurations.

Does your Domino host send mail directly, or via a relay host? If you are sending via a relay host (belonging to your ISP perhaps), then it may behave differently and hang onto mail for 24 hours waiting for a non-existent domain to resolve.

If this is the case, then changing the router timeout on your Domino server will have no effect anyway.

Where does the bounce message come from? It might be informative to look at the MIME source for any bounce messages you have and see where they came from.

Subject: RE: Time to compare configurations, because it has always worked for me.

No, our server sends directly to the internet…no relay host involved.

I’ll check the bounce message once I get it back…I sent one yesterday afternoon, so it hasn’t been 24hrs yet. I can see it still sitting in the queue and I’ve tried to force delivery a few times, hoping it would then send a bounce, but it just keeps trying.

Subject: RE: Time to compare configurations, because it has always worked for me.

My domino server sends directly to the internet. No ISP involved. I too have two messages sitting in the mailbox which I have tried to route numerous times. Funny thing is, there are absolutely no messages on the server console when I send these. I went through my configuration, connection, server and domain documents with a fine-toothed comb last night. I saw nothing amiss.

Subject: Here is the page source for the failure message.

To: bigbill@teamsol.com
Subject: DELIVERY FAILURE: No route found to domain no.such.place from server
TEAMWORK5/TEAMWORK. Check DNS configuration.
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
Message-ID: OFC1B93C4D.8A056886-ON85256CCC.00671893-85256CCC.00671BEA@LocalDomain
From: Postmaster%localdomain
Date: Thu, 13 Feb 2003 13:46:29 -0500
X-MIMETrack: Serialize by Notes Client on Bill Ernest/Teamwork(Release 6.0|September 26, 2002) at
02/13/2003 01:46:29 PM,
Serialize complete at 02/13/2003 01:46:29 PM
Content-Type: multipart/report; report-type=delivery-status; boundary=“==IFJRGLKFGIR64078UHRUHIHD”

–==IFJRGLKFGIR64078UHRUHIHD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

WW91ciBtZXNzYWdlDQoNCiAgU3ViamVjdDogVGVzdA0KDQp3YXMgbm90IGRlbGl2ZXJlZCB0bzoN
Cg0KICBub3N1Y2hVc2VyQG5vLnN1Y2gucGxhY2UNCg0KYmVjYXVzZToNCg0KICBObyByb3V0ZSBm
b3VuZCB0byBkb21haW4gbm8uc3VjaC5wbGFjZSBmcm9tIHNlcnZlciBURUFNV09SSzUvVEVBTVdP
UksuICBDaGVjayBETlMgY29uZmlndXJhdGlvbi4NCg0K

–==IFJRGLKFGIR64078UHRUHIHD
Content-Type: message/delivery-status

Reporting-MTA: dns;teamwork5.teamsol.com

Final-Recipient: rfc822;nosuchUser@no.such.place
Action: failed
Status: 5.1.2
Diagnostic-Code: X-Notes; No route found to domain no.such.place from server TEAMWORK5/TEAMWORK. Check DNS configuration.

–==IFJRGLKFGIR64078UHRUHIHD
Content-Type: message/rfc822

To: nosuchUser@no.such.place
Subject: Test
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
Message-ID: OFC1B93C4D.8A056886-ON85256CCC.00671893-85256CCC.00671BEA@LocalDomain
From: bigbill@teamsol.com
Date: Thu, 13 Feb 2003 13:46:29 -0500
X-MIMETrack: Serialize by Notes Client on Bill Ernest/Teamwork(Release 6.0|September 26, 2002) at
02/13/2003 01:46:29 PM,
Serialize complete at 02/13/2003 01:46:29 PM
Content-Type: multipart/alternative; boundary=“=alternative 00671BE985256CCC=”

This is a multipart message in MIME format.
–=alternative 00671BE985256CCC=
Content-Type: text/plain; charset=“US-ASCII”

Test
Bill Ernest, Director of Technical Services
Teamwork Solutions, Inc.

614.457.7100 x206
614.457.8200 (fax)

bigbill@teamsol.com
www.teamsol.com
www.notesworkflow.com

–=alternative 00671BE985256CCC=
Content-Type: text/html; charset=“US-ASCII”


Test


Bill Ernest, Director of Technical Services
Teamwork Solutions, Inc.


614.457.7100 x206
614.457.8200 (fax)

bigbill@teamsol.com
www.teamsol.com
www.notesworkflow.com
--=_alternative 00671BE985256CCC_=--

–==IFJRGLKFGIR64078UHRUHIHD–