On Mon, 2018-03-19 at 10:24 -0700, Don Armstrong wrote: > Messages that are signed, have things that look like valid control > commands, etc. are all scored very quickly and usually short-circuit > spam assassin. The delays (if any) should be very short, on the order of > under 3 minutes.
I used the bts command to send the mail so I'm going to assume it was correctly constructed. > On Mon, 19 Mar 2018, Lars Wirzenius wrote: > Could you send me the message-id of the message which was delayed? Even > if you had hit postgrey, and it was tempfailed, it should have only been > delayed by about 5-10 minutes. Usually longer delays indicate that there > is some kind of mail misconfiguration or queuing issue. My smarthost provider confirmed that it was not stuck on their server due to greylisting. The mail was greylisted at 06:58 UTC, but went through at 07:07 UTC. My local time is UTC+2. It thus took 43 minutes to reach the smarthost (I don't know why), but after it got to bugs.debian.org, it took about 5 hours for it be acted on. Because bts doesn't save a copy of the mail anywhere, I don't have a copy of the sent mail, but log files indicate the Message-Id may have been [email protected]. I hope that helps. > I'm actually planning on writing such a thing, but it'll use part of the > mail stack as a queue to process the changes with the appropriate locks > and everything. Cool.
signature.asc
Description: This is a digitally signed message part
