Okay, I'll clarify a little.

I'm not currently using qmailanalog, so I'll try to do it in words.

[EMAIL PROTECTED] produced a bounce due to:
<[EMAIL PROTECTED]>:
195.41.46.148 does not like recipient.

This bounce was supposed to be sent to [EMAIL PROTECTED] (uid
1014), but was instead sent to
[EMAIL PROTECTED], a message which
was accepted by [EMAIL PROTECTED] (uid 1044) and forwarded to
[EMAIL PROTECTED]

The events, as I interpret them, were as follows (in some sort of
meta-language):

1.) Mail is sent with following instructions
From: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>

2.) qmail delivers the messages separate from eachother (delivery 2349 &
2350, msg 539092)

3.) qmail reports a failure for delivery 2349, and sends a bounce (delivery
2351, msg 539093)

4.) qmail reports a failure for delivery 2350 (also msg 539092)

Here is the interesting part..

5.) qmail begins a new msg with id 539092 (there has not yet been a second
bounce for that mail, only a second report of failure,) delivery 2352

6.) qmail carries out delivery 2352 successfully, and begins the forward to
[EMAIL PROTECTED] (delivery 2353)

7.) qmail starts a bounce for msg 539092, although delivery 2352 has been
carried out successfully. It bounces the message delivered by delivery 2350,
but to the wrong adress.
It should have bounced to [EMAIL PROTECTED] but bounced to
[EMAIL PROTECTED]

I've marked out the different events in the attached log-file.

I hope this is clearer, otherwise I guess I'll have to install qmailanalog.

Thanks, Henrik.

Dave Sill wrote:

> Henrik =?iso-8859-1?Q?=D6hman?= <[EMAIL PROTECTED]> wrote:
>
> >I checked the logs..
>
> I can't make sense out these with the funky line wrapping, and without
> knowing more about your system (e.g., who are UID's 21 and 1044, and
> how is mail to henrik.ohman handled?). Try running "matchup" from
> qmailanalog to produce easier-to-read log entries.
>
> >Hey, wait a moment. The bounce came _after_ the inode had been assigned
> >to a new msg?
> >Uhh, is this normal? Did something fuck up, and in that case, was it
> >qmail or the MUA?
> >Could this have happened before, or was it a one-timer?
>
> I can't really say, since I can't tell what happened, but I can't see
> that anything unusual happened. Other than the symptoms you see in the
> logs, what happened that you don't think should have happened, or
> didn't happen that you think should have happened?
>
> -Dave
## 1.)
Feb  4 11:44:01 gammalinux qmail: 949661041.678271 new msg 539092
Feb  4 11:44:01 gammalinux qmail: 949661041.678902 info msg 539092: bytes 8458 f
rom <[EMAIL PROTECTED]> qp 32082 uid 21

## 2.)
Feb  4 11:44:01 gammalinux qmail: 949661041.681663 starting delivery 2349: msg 5
39092 to remote [EMAIL PROTECTED]
Feb  4 11:44:04 gammalinux qmail: 949661044.681268 starting delivery 2350: msg 5
39092 to remote [EMAIL PROTECTED]

## 3.)
Feb  4 11:44:05 gammalinux qmail: 949661045.751848 delivery 2349: failure: 195.4
1.46.148_does_not_like_recipient./Remote_host_said:_550_Invalid_recipient:_
Giving_up_on_195.41.46.148./
Feb  4 11:44:05 gammalinux qmail: 949661045.763374 bounce msg 539092 qp 32085
Feb  4 11:44:05 gammalinux qmail: 949661045.764177 end msg 539092
Feb  4 11:44:05 gammalinux qmail: 949661045.765228 new msg 539093
Feb  4 11:44:05 gammalinux qmail: 949661045.766079 info msg 539093: bytes 9108 f
rom <> qp 32085 uid 26
Feb  4 11:44:05 gammalinux qmail: 949661045.769127 starting delivery 2351: msg 5
39093 to local [EMAIL PROTECTED]
Feb  4 11:44:05 gammalinux qmail: 949661045.787893 delivery 2351: success: did_1
+0+0/

## 4.)
Feb  4 11:44:08 gammalinux qmail: 949661048.674722 delivery 2350: failure: 195.4
1.46.148_does_not_like_recipient./Remote_host_said:_550_Invalid_recipient:_<sect
[EMAIL PROTECTED]>/Giving_up_on_195.41.46.148./

## 5.)
Feb  4 11:44:21 gammalinux qmail: 949661061.154927 new msg 539092
Feb  4 11:44:21 gammalinux qmail: 949661061.155801 info msg 539092: bytes 1737 f
rom <[EMAIL PROTECTED]> qp 32092 uid 21
Feb  4 11:44:21 gammalinux qmail: 949661061.159059 starting delivery 2352: msg 5
39092 to local [EMAIL PROTECTED]

## 6.)
Feb  4 11:44:21 gammalinux qmail: 949661061.179819 new msg 539093
Feb  4 11:44:21 gammalinux qmail: 949661061.180866 info msg 539093: bytes 1848 f
rom <[EMAIL PROTECTED]> qp 32095 uid 10
44
Feb  4 11:44:21 gammalinux qmail: 949661061.184363 starting delivery 2353: msg 5
39093 to local [EMAIL PROTECTED]
Feb  4 11:44:21 gammalinux qmail: 949661061.186468 delivery 2352: success: did_0
+1+0/qp_32095/

## 7.) 
Feb  4 11:44:21 gammalinux qmail: 949661061.196002 bounce msg 539092 qp 32097
Feb  4 11:44:21 gammalinux qmail: 949661061.196804 end msg 539092
Feb  4 11:44:21 gammalinux qmail: 949661061.198004 new msg 539094
Feb  4 11:44:21 gammalinux qmail: 949661061.198872 info msg 539094: bytes 2447 f
rom <> qp 32097 uid 26
Feb  4 11:44:21 gammalinux qmail: 949661061.202550 starting delivery 2354: msg 5
39094 to remote [EMAIL PROTECTED]
Feb  4 11:44:21 gammalinux qmail: 949661061.224028 delivery 2353: success: did_1
+0+0/
Feb  4 11:44:21 gammalinux qmail: 949661061.225800 end msg 539093
Feb  4 11:44:29 gammalinux qmail: 949661069.445899 delivery 2354: success: 131.1
93.178.181_accepted_message./Remote_host_said:_250_ok_949661062_qp_27142/

Reply via email to