Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Mar 11, 2022

RELATED IDEAS

Send the error-report as multiple files or to alter the behavior for the way its generated/sent

Hello Team,

We did not receive error reports before reloading and during the startup, we have noticed below errors in the error report.


20220119T222709.173Z [0x80e0057c][smtp][error] ErrorReport(drErrorReport): tid(28031): SMTP Client: Error '501 Error: attribute value too long' in state 'Sending'


Our SMTP server is not accepting and buffer, The line length is not defined directly within Postfix – rather it is defined within our IMSVA (Trend Micro IMSVA) product settings which essentially utilize the postfix engine underneath. When we tested the removal of the line length limitations by setting the value to 0 (it was set to 81920 bytes) the email was successfully delivered. In discussions with our vendor TrendMicro, removing this line is not advised from a security perspective. One other point to note is that the test which had a zipped attachment – contained a file of approx. 180Mb which will not be processed as we also have a limit on the maximum size of any single file within an archive. Please consider breaking these files into smaller separate files within the zipped/archive or utilize SFTP to transfer these files to a share location.


We cannot provide our postfix configurations but I do have a lab environment that can be used for doing some tests. This is where we tested removing the line length setting. However, please note any proposed changes to our settings have the potential to impact all other applications using these relay servers – and so far we have had no other applications that require chunking to send emails through our gateway. Any changes suggested will have to be reviewed with out Vendor support and assessed for additional impact.


Idea priority High
  • Guest
    Reply
    |     Mar 31, 2023

    We have not heard back from information request. This will be closed. Re-open if still required with the additional information requested.

  • Guest
    Reply
    |     May 20, 2022

    How exactly should the error report be broken down into multiple files?

    • You still have to make it into a zip if it is multiple files? Otherwise you would have hundreds of attachments on the same email (in neither case does that solve the sizing problem).

    • If you split it into multiple emails you have hundreds of emails. I don't believe using SMTP for pushing error reports is the optimal solution, especially in a live production environment. You may be better off trying FTP/NFS given more active environments of DataPower such as production will result in larger error report (hundreds of megabytes, even seen them go into gigabyte ranges)

    DataPower already supports FTP and NFS as alternates to SMTP (no SFTP sadly) -- so maybe this idea should focus on SFTP support?

    https://www.ibm.com/docs/en/datapower-gateway/10.0.1?topic=reports-configuring-failure-notification


    You may be better served by polling either xml-mgmt or rest-mgmt for the FailureNotificationStatus and see if there are new entries. Then you can use xml-mgmt/rest-mgmt to download (get-file) the error report. I would suggest this primarily if you are looking for a secure protocol to communicate over since SFTP isn't an option.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.