Open Bug 495623 Opened 15 years ago Updated 2 years ago

.tel integration: send an email to a .tel domain name via dns lookup

Categories

(MailNews Core :: Networking, enhancement)

enhancement

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: spam, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.28 Safari/530.5
Build Identifier: 

It would be great if we could enter a .tel domain name into the To: field of a new email, and have Thunderbird dynamically perform a dns lookup for an email address record at that domain to replace the .tel.

Reproducible: Always




telnic.org have already created a plug-in that integrates .tel with Outlook.
http://dev.telnic.org/pages/winoutlook/landing.html

Lets have native support for .tel in thunderbird.
Not sure if that currently possible Gecko code can only lockup A DNS records.

Wayne, probably this should move to some mailnews core component, what you think?
Component: Mail Window Front End → Composition
Product: Thunderbird → MailNews Core
QA Contact: front-end → composition
(In reply to comment #1)
> Not sure if that currently possible Gecko code can only lockup A DNS records.

Gecko's DNS support is quite low. It all depends on how this thing is working.
Based on http://dev.telnic.org/pages/general_landing.html I don't think it would work with the current necko stack.

I also think this request would be very well suited for an extension.
Component: Composition → Networking
QA Contact: composition → networking
But extension use also Gecko code so again developer will bump against wall. .tel get information from NAPTR, TXT and LOC records.
(In reply to comment #3)
> But extension use also Gecko code so again developer will bump against wall.
> .tel get information from NAPTR, TXT and LOC records.
True. But we are blocked here by mozilla core - I'll try to find the blocker.
There seems no blocker I can find, only mention of its limitation in bug 342242#c15
Depends on: 545866
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.