RFC 5321 (Section 4.5.4.1) dictates the retry and final failure window. It states that for temporary failures, an email server SHOULD retry for at least 4 to 5 days before giving up and sending a final permanent failure notice. It also suggests a retry interval of at least 30 minutes.
-----Original Message----- From: Simon Orebi Gann <[email protected]> Sent: Wednesday, July 01, 2026 11:05 PM To: Derek Atkins <[email protected]> Cc: Murugan Mariappan <[email protected]>; John Ralls <[email protected]>; gnucash-user <[email protected]> Subject: Re: [GNC] User account Email - never a guaranteed delivery so we are probably fortunate it works as often as it does! All my expense accounts were correctly set up; it really was just AP that was wrong. Switching to commodity as the the unit fixed it at once. Must stop kicking myself - I could have fixed this a couple of years ago had I asked [sigh]. Thank you to everyone for such good advice. Simon On 1 Jul 2026, at 09:14, Derek Atkins <[email protected]> wrote: Simon, Glad that you figured it out. Note that once you change this setting you will (most likely) need to re-post your transactions because I suspect they were rounded when posted. As for not seeing my previous email -- it happens. Although not sure why you didn't receive the first one but did see this last one? *shrugs* Happy Gnucashing. -derek On Wed, July 1, 2026 11:52 am, Simon Orebi Gann wrote: > Derek > > This is the first email I have had from you so for some reason the > other one did not reach me (nor spam). > > Thank you - I think you have identified what I have always had that I > must have set up wrongly: the smallest unit is set to 1: > [cid:[email protected]] > > > I did not realise when I set it up quite what that parameter meant > whereas now you mention it, it is obvious. > > I will amend it. > > Kind regards > > Simon > > > On 1 Jul 2026, at 05:48, Derek Atkins <[email protected]> wrote: > > Simon, > > I asked these questions on Monday -- can you please answer them? > > Can you show us the transaction in the A/P account? > Also, what do you have set up as the Commodity SCU in the A/P account > and in the expense account? > Something is clearly rounding the amount to .00, which implies > somewhere you have a commodity or account with a SCU of 1 instead of 1/100. > > Thanks! > > -derek > > On Wed, July 1, 2026 6:24 am, Murugan Mariappan wrote: >> Simon >> >> Can you confirm that the default currency is GBP. Also can you check >> the Numbers, Date, Time in preferences and tell us what is the >> decimal places is showing and as well if the automatic decimal is >> enabled or not >> >> >> >> >> Saludos Cordiales >> >> >> Murugan >> >> ________________________________ >> From: gnucash-user >> <[email protected]> on >> behalf of Simon Orebi Gann <[email protected]> >> Sent: 30 June 2026 04:02 >> To: John Ralls <[email protected]> >> Cc: gnucash-user <[email protected]>; Derek Atkins >> <[email protected]> >> Subject: Re: [GNC] User account >> >> Everything is GBP >> >> Simon >> >> Sent from my tablet >> >> On 29 Jun 2026, at 20:01, John Ralls <[email protected]> wrote: >> >> Is everything in the transaction in GBP or is another currency >> involved? >> >> Regards, >> John Ralls >> >> >> On Jun 29, 2026, at 18:45, Derek Atkins <[email protected]> wrote: >> >> Can you show us the transaction in the A/P account? >> Also, what do you have set up as the Commodity SCU in the A/P account >> and in the expense account? >> Something is clearly rounding the amount to .00, which implies >> somewhere you have a commodity or account with a SCU of 1 instead of >> 1/100. >> >> -derek >> >> On Mon, June 29, 2026 8:52 pm, Simon Orebi Gann wrote: >> John >> >> For family reasons I have been unable to attend to this until now. >> >> Ever since I have started to use gnucash, when I set up an invoice >> and post it - eg this test one: >> [cid:[email protected]] >> >> >> when I come to pay it the amount it defaults to using is always >> rounded, in this case 598.00. I run my business exactly as my >> suppliers expect to be paid exactly ie to the penny. >> >> [cid:[email protected]] >> >> >> If I am directing this to the wrong person, please accept my >> apologies and if you can, let me know to whom I should send it. I >> view it as a mild inconvenience which just rubs a little gloss off an >> otherwise incredible piece of software. >> >> Kind regards >> >> Simon >> >> >> On 5 Dec 2025, at 15:05, John Ralls <[email protected]> wrote: >> >> Simon, >> >> Please copy the list on all replies. You can use “Reply-all” in most >> mailers. >> >> If you’re getting rounded amounts when paying bills then you’ve got a >> sub-optimal way of doing something. Please invent an illustrative >> example. >> >> Regards, >> John Ralls >> >> >> On Dec 5, 2025, at 2:08 PM, Simon Orebi Gann <[email protected]> >> wrote: >> >> John >> >> Thank you for being so helpful. Of course I hope that I find very >> few more bugs in what for the few years I have used it has been a >> rock solid program. >> >> The only thing I would have improved is to allow me to default to >> paying a bill exactly instead of finding the amount has been rounded >> and having to override it. >> >> Given the program has such a huge range of functionality, it is a >> trivial point and I am very impressed overall. After working in >> technology for 35 years and counting, it’s one of the best pieces of >> software I have come across. >> >> Kind regards >> >> Simon >> >> On 4 Dec 2025, at 22:31, John Ralls <[email protected]> wrote: >> >> Simon, >> >> Please always use the mailing lists to contact the GnuCash >> development team unless you’re expressly invited to do otherwise. >> >> I’ve never had much luck with the search bubble in the title bar or >> the simple search tab. Here’s how I do it: >> >> Click search link in the title bar (not the button) and then the >> advanced tab. Click GnuCash in the first box and click one of the >> items and then command-click again in the status box so that nothing >> is selected. In Detailed Bug Information enter “invoice crash” (no >> quotes) in the comment field and select 5.13 in the Version box on >> the lower left. Click either search button. >> >> Regards, >> John Ralls >> >> On Dec 4, 2025, at 1:59 PM, Simon Orebi Gann <[email protected]> >> wrote: >> >> John >> >> Quick follow up. I see that you seem to be the Apple silicon expert, >> so thank you for all that you do. >> >> Quick question: can you tell me a search string which would have >> helped me to find the bug report for this please? I want to ensure >> that in future I only post if I find new bugs, and I struggled to >> find this bug report. >> >> Kind regards >> >> Simon >> >> >> On 4 Dec 2025, at 17:32, John Ralls <[email protected]> wrote: >> >> I’ve created an account on bugs.gnucash.org with this email address >> as the user id. The password is N7UYQ!URgB6j . Please log in and >> change it at your earliest convenience. >> The invoice crash has already been reported and fixed for GnuCash >> 5.14 that will be released in a little over two weeks. >> >> Regards, >> John Ralls >> >> >> On Dec 3, 2025, at 14:53, Simon Orebi Gann <[email protected]> >> wrote: >> >> Please could I have an account to post details of a hard fault in gnu >> cash 5.13-2 running the Mac silicon version on a new MacBook Pro on >> the latest Mac OS. >> >> Whenever I try to pay an invoice, the program exits/crashes. It must >> be an Apple version issue as the same data files work fine if I dig >> my old windows PC out of the museum and run it on there. >> >> I get this report: >> >> >> Gnucash quit unexpectedly. >> >> Click Reopen to open the application again. This report will be sent >> automatically to Apple. >> >> Comments >> >> Problem Details and System Configuration >> >> Translated Report (Full Report Below) >> >> Process: >> >> Path: >> >> Identifier: >> >> Version: >> >> Code Type: >> >> Role: >> >> Parent Process: >> >> Coalition: >> >> User ID: >> >> Gnucash [63611] >> >> /Applications/Gnucash.app/Contents/MacOS/Gnucash >> >> org. gnucash. Gnucash >> >> 5.13-2 (5.13-2) >> >> ARM-64 (Native) >> >> Foreground launchd 1] >> >> org. gnucash.Gnucash [11771] >> >> 501 >> >> Date/Time: >> >> Launch Time: >> >> Hardware Model: >> >> OS Version: >> >> Release Type: >> >> 2025-12-03 22:44:38.8769 +0000 >> >> 2025-12-03 22:42:47.7610 +0000 >> >> Mac15,7 macoS >> >> 26.1 (25B78) >> >> User >> >> Crash Reporter Key: 376AA1C0-BAF9-133A-7CED-CC52BE87A0A1 >> >> Incident Identifier: 54320D23-B4BB-4895-8EAA-A4FEDFA15DF4 >> >> Sleep/Wake UUID: >> >> FC79FA0E-D0C7-4940-A456-C20C79C316BF >> >> Time Awake Since Boot: 180000 seconds >> >> Time Since Wake: >> >> 112634 seconds >> >> System Integrity Protection: enabled >> >> Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread >> >> Exception Type: >> >> EXC_BAD_ACCESS (SIGSEGV) >> >> Exception Subtype: KERN_INVALID_ADDRESS at ØX00000000007730f0 >> >> Exception Codes: >> >> 0X0000000000000001, 0x00000000007730f0 >> >> Termination Reason: Namespace SIGNAL, Code 11, Segmentation fault: 11 >> >> Terminating Process: exc handler [63611] >> >> VM Region Info: 0x7730f0 is not in any region. Bytes before following >> region: 4323774224 >> >> REGION TYPE >> >> START - END >> >> I VSIZE] PRT/MAX SHRMOD REGION DETAIL >> >> UNUSED SPACE AT START >> >> IIIV >> >> _TEXT >> >> 1022ec000-10234c000 >> >> >> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >> >> >> libgtk-3.0.dylib >> >> >> libgnc-gnome.dylib >> >> >> libgobject-z.o.o.dylib >> >> 3 >> >> libgobject-z.o.o.dylib >> >> 4 >> >> libgobject-2.0.o.dylib >> >> >> -- RECURSION LEVEL 12 >> >> 5 >> >> libgtk-3.0.dylib >> >> 6 >> >> libanc-qnome-utils.dylib >> >> | 384K] r-x/r-x SM=COW >> /Applications/Gnucash.app/Contents/MacOS/Gnucash >> >> øx103a7340c gtk_widget_show + 32 >> >> 0x102b00288 gnc_payment_window_check_payment >> >> 0x10300C250 _9_closure. >> >> _invoke_va + 264 >> >> 0x103023f5c signal_emit_valist_unlocked + 1168 >> >> 0x1030246c4 9_signal_emit + 12 >> >> Øx103a51d0c gtk_tree_view_set_model + 1168 >> >> 0x102d7a5c8 qnc_tree view account destroy + 44 >> >> >> Simon >> >> _______________________________________________ >> gnucash-user mailing list >> [email protected] >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> >> >> >> >> >> >> _______________________________________________ >> gnucash-user mailing list >> [email protected]<mailto:[email protected]> >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> >> >> >> -- >> Derek Atkins 617-623-3745 >> [email protected]<mailto:[email protected]> >> www.ihtfp.com<http://www.ihtfp.com/> >> Computer and Internet Security Consultant >> >> _______________________________________________ >> gnucash-user mailing list >> [email protected] >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> _______________________________________________ >> gnucash-user mailing list >> [email protected] >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. >> > > > -- > Derek Atkins 617-623-3745 > [email protected] www.ihtfp.com<http://www.ihtfp.com> > Computer and Internet Security Consultant > > > -- Derek Atkins 617-623-3745 [email protected] www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
