The mailing list for listmasters using Sympa

["Allen, Pat" <address@concealed>]

Thank you, Serge, for your suggestions. You pointed me in the right direction 
and I was able to figure out what was going on. The problem turned out to be 
me (of course). I am getting ready to migrate our production Lyris list 
server to Sympa and wanted to make sure that everything is working OK. I only 
have a few lists with a few items in the archives on the Sympa server. (We 
will be migrating all the archives over later.) So, in testing the 
functionality of the "Send it back" button, I would try to send the same 
archived message to myself more than once. This ran into the duplicate 
detection logic of the Exchange server which is not very well documented. I 
was able to find a good explanation of it at the Exchange Team Blog at 
http://msexchangeteam.com/archive/2004/07/14/183132.aspx. Essentially, the 
server will drop the message if the Internet Message ID is the same and it is 
submitted within the same hour. It appears that the Message ID which is used 
is always the Message ID of the original archived message so clicking the 
button more than once will cause subsequent messages to be dropped into the 
bit bucket.

Thanks for the help in figuring this out.
Pat

-----Original Message-----
From: Allen, Pat [mailto:address@concealed] 
Sent: Monday, March 17, 2008 12:01 PM
To: address@concealed
Subject: RE: [sympa-users] Send it back button behavior - More info & 
questions

I've logged the traffic going from the Sympa server to the Exchange server 
and everything looks like it should be OK. And, surprisingly, a couple of 
messages actually did show up later which made me think that things were 
working but only a couple did and then they stopped. The ones that came 
through had the original sender's "From" address instead of 
address@concealed and the date was the original date rather than 
the date when I asked for the message to be resent. Is this the way that the 
"Send it back" button is supposed to work? Are the conflicting message 
headers confusing Exchange? Is there any way to suppress the original routing 
message headers and just send back selected headers and the body?

Thanks,
Pat

-----Original Message-----
From: Allen, Pat [mailto:address@concealed] 
Sent: Monday, March 17, 2008 10:30 AM
To: address@concealed
Subject: [sympa-users] Send it back button behavior

Hi there -

I'm having some very strange behavior and I'm wondering if anybody has seen 
this before. I'm running Sympa 5.3.4 with virtual hosts. (I only mention the 
virtual hosts because I'm not sure if that may be contributing to the 
problem.) I'm using sendmail 8.13.8 connecting to an Exchange server as a 
smart host. I'm also using CNAME's to connect to the server; the physical 
name of the server is tundra.shore.mbari.org but the virtual host is 
listserver4.mbari.org.

When I send a new mail message to one of the lists, the message is delivered 
immediately (or close enough). When I use the web interface to post a 
message, it is delivered immediately. The same is true if I go to the 
archives, select a message and select the "reply to sender" or "reply to 
list". Delivery of the messages are OK. So far everything is working great.

The only problem that I'm having is when I select a message in the archive 
and hit the "send it back to me" button. If I watch my sendmail log, I see an 
entry saying that a message is being sent to the Exchange server but I never 
see it  in the Exchange tracking logs. Here are the sendmail messages which 
get generated when I click the button. Tundra.shore.mbari.org is the Sympa 
server and snow.shore.mbari.org is our front-end Exchange server.

Mar 17 10:12:27 tundra sendmail[10314]: m2HHCRDi010314: 
Authentication-Warning: tundra.shore.mbari.org: sympa set sender to 
address@concealed using -f
Mar 17 10:12:28 tundra sendmail[10314]: m2HHCRDi010314: 
address@concealed, size=831, class=0, nrcpts=1, 
msgid=<address@concealed>, 
relay=sympa@localhost
Mar 17 10:12:28 tundra sendmail[10315]: m2HHCSb4010315: 
from=<address@concealed>, size=1091, class=0, nrcpts=1, 
msgid=<address@concealed>, proto=ESMTP, 
daemon=MTA, relay=localhost.localdomain [127.0.0.1]
Mar 17 10:12:28 tundra sendmail[10314]: m2HHCRDi010314: address@concealed, 
address@concealed (10001/10001), delay=00:00:01, 
xdelay=00:00:00, mailer=relay, pri=30831, relay=[127.0.0.1] [127.0.0.1], 
dsn=2.0.0, stat=Sent (m2HHCSb4010315 Message accepted for delivery)
Mar 17 10:12:28 tundra sendmail[10317]: m2HHCSb4010315: to=<address@concealed>, 
delay=00:00:00, xdelay=00:00:00, mailer=smtp, pri=121091, 
relay=snow.shore.mbari.org. [134.89.12.65], dsn=2.0.0, stat=Sent (2.6.0  
<address@concealed> Queued mail for delivery)

Has anyone seen this before?

Thanks!
Pat