Please do not obfuscate with problems like this one, we cannot try out
if you obfuscate, and most people here don't have a barracuda 400 on hand.
http://www.exim.org/eximwiki/MailingListEtiquette
thanks
B. Cook wrote:
> Hello all,
>
> In having a problem with someone running a baraccuda 400 appliance..
>
> The problem is that his logs show he never took the mail from us and we
> 'Aborted', my exim logs (and the debug pasted below) show he took the
> message and then (seeminly) trashed it b/c we didn't wait around for his
> OK to our QUIT.
>
>
> I then sent an email to the queue and debugged it being sent and found
> this: (exim -v -d -M 1G0N4G-0007Ph-9L)
>
> ...
> SMTP<< 250 Ok: queued as A2867519F3
> journalling name@???
> ok=1 send_quit=1 send_rset=0 continue_more=0 yield=0 first_address is NULL
> no messages waiting for 64.x.241.y
> SMTP>> QUIT
> set_process_info: 58372 delivering 1G0N4G-0007Ph-9L: just tried
> 64.x.241.y [64.x.241.y] for name@???: result OK
> LOG: MAIN
> ...
>
> His appliance is showing that I have aborted and even though it issued
> an OK does not show my message. He needs to take screenshots of his
> appliance to show me logs.. but it says this:
>
> Time Received:
> From:
> To:
> Action: Aborted
> Reason: Sender Quit
> Score:
> Source IP:
> Delivery Status:
> Delivery Detail:
>
> I think that it is wrong that this appliance said OK and then deleted
> the message because we didn't wait around for them to issue an OK to our
> QUIT.. is there some setting that I might have set that is 'breaking' this?
>
> Or is this device just this way?
>
--
Nikademus
http://www.octools.com
.O.
..O
OOO
PGP key:
http://www.llorien.org/gnupg/key.pub
