Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

QuickBooks email previews in Thuderbird

  • 2 wótegronje
  • 3 maju toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót nixon3

more options

Using Thunderbird 66.0b1 as my default email with QuickBooks Enterprise 2019. About 3 weeks ago an update was installed, prior to the one today, that caused the email preview screen not to appear before sending emails out of QuickBooks. This use to provide an opportunity for me to write a comment in the email body before sending the email. Now they just get sent with no body info and the invoice or purchase order attached. My current work around is to save the PO or invoice as a PDF and then write the email in Thunderbird - which is a slow process.

Using Thunderbird 66.0b1 as my default email with QuickBooks Enterprise 2019. About 3 weeks ago an update was installed, prior to the one today, that caused the email preview screen not to appear before sending emails out of QuickBooks. This use to provide an opportunity for me to write a comment in the email body before sending the email. Now they just get sent with no body info and the invoice or purchase order attached. My current work around is to save the PO or invoice as a PDF and then write the email in Thunderbird - which is a slow process.

Wšykne wótegrona (2)

more options

Maybe do not use beta versions of Thunderbird if you expect the most compatibility. The latest general re!ease is 60.5. The letter b in version numbers indicate beta software.

more options

Thanks for the reply. The problem first occurred with a non beta version. The beta version was installed today to hopefully fix the problem.