Difference between revisions of "Troubleshoot regibill regipay regimail Desktop"

From regify WIKI
Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== e-mail sending==
+
== E-mail sending==
  
 
===Can not send SMTP mails (no connection)===
 
===Can not send SMTP mails (no connection)===
 
Please check in this order:
 
Please check in this order:
−
* Are you able to access internet using a webbrowser -> if not, check computers connectivity
+
* Are you able to access Internet using a web-browser -> if not, check computers connectivity
−
* Can you use [http://windows.microsoft.com/en-US/windows7/Telnet-frequently-asked-questions telnet] to access the smtp server (''telnet smtp.myserver.net 25'')? -> If not, smtp may be blocked by a [http://wiki.regify.com/index.php?title=Troubleshooting_AntiVirus_false_positives#other_virusscanner_issues virusscanner] or firewall.
+
* Can you use [http://windows.microsoft.com/en-US/windows7/Telnet-frequently-asked-questions telnet] to access the smtp server (''telnet smtp.myserver.net 25'')? -> If not, SMTP may be blocked by a [http://wiki.regify.com/index.php?title=Troubleshooting_AntiVirus_false_positives#other_virusscanner_issues virusscanner] or firewall.
 
* There also may be a Desktop Firewall or security suite blocking the access.<br>
 
* There also may be a Desktop Firewall or security suite blocking the access.<br>
 
** We know about [http://wiki.regify.com/index.php?title=Troubleshooting_AntiVirus_false_positives#McAfee_VirusScan_.28May_2012.29 McAfee blocking Port 25] by default.<br>
 
** We know about [http://wiki.regify.com/index.php?title=Troubleshooting_AntiVirus_false_positives#McAfee_VirusScan_.28May_2012.29 McAfee blocking Port 25] by default.<br>
Line 11: Line 11:
 
===Can not send SMTP mails (time out reached)===
 
===Can not send SMTP mails (time out reached)===
 
Currently, sending of a single e-mail by using SMTP with TLS is not allowed to need more than 5 seconds. If you like to verify this, [[#How to activate debug logging|activate logging]] and compare the entry times from the beginning of the sending part until the timeout message. Possible solutions to this issue:
 
Currently, sending of a single e-mail by using SMTP with TLS is not allowed to need more than 5 seconds. If you like to verify this, [[#How to activate debug logging|activate logging]] and compare the entry times from the beginning of the sending part until the timeout message. Possible solutions to this issue:
−
* Send smaller PDF files. As a reference, an invoice of 2 pages really should not exceed the size of 100KB.
+
* Send smaller PDF files. As a reference, a document of 2 pages really should not exceed the size of 100KB.
−
* Deactivate sending SMTP using TLS (if your mailserver accepts this).
+
* Deactivate sending SMTP using TLS (if your mail server accepts this).
−
* Use an internet connection with faster upload.
+
* Use an Internet connection with faster upload.
  
−
===I get errors regarding the certificate of the mailserver===
+
===After some successful sending, error "failed connecting to pear" comes up===
 +
If you turn on the debug logging in your desktop application, you might find the following error in your log:
 +
 
 +
''421 4.4.2 Message submission rate for this client has exceeded the configured limit''
 +
 
 +
This means, that your e-mail server (Exchange?) refused further sending because some internal limit was reached. Please tell this your Exchange administrator in order to increase this limit (possibly with help from [http://www.servolutions.de/support/articles/Messagesubmissionrate.htm this site]).
 +
 
 +
===Email messages are rejected because of DKIM alignment===
 +
We've seen this at web.de, 1&1 and GMX mailservers (error message ''451 Nemesis ESMTP Service not available. Requested action aborted Reject due to policy restrictions.''). The reason was an invalid DKIM signature of the sending email server. In the cases we've seen, the domain key (d=) in the DKIM header was wrong. The domain key (d=) must match the domain of the sender of the message (''From:'' header). If it does not match, the signature may be valid but does not align to the From: header. In order to fix this, please fix the DKIM header in your email sever configuration and let the domain key (d=) point to the domain you are sending from.
 +
 
 +
Please note that this is not an error related to regify at all. It is simple mail server missconfiguration. regify can not help you to fix your email server settings.
 +
 
 +
[https://mailtrap.io/blog/dkim/ Good source for understanding the DKIM headers.]
 +
 
 +
===I get errors regarding the certificate of the mail-server===
 
You may encounter error messages like these:
 
You may encounter error messages like these:
 
* Peer Certificate can not be authenticated with given CA
 
* Peer Certificate can not be authenticated with given CA
 
* Certificate verify failed
 
* Certificate verify failed
 
* etc
 
* etc
−
In most cases, the wrong smtp server was chosen (or the wrong port). Try to find out if the mailserver certificates are correctly installed and you are really using the correct mailserver. Many mailservers are also having alias domains which are not having a matching certificate.
+
In most cases, the wrong SMTP server was chosen (or the wrong port). Try to find out if the mail-server certificates are correctly installed and you are really using the correct mail-server. Many mail-servers are also having alias domains which are not having a matching certificate.
  
−
If you are not able to eliminate the problem, please enter all data like it should work and save the settings. Now, please close the program and open up its configuration file (locate it in %APPDATA%\regify). There you need to locate a setting named '''MailIgnoreSSLError'''. Please set this value to '''1''' to let the program ignore all SSL related errors. Please remark that this setting is reset to 0 if you change the smtp server settings in the configuration dialogs.
+
If you are not able to eliminate the problem, please enter all data like it should work and save the settings. Now, please close the program and open up its configuration file (locate it in %APPDATA%\regify). There you need to locate a setting named '''MailIgnoreSSLError'''. Please set this value to '''1''' to let the program ignore all SSL related errors. Please remark that this setting is reset to 0 if you change the SMTP server settings in the configuration dialogs.
  
 
You also can try to turn off TLS usage by removing the TLS checkbox (V1.6.2 and newer only).
 
You also can try to turn off TLS usage by removing the TLS checkbox (V1.6.2 and newer only).
 +
 +
===No matter what I enter, I do not get a login===
 +
Please start [[#How_to_activate_debug_logging|debugging]] an have a look what CURL is reporting. In many cases you will get additional information. In case you can see it trying to login using AUTH GSSAPI, please note that regipay Desktop is using libcurl for connections and libcurl does not fully support AUTH GSSAPI as login option. Please use a mailserver that also offers other methods like PLAIN, LOGIN, DIGEST-MD5, CRAM-MD5 or NTLM, too.
  
 
== Processing files ==
 
== Processing files ==
Line 43: Line 60:
  
 
== Other problems ==
 
== Other problems ==
−
===Proxy issues===
 
−
The regify Desktop software supports proxy servers for connections. The proxy settings have to be entered manually.
 
  
−
For authentication, the regify Desktop software supports the following authentication schemes: AUTH_BASIC, AUTH_DIGEST and AUTH_NTLM.
+
===The software always starts with setup assistant===
 +
This are the possible reasons:
 +
 
 +
# You log in to Windows with wrong user/account (settings are profile related and if you login with different user profile, the settings are different or not existing).
 +
# The windows profile and the files in %APPDATA% were deleted.
 +
# Previously configured PDF pathes from your profile are not accessible.
 +
## Once a needed VPN was not connected.
 +
## Once the permissions to the SMB share were removed.
 +
## Once, the path has simply changed (different network folder etc).
 +
## Check below article [[Troubleshoot_regibill_regipay_regimail_Desktop#The_software_closes_after_the_wizard_was_run.2C_unable_to_start |The software closes after the wizard was run, unable to start]].
 +
# Or you did a fresh install on a new PC.
 +
 
 +
===The software closes after the wizard was run, unable to start===
 +
We've seen this before if the path of either the Windows profile (%APPDATA%) has changed or the pathes configured in the profiles are no longer existing. To fix this, follow these steps:
 +
 
 +
'''Fix the profiles.ini'''
 +
 
 +
# Enter '''%APPDATA%\regify''' into the file explorer
 +
#* Does the folder exist? If not, you are on a different Windows account! Log in with the correct user or ask your administrator to restore your Windows profile data.
 +
#* Please look at the full path now in file explorer. You need it in step 4.
 +
# Enter the directory of your desktop product (eg regipay_desktop, regibill_desktop, regimail_desktop).
 +
# Open the file '''profiles.ini'''.
 +
# Verify all entries for ''file'', ''idfile'' and ''logofile''. All pathes of the files have to point to the same directory as the one identified in step 1. If they don't do, please adapt to the new path, but keep the filenames.
 +
# Save the updated file.
 +
 
 +
'''Fix the regify profiles'''
 +
 
 +
# Enter '''%APPDATA%\regify''' into the file explorer
 +
# Enter the directory of your desktop product (eg regipay_desktop, regibill_desktop, regimail_desktop).
 +
# Open all the '''profile_yyyy-mm-dd-hh-nn-ss.ini''' files and check or repair the path information inside.
 +
#* Check the fields ''SourceDir'', ''DoneDir'', ''ErrDir'' and ''BillDir''. Do not change any other data in here!
 +
#* Save the files.
  
−
Please always test with the most recent regify Desktop software version!
+
Now start your regify Desktop tool and check if it works.
  
−
=== What ports is regify Desktop using? ===
+
===I'm unable to import profiles===
−
In order to allow regify Desktop to work, you need to allow accessing the Internet on TCP/IP ports 443 (https) and 80 (http).
+
It might be that your PC needs a proxy server. Sadly, the profile import and export does not contain proxy passwords until regify desktop version 2.3.2. To import, please run the regipay desktop. The first page of the setup assistant appears. But before clicking the import button, first fill in valid proxy settings. Then click the import button and import the profile needed.
  
−
=== What domains do I need to white-list for regify Desktop usage? ===
+
'''NOTE:''' If the setup assistant does not appear, you already may have a working profile. If this is not something you need to keep (eg just a test), you can delete the whole content of the folder ''%appdata%\regi..._desktop\'' to get a clean configuration and then the assistant will start on next run.
−
* In general, regify Desktop needs access to all '''*.regify.com''' domains. This is for using the PLS (Provider Lookup Service) and for automatic updates etc.<br>
 
−
* In addition, you need to white-list the '''domains of your regify provider'''. These domains depend on the regify provider your regify account is registered at.
 
  
 
===How to activate debug logging===
 
===How to activate debug logging===
−
Try to activate the debug log by starting with commandline parameter (example call):
+
<span style="display: block; padding: 10px; border: 1px solid #550000; background-color: #ffcccc; color: 550000;">'''Warning:'''<br>This logging is mainly for developers. Please inspect the logfile for passwords before you send it to us. In case a users password (account, smtp etc) is inside, please replace it by some other text or delete it!</span>
−
  regibill_desktop.exe -v -l "c:\temp\logfile.txt"
+
 
 +
Activate the debug log by starting with commandline parameter (example call):
 +
  regipay_desktop.exe -v -l "c:\temp\logfile.txt"
 
If you start regibill, regipay or regimail Desktop this way, it writes a verbose log into the given logfile.
 
If you start regibill, regipay or regimail Desktop this way, it writes a verbose log into the given logfile.
 
Please ensure that you have write permissions on the given logfile location and that the destination path exists.
 
Please ensure that you have write permissions on the given logfile location and that the destination path exists.
 
If you have been prompted to send this logfile to regify, please send it to support@regify.com.
 
If you have been prompted to send this logfile to regify, please send it to support@regify.com.
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
-

Latest revision as of 07:54, 17 October 2024

E-mail sending

Can not send SMTP mails (no connection)

Please check in this order:

  • Are you able to access Internet using a web-browser -> if not, check computers connectivity
  • Can you use telnet to access the smtp server (telnet smtp.myserver.net 25)? -> If not, SMTP may be blocked by a virusscanner or firewall.
  • There also may be a Desktop Firewall or security suite blocking the access.

Can not send SMTP mails (time out reached)

Currently, sending of a single e-mail by using SMTP with TLS is not allowed to need more than 5 seconds. If you like to verify this, activate logging and compare the entry times from the beginning of the sending part until the timeout message. Possible solutions to this issue:

  • Send smaller PDF files. As a reference, a document of 2 pages really should not exceed the size of 100KB.
  • Deactivate sending SMTP using TLS (if your mail server accepts this).
  • Use an Internet connection with faster upload.

After some successful sending, error "failed connecting to pear" comes up

If you turn on the debug logging in your desktop application, you might find the following error in your log:

421 4.4.2 Message submission rate for this client has exceeded the configured limit

This means, that your e-mail server (Exchange?) refused further sending because some internal limit was reached. Please tell this your Exchange administrator in order to increase this limit (possibly with help from this site).

Email messages are rejected because of DKIM alignment

We've seen this at web.de, 1&1 and GMX mailservers (error message 451 Nemesis ESMTP Service not available. Requested action aborted Reject due to policy restrictions.). The reason was an invalid DKIM signature of the sending email server. In the cases we've seen, the domain key (d=) in the DKIM header was wrong. The domain key (d=) must match the domain of the sender of the message (From: header). If it does not match, the signature may be valid but does not align to the From: header. In order to fix this, please fix the DKIM header in your email sever configuration and let the domain key (d=) point to the domain you are sending from.

Please note that this is not an error related to regify at all. It is simple mail server missconfiguration. regify can not help you to fix your email server settings.

Good source for understanding the DKIM headers.

I get errors regarding the certificate of the mail-server

You may encounter error messages like these:

  • Peer Certificate can not be authenticated with given CA
  • Certificate verify failed
  • etc

In most cases, the wrong SMTP server was chosen (or the wrong port). Try to find out if the mail-server certificates are correctly installed and you are really using the correct mail-server. Many mail-servers are also having alias domains which are not having a matching certificate.

If you are not able to eliminate the problem, please enter all data like it should work and save the settings. Now, please close the program and open up its configuration file (locate it in %APPDATA%\regify). There you need to locate a setting named MailIgnoreSSLError. Please set this value to 1 to let the program ignore all SSL related errors. Please remark that this setting is reset to 0 if you change the SMTP server settings in the configuration dialogs.

You also can try to turn off TLS usage by removing the TLS checkbox (V1.6.2 and newer only).

No matter what I enter, I do not get a login

Please start debugging an have a look what CURL is reporting. In many cases you will get additional information. In case you can see it trying to login using AUTH GSSAPI, please note that regipay Desktop is using libcurl for connections and libcurl does not fully support AUTH GSSAPI as login option. Please use a mailserver that also offers other methods like PLAIN, LOGIN, DIGEST-MD5, CRAM-MD5 or NTLM, too.

Processing files

While processing PDF files, the application stops with error 99

There are various reasons known for this error. Please follow these steps to solve the problem:

  1. Please ensure that you are using regibill desktop or regipay desktop in version 1.6 or newer. If not, please download the most recent version at the regify homepage.
  2. Please ensure that the PDF file's you are using are compliant to the standards. You can validate PDF files online at pdf-tools] (check Analyze Only option). Only valid PDF files can get converted to regibills or regipays.
  3. Try to turn off any "optimization" options like "Enable Fast Web View", "Optimize for web", "Web Optimized", "Optimized Output", "Linearized" or similar.
  4. Try to turn off compression options (if available).
  5. If the problem still exists, please send some detailed error description and such a PDF document to support@regify.com.

While processing PDF files, the application stops with error 60

There are multiple possible solutions for this problem:

  1. Check, if you have all needed permissions on the folders you are using.
  2. Please do not use a regify account with obligatory attachments together with regibill or regipay.

For further information, please activate logging and send the logfile together with a detailed error description to regify support.

Other problems

The software always starts with setup assistant

This are the possible reasons:

  1. You log in to Windows with wrong user/account (settings are profile related and if you login with different user profile, the settings are different or not existing).
  2. The windows profile and the files in %APPDATA% were deleted.
  3. Previously configured PDF pathes from your profile are not accessible.
    1. Once a needed VPN was not connected.
    2. Once the permissions to the SMB share were removed.
    3. Once, the path has simply changed (different network folder etc).
    4. Check below article The software closes after the wizard was run, unable to start.
  4. Or you did a fresh install on a new PC.

The software closes after the wizard was run, unable to start

We've seen this before if the path of either the Windows profile (%APPDATA%) has changed or the pathes configured in the profiles are no longer existing. To fix this, follow these steps:

Fix the profiles.ini

  1. Enter %APPDATA%\regify into the file explorer
    • Does the folder exist? If not, you are on a different Windows account! Log in with the correct user or ask your administrator to restore your Windows profile data.
    • Please look at the full path now in file explorer. You need it in step 4.
  2. Enter the directory of your desktop product (eg regipay_desktop, regibill_desktop, regimail_desktop).
  3. Open the file profiles.ini.
  4. Verify all entries for file, idfile and logofile. All pathes of the files have to point to the same directory as the one identified in step 1. If they don't do, please adapt to the new path, but keep the filenames.
  5. Save the updated file.

Fix the regify profiles

  1. Enter %APPDATA%\regify into the file explorer
  2. Enter the directory of your desktop product (eg regipay_desktop, regibill_desktop, regimail_desktop).
  3. Open all the profile_yyyy-mm-dd-hh-nn-ss.ini files and check or repair the path information inside.
    • Check the fields SourceDir, DoneDir, ErrDir and BillDir. Do not change any other data in here!
    • Save the files.

Now start your regify Desktop tool and check if it works.

I'm unable to import profiles

It might be that your PC needs a proxy server. Sadly, the profile import and export does not contain proxy passwords until regify desktop version 2.3.2. To import, please run the regipay desktop. The first page of the setup assistant appears. But before clicking the import button, first fill in valid proxy settings. Then click the import button and import the profile needed.

NOTE: If the setup assistant does not appear, you already may have a working profile. If this is not something you need to keep (eg just a test), you can delete the whole content of the folder %appdata%\regi..._desktop\ to get a clean configuration and then the assistant will start on next run.

How to activate debug logging

Warning:
This logging is mainly for developers. Please inspect the logfile for passwords before you send it to us. In case a users password (account, smtp etc) is inside, please replace it by some other text or delete it!

Activate the debug log by starting with commandline parameter (example call): 

regipay_desktop.exe -v -l "c:\temp\logfile.txt"

If you start regibill, regipay or regimail Desktop this way, it writes a verbose log into the given logfile. Please ensure that you have write permissions on the given logfile location and that the destination path exists. If you have been prompted to send this logfile to regify, please send it to support@regify.com.

















-

Retrieved from "https://wiki.regify.com/index.php?title=Troubleshoot_regibill_regipay_regimail_Desktop&oldid=2497"