[Building Sakai] To field rewritten by email service or something else?

[Adams, David]

After some recent emergency DNS changes, we've discovered that the
mailarchive messages arrive in users' emailboxes with an incorrect 'To'
line, which causes problems when they try to reply to the list.

In particular, our production DNS name is scholar.vt.edu. Up until last
week that name was the A record for a particular IP. Then we moved to a
new IP, where the A record is prod.scholar.edtech.vt.edu and
scholar.vt.edu is a CNAME/alias. However, now, emails sent to, eg,
"CIS101 at scholar.vt.edu" are delivered correctly, but they arrive with a
To: field of "CIS101 at prod.scholar.edtech.vt.edu" which doesn't work for
replies.

So my question is, is Sakai doing this? We've traced the message as far
as we can through the Sakai code and the To header seems to remain
intact up to the point that the message is handed off to the
javax.mail.SMTPTransport. We're working on checking the TCP traffic to
see what Sakai is sending out, but in the meantime I was wondering if I
should be blaming Sakai for this or the outbound SMTP server? Has anyone
experienced this problem before?

Thanks,

David Adams
Director of Learning Systems Integration and Support
Virginia Tech Learning Technologies