perlbug and Resent-To: lines

[p5pRT]

Migrated from rt.perl.org#2679 (status was 'resolved')

Searchable as RT2679$

[p5pRT]

From gnat@frii.com

Tom Christiansen writes​:

I tried both resending (which appeared not to work) and forwarding (which did appear to work).

I guess the bugtron looks at the To and CC headers\, but not Resent-To. I guess this is a bug.

It also rejected my first attempt at this message because it didn't contain "perl". Maybe all mail coming *from* the p5p subscribers should be allowed\, regardless of "perl" presence? Hmm\, then the bugtron has to maintain a list of subscribers. Such information doesn't seem easily accessible with the new mailing list software.

Nat

[p5pRT]

From [Unknown Contact. See original ticket]

In message \14555\.37998\.180633\.66430@​prometheus\.frii\.com   Nathan Torkington \gnat@​frii\.com wrote​:

Tom Christiansen writes​:

I tried both resending (which appeared not to work) and forwarding (which did appear to work).

I guess the bugtron looks at the To and CC headers\, but not Resent-To. I guess this is a bug.

Why does it need to look at any of them? Surely the MTA uses the envelope recipient address to invoke the appropriate script and what's in the headers shouldn't matter.

In case you're wondering I encountered the same problem when I tried bouncing a message to perlbug only to have to give up waiting for it to appear and forward it instead.

I didn't even get a bounce message - surely if it's not going to do what I want it should at least tell me.

Tom

-- Tom Hughes (tom@​compton.nu) http​://www.compton.nu/ ...ERROR #1511​: Brain Offline

[p5pRT]

From [Unknown Contact. See original ticket]

I didn't even get a bounce message - surely if it's not going to do what I want it should at least tell me.

Yes\, it should never drop something without notifying someone.

I find it ironic that it sends out duplicate message IDs\, yet does not tolerate them itself.

--tom

[p5pRT]

From [Unknown Contact. See original ticket]

Tom Christiansen wrote​:

I didn't even get a bounce message - surely if it's not going to do what I want it should at least tell me. You should get a bounce message.

Yes\, it should never drop something without notifying someone. The only time it does that is when it appears to come from itself\, (ie; anti-loop).

I find it ironic that it sends out duplicate message IDs\, yet does not tolerate them itself. There's a new version going in as we speak. As per my earlier mails\, I wanted to wait until the release was out of the way before modifying anything.

Ciao Richard Foley

---

richard@​rfi.net 'Ciao' - shorter than 'Aufwiedersehen'