Ticket #1484477 (closed Feature Requests: fixed)

Opened 17 months ago

Last modified 7 months ago

If no reciepient is specified in To field, emails fails even if email addresses in BCC field

Reported by: digby_dude Owned by: till
Priority: 10 - Lowest Milestone: 0.1-stable
Component: Core functionality Version: 0.1-rc1
Severity: minor Keywords: bcc
Cc:

Description

When creating a new mail, I left the TO field blank but placed all my wanted contacts into the BCC field.

When I click on send, I get an error message "Please enter at least one recipient".

I guess the part of the code that checks this, needs to check the cc and bcc fields to, as it it should be possible to send an email only to BCC recepients right?

Thanks,

Adam

Change History

follow-up: ↓ 2   Changed 15 months ago by till

  • status changed from new to assigned
  • severity changed from major to minor
  • priority changed from 4 to 10
  • owner set to till
  • keywords bcc added; BCC only doesn't work removed
  • type changed from Bugs to Feature Requests

Does this work in any client? I am just wondering, because usually people put their own email into the "To" when they BCC.

I wonder what the email RFC says.

in reply to: ↑ 1   Changed 14 months ago by digby_dude

Replying to till:

Does this work in any client? I am just wondering, because usually people put their own email into the "To" when they BCC. I wonder what the email RFC says.

Don't agree that this is a feature request, but a bug, Outlook and Evolution and Pine all let you just specify just BCC reciients, with nothing in the "To" field.

Please change back to a bug.

Thanks,

Adam

  Changed 11 months ago by digby_dude

Please change back to a bug, or at least disagree with my reponse...

Thanks,

Adam

  Changed 10 months ago by till

  • milestone set to 0.1.1

undisclosed-recipients, or something like that. Have to debug and see how it works. In the meantime, as I said, put in your own email as a workaround.

  Changed 10 months ago by thomasb

  • milestone changed from 0.1.1 to 0.1.5

0.1.1 is for bugfixes only

  Changed 9 months ago by thomasb

  • milestone changed from 0.1.5 to 0.1-stable

Implemented in 0.1-stable

  Changed 7 months ago by alec

  • status changed from assigned to closed
  • resolution set to fixed

Closed

Note: See TracTickets for help on using tickets.