Closed Bug 994977 Opened 11 years ago Closed 11 years ago

[B2G] [Email] [POP3] AOL.com accounts are unable to send emails

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.3 affected, b2g-v1.3T affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v1.3 --- affected
b2g-v1.3T --- affected

People

(Reporter: ckreinbring, Unassigned)

Details

(Whiteboard: 1.3tarakorun2)

Attachments

(3 files)

Attached file firewatch.txt
Description: The user is unable to send emails to other accounts from a POP3 account. Repro Steps: 1) Update Tarako to Build ID: 20140402164004 2) Launch Email and log in with a POP3 account (eg an AOL account). 3) Tap the new email icon and enter a valid address, subject and body text. 4) Tap the Send icon and observe the device's reaction. Actual: An error message appears stating "Sending email failed". Expected: The email is sent to the destination account with no errors. Environmental Variables Build ID: 20140409004001 Gecko: e757fdd55426 Gaia: 643f3e6676cbb89c62708a9f7cbef2edc795a552 Base Image: sp8810 Notes: Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/cases/?filter-id=10893 See attached screenshot and firewatch logs
Hi, thanks for the report. Can you please provide a logcat per the instructions at the following link? https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo
Also repros on Buri 1.3 mozilla RIL Build ID: 20140409164003 Gecko: https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/82e5ff16645a Gaia: 62acb4b0e774b6709b8be400d849f807404bb21b Platform Version: 28.0 Firmware Version: V1.2-device.cfg
Can you be specific about what email provider you are using here? Does this reproduce with other POP3 email providers?
Flags: needinfo?(ckreinbring)
When I first wrote the bug, the account used was from AOL.com. However, accounts from fastmail.fm, gmail.com and outlook.com are able to send emails with no errors. I've updated the bug title to reflect this.
Flags: needinfo?(ckreinbring)
Summary: [B2G] [Email] [POP3] Unable to send emails → [B2G] [Email] [POP3] AOL.com accounts are unable to send emails
When you entered the username in the configuration fields, did you use the full e-mail including "@aol.com" or just the username? AOL's mail server may only work if you include the "@aol.com" per their instructions.
Flags: needinfo?(ckreinbring)
The full email name was used.
Flags: needinfo?(ckreinbring)
Andrew - Can you weigh in on the severity of this bug? Why are we failing to send emails here?
Flags: needinfo?(bugmail)
I am able to send email messages with a configured AOL.com POP3 account on both trunk on b2g-desktop and on v1.3T on a Tarako device. It sounds like the problem here is either AOL thinks ckreinbring is a spammer or some other heuristic is preventing the send. http://help.aol.com/help/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=95666 indicates that if you put "AOL" in your display name it thinks you are trying to phish people and forbids the send. It also might be synchronously trying to send the message and passing through the SMTP error codes; for example http://help.aol.com/help/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=91671 suggests that if the recipient has marked you as a spammer, AOL will reject it for you right there. We already have it in our background-sending enhancement to improve the error code situation, so I don't think there's any further work here other than a new AOL test account may need to be acquired or care needs to be taken in choosing the display name when creating the account.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(bugmail)
Resolution: --- → WORKSFORME
The email that was used has a display name of "Ffos Qa" and an address of ffos.qa@aol.com. I was also able to send mail to the account. I just made another AOL account and was able to send mail from it on the device.
Resolution: WORKSFORME → FIXED
(WORKSFORME or INVALID is still most appropriate since we didn't actually fix anything in the code; this was apparently just an account-specific testing issue. This lets us search on FIXED bugs to find things addressed in the code.)
Resolution: FIXED → WORKSFORME
I have no idea how that happened. It was an accident.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: