gform_after_submission; inherit post

I am using 'gform_after submission' to check input data and setting filters.
Now I recognized that the form always submits two post to my database: a 'Untitled_??' named one with status 'inherit' and the real one with the given name and status 'published'.
This is causing trouble because the first entry already triggers Subscribe2 to send out an email to notify subscribers of a 'Untitled_??' new post.
I have tried 'gform_post_submission' with the same result.
How can I avoid or suppress the 'inherit posting'? What is it good for ?

Yes, you are right: I was a little confusing.
Found out the same meanwhile. Looks like Subscribe2 ( the code I am running) is getting the post_title of the child (attachment) not the parent (the post).
I changed code now to
[$post->post_title = get_the_title($post->post_parent);]

Hope this helps.

Found the reason for my probs:
I had this three fields in my forms: a single line text(1), a Post Title(2) and a Body Field(3).
For some reason, I used the single line input(1) via tag also in (2) as PostTitle in form of {input:1}.
Somehow, on submission the Post Title field(2) came in empty, although text was entered into (1). This caused the 'Untitled_**' naming and all subsequent failures.
Changed to use the Post Title field(2) as entry point and dropped (1). It works now but I lost the 'no duplicates' checkbox which is available in (1) but not in (2).
What is the reason for this behaviour? Inserting the merge tag should fully replace the content of the Post Title field - at least at submission.

I am not sure what you want me to do because I am using the German translations of GF. Do you mean the content template in a body field?
I can check putting a Single Input and a Post Title as a tag into the content field and see what happens or I do a var_dump($entry) in the callback function of my gform_after_submission hook. I guess the latter will be more enlightening or I do both together.
I am highly interested to use the Single Input field because this is a user input. They have no glue what's already in my database when they type it. Otherwise, I have to set a filter to avoid duplicates, bouncing back to user, re-enter and all that stuff.
Is there a hook later in time, maybe gform_post_submission, where I can rely on the merge tags being parsed?

Tried it and worked well, so far!
But now I have another issue maybe related to the above. I have a image file upload field in my form and whenever my users are typing German umlauts the $entry[n] contains the right representation also after submission. The file is targeted as thumbnail image for the post. When I look at the uploaded file name, it has been transferred to the standard WP upload folder and to the hashed GF upload folder, but both have the umlauts converted to HTML entities and subseqently, is not displayed as a post_thumbnail. Looking at the database the GUID of the thumbnail points to the WP standard upload folder but the file name shows umlauts. Because they are not the same, it will not display. I have traced it back to the line 1870 in forms_model.php and the target there is the GF hashed upload folder/file name with umlauts. After that may debugger won't work and crashes when the database is accessed. So ,I can't tell what happens after.
Long story, short question: where happens the fault? Is it the move_uploaded_file() function?
It seems to happen during the file transfer. Anything I can hook or filter into?

Auto-reply to my question 3 days ago : it is the move_uploaded_file() function!
Transferring the files using this function converts umlauts . Since GF is not using wp_handle_upload function from WP (why?) you do not get hooks or filters short before transferring the upload. So I had to modify the plugin code(!) to get rid of this nasty thing. I hate doing that because of obvious reasons.
Are there any plans to insert a hook/filter there or to use wp_handle_upload in future??