Home Forums Bug Reports SwithMail Bug Reports Strange swithmail behaviour with a long subject field

Viewing 3 reply threads
  • Author
    Posts
    • #131 Score: 0
      Gil Fleming
      Participant

      We have downloaded swithmail to see if we can incorporate it into our in-house invoicing system. It was looking promising until we had a subject bigger than 40 characters and used a body text file. When the mail was received, the subject had been truncated to 40 characters and then concatted with the body text file name. If we have a short subject line, it works ok. We need the longer line because the subject is of the form: “FT Invoice Ref EInv 011996 (Southampton Car & Van Hire)”.

      • This topic was modified 2 years, 9 months ago by Gil Fleming.
    • #134 Score: 0
      tbare
      Keymaster
      1 pt

      Interesting — there is no character limit on the fields, so I’m not sure why that’s happening.

      The subject is breaking after the word “Southampton”?

      Try changing the “&” to & amp; (without quotes and remove the space) and see if that gets it working.

      If not, can you send over the XML or the CLI string you’re using (mark it as a private reply) so I can see if I can duplicate it on my side?

      • This reply was modified 2 years, 9 months ago by tbare.
      • This reply was modified 2 years, 9 months ago by tbare.
    • #138 Score: 0
      Gil Fleming
      Participant

      It was a false alarm. We are programming (scripting) inside database software. This involves passing parameters between procedures so that a user can send an email by simply clicking a button on, say , the invoice screen in order to send a copy invoice. The problem was being caused by a corruption in our database software so that two passed parameters were being somehow merged. We’ve found a workaround so can continue the work. On a separate topic, you give an example of a batch file that uses errorlevel to return a successful or unsuccessful send. We are not operating in a batch file but calling swithmail from within our software. for example, our procedure for swithmail would be:

      call program w:\swithmail.exe …. with parameters.

      can we access error codes from within our system?

    • #141 Score: 0
      tbare
      Keymaster
      1 pt

      Glad you got it working!

      I’ll tell you, I’ve never tried getting the results not from within a batch, but the program does return a 0 or 1, so you may be able to set a variable to the call program w:\swithmail.exe ... (depending on capabilities of your program) and step through and see if it sets it to a 1 or 0.

      pseudo code:

      dim swithSuccess as boolean = 0
      
      swithSuccess = call program w:\swithmail.exe /s /xml "w:\swithSettings.xml"
      
      if(swithSuccess == 0) {
        -- Success
      } else {
        -- Fail
      }
      • This reply was modified 2 years, 9 months ago by tbare.
Viewing 3 reply threads
  • You must be logged in to reply to this topic.