After updating Messaging Gateway (SMG) to version 10.7.4 the ecelerity process (mail server) begins logging stack traces into the maillog file although there is no associated process crash or other issue.
2020 Dec 29 08:09:01 EST (err) ecelerity: [7847]
#0 0x4872fb#011/opt/msys/ecelerity/sbin/ecelerity(ec_log_current_stack_trace+0x2b) [0x4872fb]
#1 0x4b48c9#011/opt/msys/ecelerity/sbin/ecelerity(ec_malloc_size+0x199) [0x4b48c9]
#2 0x7f00b5ae2220#011/opt/msys/ecelerity/libexec/validate/spf.so(+0x5220) [0x7f00b5ae2220]
#3 0x7f00b5ae2e23#011/opt/msys/ecelerity/libexec/validate/spf.so(+0x5e23) [0x7f00b5ae2e23]
#4 0x7f00b5ae5e25#011/opt/msys/ecelerity/libexec/validate/spf.so(spf_process+0x2755) [0x7f00b5ae5e25]
#5 0x7f00b5adfd1e#011/opt/msys/ecelerity/libexec/validate/spf.so(+0x2d1e) [0x7f00b5adfd1e]
#6 0x48961e#011/opt/msys/ecelerity/sbin/ecelerity() [0x48961e]
#7 0x56292e#011/opt/msys/ecelerity/sbin/ecelerity() [0x56292e]
#8 0x5614ca#011/opt/msys/ecelerity/sbin/ecelerity() [0x5614ca]
#9 0x562147#011/opt/msys/ecelerity/sbin/ecelerity(process_answer+0x217) [0x562147]
#10 0x563918#011/opt/msys/ecelerity/sbin/ecelerity(glue_read_udp_packets+0xc8) [0x563918]
#11 0x7f00ac22d397#011/opt/msys/ecelerity/libexec/schedulers/epoll.so(+0x2397) [0x7f00ac22d397]
#12 0x7f00ac22daa5#011/opt/msys/ecelerity/libexec/schedulers/epoll.so(+0x2aa5) [0x7f00ac22daa5]
#13 0x45165f#011/opt/msys/ecelerity/sbin/ecelerity(main+0x87f) [0x45165f]
#14 0x7f00be59b3d5#011/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f00be59b3d5]
#15 0x4518a9#011/opt/msys/ecelerity/sbin/ecelerity() [0x4518a9]
Component: MTA
This issue has been addressed with the 10.8.0 release.
For SMG releases previous to version 10.8.0, this is a false error message being generated by the mail server and may be safely ignored. The stack trace does not indicate any issues with mail processing and will be removed in the SMG 10.7.6 release.