qastaging doesn't receive mail

I suspect this will have to become an RT ticket, but let's see what our foundational experts say.

On 3 December 2010 18:05, Jeroen T. Vermeulen <email address hidden> wrote:
> I suspect this will have to become an RT ticket, but let's see what our
> foundational experts say.

I think it will need an RT for DNS configuration, but perhaps more, so
I thought we could discuss it here first.

--
Martin

This is an RT-style task, yes.

Martin started a thread on launchpad-dev ("[rfc] mail into qastaging") about this. Tom Haddon replied that there was a related RT (37768) but that he would appreciate another one about this specific issue. Martin or Jeroen, could you make an RT if one has not already been made, and update this bug with the RT number? Alternately, request Foundations to file the RT.

Thanks

Gary

rt 37768 seems kinda confused; what was ultimately done doesn't seem very closely related to the original request which was that the To addresses not be rewritten.

I filed a new RT 42819 asking for incoming mail to be accepted.

This is now fixed. You'll still need to request a manual run of process-mail.py to actually process the incoming mail, as we don't yet run this cronscript on a schedule for qastaging.

On 21 December 2010 23:35, Tom Haddon <email address hidden> wrote:
> This is now fixed. You'll still need to request a manual run of process-
> mail.py to actually process the incoming mail, as we don't yet run this
> cronscript on a schedule for qastaging.

Thanks very much!

Do you think we could, in a follow on RT, ask for that cronscript to
be run? That would enable people to do qa of incoming-mail-related
features, without them interrupting or blocking on a LOSA. I filed rt
43094 for that.

--
Martin