I'm not sure I undestand this. Doesn't CF merely pass off the messages to
the SMTP server for relaying? Same as if they had come from an email
client such as Outlook Express? Is it the mass-assault on the SMTP server
that causes messages to be immediately sent to the undeliv folder? In my
experience the immediate return to the sender would only be caused by
things like a domain that can't be resolved, or else the domain has no
mail exchanger in DNS, or else the destination mail server rejects the
imcoming message for some reason, like the email address is invalid, the
mailbox has exceeded its size quota, or the sender domain or IP address
has been rejected. In most other cases, the outgoing SMTP server will
hold the message and attempt to send it for (usually) several days. Are
there other reasons why CF, as a sending client would see more rejections
than another client? If the 'undeliver' messages are placed there for a
good reason, then it wouldn't make much sense trying to send them again.
Jim
-----Original Message-----
From: Nick Slay <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, July 05, 2000 11:54 PM
Subject: Re: <CFMAIL>Hundreds of messages left undelivered ... why?
>As far as I understand Mike, the steps you mention are correct. I have
seen
>things sitting in the undeliv folder, and they have never been sent.. so
I'm
>fairly certain that you're 40,000+ messages would never have been sent.
>
>If you want to actually send them, you can copy them back to the Spool
>folder, however this poses the question as to why they weren't sent,
which I
>guess you've figured... If it was that the mail server was unavailable
at
>the time, then they should be delivered if you drop them into the spool
>folder.. but if it's a relaying error, ie, the domain of the senders
address
>does not equal that of the email server, then they would never be
delivered.
>
>Hope that helps a little
>
>Nick
>
>
>> From: Michael Kear <[EMAIL PROTECTED]>
>> Reply-To: [EMAIL PROTECTED]
>> Date: Thu, 6 Jul 2000 13:01:43 +1000 (EST)
>> To: [EMAIL PROTECTED]
>> Subject: <CFMAIL>Hundreds of messages left undelivered ... why?
>>
>> Yesterday, I did a dumb thing and got into a nasty pickle with my email
>> newsletter. I'm really grateful to Nick Slay for coming rapidly to my
>> rescue with the solution.
>>
>> Now I find there's another potential problem ..... there were 40,920
>> undelivered messages left on my server after I rebooted it, all with a
>> file name like CFMnnnn.TMP. As it happens, this was a blessing in this
>> case, or else there would have been 40,920 messages incorrectly
delivered
>> to my users. And they'd have been even more irate than they were.
>>
>> But what about all those undelivered messages?
>>
>> Would they have ever been sent? If I had wanted them to be sent, how
>> would I do that?
>>
>> Is this folder C:\CFUSION\MAIL\UNDELIVR (Assuming a default
installation)
>> a holding pen for messages that are to be delivered? If not, what
exactly
>> is the process?
>>
>> Here's how I am guessing it works .. can someone confirm this please?
>>
>> (1) The CF server performs the query and other processing to compile
each
>> email.
>> (2) Each email is in a file of its own called CFMnnnn.TMP and is
dropped
>> into C:\CFUSION\MAIL\SPOOL
>> (3) The SMTP server looks there regularly and takes any files and
>> sends them.
>> (4) If there is an error, the SMTP server writes a record to
>> C:\CFUSION\MAIL\LOGS\ERRORS.LOG then moves the error email to
>> C:\CFUSION\MAIL\UNDELIVR
>> (5) Once a message gets to C:\CFUSION\MAIL\UNDELIVR it sits there until
>> manual intervention fixes it.
>>
>> Is this right?
>>
>> Cheers,
>> Mike Kear
>> AFP Web Development
>> Windsor, NSW, Australia
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
