Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

How to Change the Default "Outbox" from Local Folders to my Default Account?

  • 3 risposte
  • 1 ha questo problema
  • 3 visualizzazioni
  • Ultima risposta di Matt

more options

For a long time my default account used the "Special" Local Folders account for incoming and outgoing mail. (This was because when I created the account in TBird, in server settings for POP3, there was no option for using "default account:Sent" etc. in the Account Settings, Copies & Folders pane. Now that I (finally) figured out how to get TBird to create the default "Sent" and "Outbox" for the account, and to target them for "normal operation" I cannot get it to use an account-based "Outbox" for send-later mail. Instead it always puts the mail in the Local Folders:Outbox. I even tried changing the config editor entry:

mail.default_sendlater_uri mailbox://nobody@Local%20Folders/Unsent%20Messages

to my local account like:

mail.default_sendlater_uri mailbox://nobody@My%AcccountName/Unsent%20Messages

which changed nothing - send later messages still went to Local Folders:Outbox.

Is there a way to get "Send Later" to drop the mail into "My AccountName:Outbox?

For a long time my default account used the "Special" Local Folders account for incoming and outgoing mail. (This was because when I created the account in TBird, in server settings for POP3, there was no option for using "default account:Sent" etc. in the Account Settings, Copies & Folders pane. Now that I (finally) figured out how to get TBird to create the default "Sent" and "Outbox" for the account, and to target them for "normal operation" I cannot get it to use an account-based "Outbox" for send-later mail. Instead it always puts the mail in the Local Folders:Outbox. I even tried changing the config editor entry: mail.default_sendlater_uri mailbox://nobody@Local%20Folders/Unsent%20Messages to my local account like: mail.default_sendlater_uri mailbox://nobody@My%AcccountName/Unsent%20Messages which changed nothing - send later messages still went to Local Folders:Outbox. Is there a way to get "Send Later" to drop the mail into "My AccountName:Outbox?

Tutte le risposte (3)

more options

wmcole said

For a long time my default account used the "Special" Local Folders account for incoming and outgoing mail. (This was because when I created the account in TBird, in server settings for POP3, there was no option for using "default account:Sent" etc. in the Account Settings, Copies & Folders pane. Now that I (finally) figured out how to get TBird to create the default "Sent" and "Outbox" for the account, and to target them for "normal operation" I cannot get it to use an account-based "Outbox" for send-later mail. Instead it always puts the mail in the Local Folders:Outbox. I even tried changing the config editor entry: mail.default_sendlater_uri mailbox://nobody@Local%20Folders/Unsent%20Messages to my local account like: mail.default_sendlater_uri mailbox://nobody@My%AcccountName/Unsent%20Messages which changed nothing - send later messages still went to Local Folders:Outbox. Is there a way to get "Send Later" to drop the mail into "My AccountName:Outbox?

Send later is in Local folders. That is not an accident or some sort of strange oddity it is a decision that was made probably 20 years ago in the development team at Netscape.

more options

I get why that decision was made, but I would still like account-based Outboxes like I have account-based Inboxes.

more options

wmcole said

I get why that decision was made, but I would still like account-based Outboxes like I have account-based Inboxes.

And you can not have them. I actually think it would be a major development process to even implement. I am no developer, but I think it would take a dedicated developers several weeks to implement. So I guess we would be talking close to a hundred thousand dollars worth of development, testing and approvals. Not something I would support given there is no functional improvement. Cosmetic change not withstanding.