my_hdr Message-ID doesn't work

Hey guys,

I'm back again looking for help on this project I'm working on. I'm
generating custom Message-IDs by using my_hdr to call a script that
results in the string "my_hdr Message-ID: <blahblah@blah>".

This works fine on a linux system, but on Mac OS it refuses to work. If
I change "Message-ID" to "MMessage-ID" it works fine, but it's somehow
"colliding" with the true string Message-ID.

Any suggestions?

Also, any comments on how much of a bad idea it is to give a message a
custom ID?

Mike

* Mike Hunter is quoted & my replies are inline below :
> Hey guys,
>
> I'm back again looking for help on this project I'm working on. I'm
> generating custom Message-IDs by using my_hdr to call a script that
> results in the string "my_hdr Message-ID: <blahblah@blah>".
>
> This works fine on a linux system, but on Mac OS it refuses to work. If
> I change "Message-ID" to "MMessage-ID" it works fine, but it's somehow
> "colliding" with the true string Message-ID.

Sorry mate. I don't know Mac, but I use the following for linux.

send-hook . 'my_hdr Message-ID:<`date +"%Y%m%d%H%M%S"`@usenet.piggo.com>'

Note I have no space between "M-ID:" and the "<". This was due
to a bug on a previous version of mutt. Not sure if it is fixed
in 1.5.15 or 1.5.16. Mutt (and mutt-ng) inserted an extra space
in there. Refer
http://groups.google.com/group/news....bb6618dca426ab

Don't know if your MMessage-ID is related or not.

> Any suggestions?
>
> Also, any comments on how much of a bad idea it is to give a message a
> custom ID?

It's fine as long as it's unique.

--
Troy Piggins | http://piggo.com/~troy _ /|/
RLU#415538 |\__/ Oo, ,-O (o- O
( \\ D O ) //\ O
Mutt 1.5.15 (rr.compressed & vvv.nntp patches) L\-\L`\/| `-O V_/_ OOO

On Fri, 15 Jun 2007 11:56:07 +1000, Troy Piggins wrote:
> * Mike Hunter is quoted & my replies are inline below :
> > Hey guys,
> >
> > I'm back again looking for help on this project I'm working on. I'm
> > generating custom Message-IDs by using my_hdr to call a script that
> > results in the string "my_hdr Message-ID: <blahblah@blah>".
> >
> > This works fine on a linux system, but on Mac OS it refuses to work. If
> > I change "Message-ID" to "MMessage-ID" it works fine, but it's somehow
> > "colliding" with the true string Message-ID.
>
> Sorry mate. I don't know Mac, but I use the following for linux.

I may have to switch do doing it on linux....

> send-hook . 'my_hdr Message-ID:<`date +"%Y%m%d%H%M%S"`@usenet.piggo.com>'
>
> Note I have no space between "M-ID:" and the "<". This was due
> to a bug on a previous version of mutt. Not sure if it is fixed
> in 1.5.15 or 1.5.16. Mutt (and mutt-ng) inserted an extra space
> in there. Refer
> http://groups.google.com/group/news....bb6618dca426ab

Thanks! I had wondered if I was going crazy or what Unfortunately
that didn't solve my problem.

> Don't know if your MMessage-ID is related or not.
>
> > Any suggestions?
> >
> > Also, any comments on how much of a bad idea it is to give a message a
> > custom ID?
>
> It's fine as long as it's unique.

That's what I'd understood. Thanks again!

Mike
>

* Mike Hunter is quoted & my replies are inline below :
> On Fri, 15 Jun 2007 11:56:07 +1000, Troy Piggins wrote:
>> * Mike Hunter is quoted & my replies are inline below :
>> >
>> > I'm back again looking for help on this project I'm working on. I'm
>> > generating custom Message-IDs by using my_hdr to call a script that
>> > results in the string "my_hdr Message-ID: <blahblah@blah>".
>> >
>> > This works fine on a linux system, but on Mac OS it refuses to work. If
>> > I change "Message-ID" to "MMessage-ID" it works fine, but it's somehow
>> > "colliding" with the true string Message-ID.
>>
>> Sorry mate. I don't know Mac, but I use the following for linux.
>
> I may have to switch do doing it on linux...

Have you tried making it simpler to see if it's the invokation
of the script or the setting of a custom M-ID that's causing the
problem?

To clarify, I would try this:

send-hook . 'my_hdr Message-ID:<1234567890xyz@usenet.piggo.com>'

with the username part of the M-ID some unique value, but
fixed/typed. Not created by a script. If that works, we know
it's the script somehow causing problems. If it doesn't work, we
know it's the custom M-ID causing the problem in Mac.

If it does work, the next step I'd try to see how the script is
mucking it up. Instead of using your script, try a simple
built-in command like 'date' as I do.

See how that goes.

>> send-hook . 'my_hdr Message-ID:<`date +"%Y%m%d%H%M%S"`@usenet.piggo.com>'
>>
>> Note I have no space between "M-ID:" and the "<". This was due
>> to a bug on a previous version of mutt. Not sure if it is fixed
>> in 1.5.15 or 1.5.16. Mutt (and mutt-ng) inserted an extra space
>> in there. Refer
>> http://groups.google.com/group/news....bb6618dca426ab
>
> Thanks! I had wondered if I was going crazy or what Unfortunately
> that didn't solve my problem.



>> Don't know if your MMessage-ID is related or not.
>>
>> > Any suggestions?
>> >
>> > Also, any comments on how much of a bad idea it is to give a message a
>> > custom ID?
>>
>> It's fine as long as it's unique.
>
> That's what I'd understood. Thanks again!

NP.

--
Troy Piggins | http://piggo.com/~troy _ /|/
RLU#415538 |\__/ Oo, ,-O (o- O
( \\ D O ) //\ O
Mutt 1.5.15 (rr.compressed & vvv.nntp patches) L\-\L`\/| `-O V_/_ OOO

On Fri, 15 Jun 2007 12:44:26 +1000, Troy Piggins wrote:
>
> Have you tried making it simpler to see if it's the invokation
> of the script or the setting of a custom M-ID that's causing the
> problem?
>
> To clarify, I would try this:
>
> send-hook . 'my_hdr Message-ID:<1234567890xyz@usenet.piggo.com>'
>
> with the username part of the M-ID some unique value, but
> fixed/typed. Not created by a script. If that works, we know
> it's the script somehow causing problems. If it doesn't work, we
> know it's the custom M-ID causing the problem in Mac.
>
> If it does work, the next step I'd try to see how the script is
> mucking it up. Instead of using your script, try a simple
> built-in command like 'date' as I do.
>
> See how that goes.

Thanks for the suggestion. I did try what you suggested above and
confirmed that that *doesn't* work, so it's something with mutt and not
something with my script. The strange part is that when I edit full
headers with "E" and *type* in a Message-ID, it accepts it and I see the
resulting ID on the remote end. And I don't have the problem at all on
linux. Very strange.

Mike

* Mike Hunter is quoted & my replies are inline below :
> On Fri, 15 Jun 2007 12:44:26 +1000, Troy Piggins wrote:
>>
>> Have you tried making it simpler to see if it's the invokation
>> of the script or the setting of a custom M-ID that's causing the
>> problem?
>>
>> To clarify, I would try this:
>>
>> send-hook . 'my_hdr Message-ID:<1234567890xyz@usenet.piggo.com>'
>>
>> with the username part of the M-ID some unique value, but
>> fixed/typed. Not created by a script. If that works, we know
>> it's the script somehow causing problems. If it doesn't work, we
>> know it's the custom M-ID causing the problem in Mac.
>>
>> If it does work, the next step I'd try to see how the script is
>> mucking it up. Instead of using your script, try a simple
>> built-in command like 'date' as I do.
>>
>> See how that goes.
>
> Thanks for the suggestion. I did try what you suggested above and
> confirmed that that *doesn't* work, so it's something with mutt and not
> something with my script. The strange part is that when I edit full
> headers with "E" and *type* in a Message-ID, it accepts it and I see the
> resulting ID on the remote end. And I don't have the problem at all on
> linux. Very strange.

Bugger. Sorry I can't help you further. Mac is not something
I'm familiar with.

--
Troy Piggins | http://piggo.com/~troy _ /|/
RLU#415538 |\__/ Oo, ,-O (o- O
( \\ D O ) //\ O
Mutt 1.5.15 (rr.compressed & vvv.nntp patches) L\-\L`\/| `-O V_/_ OOO