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

Yuji Shinozaki yuji at virginia.edu
Thu Apr 23 07:25:04 PDT 2009


Like Stephen, we had gotten similar advice from our local mail  
admins:  always use an A record for your mail domain and MX records to  
direct the mail traffic as needed.

yuji
----

On Apr 23, 2009, at 10:14 AM, Stephen Marquard wrote:

> You shouldn't use a CNAME for the primary hostname of a mail domain  
> - rather use explicit A and MX records in your DNS.
>
> Some MTAs regard CNAMEs as aliases that should be resolved for mail  
> purposes (i.e. putting in the FQDN of the target) - I can't remember  
> the exact details but did investigate this a while back when we had  
> a similar configuration, and the solution was to change the DNS setup.
>
> Regards
> Stephen
>
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za
> Email/IM/XMPP: stephen.marquard at uct.ac.za
> Phone: +27-21-650-5037 Cell: +27-83-500-5290
>
>
>>>> "Adams, David" <da1 at vt.edu> 2009/04/23 04:07 PM >>>
> 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
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"

-----
Yuji Shinozaki
Sr. Technical Lead/Project Manager
University of Virginia
Advanced Technologies Group
ys2n at virginia.edu
-----
"Computers are useless.  They only give you answers". --Pablo Picasso








More information about the sakai-dev mailing list