This is my problem :
Hi,
i have this on all the email the workflow reply , heres my node. i put it to false but that changes nothing the email continue to have ““This email was sent automatically with n8n
https://n8n.io”” . So i need a lil help
It looks like you’re trying to remove the “This email was sent automatically with n8n” footer but it persists even after disabling the “Append n8n Attribution” option. This issue might be related to a new bug.
i use an smtp thats write on the screenshot… but that change nothing
Yea that’s weird because you have it off, maybe try restarting your n8n instance?
i uptade n8n on hostinger to see if that change something but , nothing changes 
Maybe see if you can turn it back on the append button, run it, and turn it back off, and run it again?
ok , i did it
But nothing change , one more time :L
i really dont know why i have this , its not supposed to be possible
It should be off, its extremely weird! Can you try deleting the node and readding it?
Heres all my worflow , i try to used the node java to help and hide the n8n msg but it didnt works too
In the options you have to disable to send by n8n.
yes , thats the first thing i did
the n8n message continue to appear on the mails
i have n8n version 2.4.4 , is that the problem ?
I just tested this behaviour in n8n 2.4.4 and it does work as expected.
I’d recommend that you delete the node from your workflow and add it back again to enusure
that your workflow is using the latest version of this node.
i tried it , i tried too recreate the entire workflow, thats changes nothing.. the message continue to be on the email
when i test the workflow inside n8n that work but when the workflow just do it himself , it didnt work..
I just tested it with n8n 2.4.4 in manual (test) mode and with a scheduled trigger. In both cases the node did behave as expected and removed the attribution when the toggle was off in the node settings.
Are you using n8n cloud or selfhosted? If it’s cloud, get in touch with support via [email protected] or support.n8n.io
If its local, I’d recommend to spinup a new instance and see if the issue is gone.
i paied the hostinger offer to host it
do you already “Republish” the updated version?
yes i did it
