Dear postfix people,

I just sent a message I should not have sent, using my local postfix
setup, which forwards to a smarthost for further processing.

After sending the message, I almost immediately pulled the plug, and
looking at mailq, I felt good about that:

  -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
  3DE8FEF5       5142 Tue Feb 16 13:48:14  madd...@lapse.rw.madduck.net
                                           fri...@gmail.com

  -- 5 Kbytes in 1 Request.

So I removed it:

  % sudo postsuper -d 3DE8FEF5
  postsuper: 3DE8FEF5: removed
  postsuper: Deleted: 1 message

and checked mailq, which now reported an empty queue.

I then reconnected, and syslog rewarded me with:

  13:49:51 lapse postfix/smtp[17216]: 3DE8FEF5: to=<fri...@gmail.com>,
  relay=b.mx.madduck.net[2001:41e0:ff43::1]:587, delay=97,
  delays=0.08/0.01/84/13, dsn=2.0.0, status=sent (250 2.0.0 Ok:
  queued as 764981D4099)

Ouch! :(

I realise that I probably connected too quickly and that maybe there
was even an open connection to the smarthost, which didn't timeout
but just resumed (though it was logged >90 seconds after the initial
submission…)

Is there anything I should have done differently, for the next time
this happens? Probably kill the running smtp process, or is there
something else?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
fitter, healthier, more productive
like a pig, in a cage, on antibiotics
                                                          -- radiohead
 
spamtraps: madduck.bo...@madduck.net

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply via email to