Issues after upgrade to V3

Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic

   Yesterday we updated to V3 and we have run into 2 major issues as of right now that has us partially dead in the water as far as our parsing goes. The first one is that using the build in email2db database the message store would not convert and migrate into the V3 built-in database. 

When performing this via the email2db server configuration it migrates the mail server settings fine but when it gets to the conversion of the message store to V3 the database version the server config manager becomes "Not Responding" and i have to use task manager to kill it. This happens every single time and does not seem to get past that point without killing it.

The second issue is outbound emails which is the major issue for us right now because it make it that only half of our process is working. Our inbound process for our account and triggers which includes checking emails, parsing them and performing the trigger events seems to be working ok it's the portion of the outbound part which includes customized emails to our clients and potential clients that is killing us right now. 

We have the email2db mail server installed we use our own dedicated server for all outbound emails only and do not use the built in mail server at all. We had no issues without bound emails and now we get the foillowing message everytime no matter what account is sending which we have about 5 accounts and each account only has one trigger.

Our email2db server and our dedicated mail server are both on the same VLAN behind our firewalls. and before the upgrade we had all the settings set for the email2db application to connect via IP address and never had issues. Now as you see we tried with the IP address and also the actual domain and get the same thing no matter what.

For security i have xxxx'd out our domain and partial of the ip address of the network but you should get the idea. Also the confusing thing is that i see below that the email address being used to send is email2dbserver@ourdomain.com but i can not find anywhere to change the password or settings for this account and also depending on the account and trigger one trys using our sales@ email and the other seems to try using the email2db@ email.

That email2dbserver@ account will never be able to send thru our server if i can't change it's password and create a account on our email server. The sales@ account passes the send test option inside the Program options of email2db but as you see it won't send out thru the same account via the trigger settings for outbound emails.

4/23/2012 9:07:11 PM 19x.xxx.xxx.210 message for <sales@ourdomain.com> from <email2dbserver@ourdomain.com> failed with error Destination SMTP server replied invalid to HELO command. (30012) will retry in 5 attempt 1 (1 Relays)

4/24/2012 12:01:31 PM mail.ourdomain.com mail server relay To <abxxxxxir@xxxxxx.com> from <sales@ourdomain.com> error Destination SMTP server replied invalid to HELO command. (30012)

I can deal with the message store not converting for now but the outbund email issues i have got to get resolved fast, i figured i'd post in here first before opening a ticket with support since we have a lifetime subscription.

Author	Message Share Topic Printable Version Google Delicious Digg StumbleUpon Windows Live Yahoo Bookmarks reddit Facebook MySpace Newsvine Furl Topic Search Topic Options Post Reply Create New Topic
JnascECSI Members Profile Send Private Message Find Members Posts Add to Buddy List New User Joined: 24 May 2007 Location: Rhode Isalnd Posts: 2	Post Options Post Reply Quote JnascECSI Report Post Quote Reply Topic: Issues after upgrade to V3 Posted: 24 Apr 2012 at 5:45pm
	Yesterday we updated to V3 and we have run into 2 major issues as of right now that has us partially dead in the water as far as our parsing goes. The first one is that using the build in email2db database the message store would not convert and migrate into the V3 built-in database. When performing this via the email2db server configuration it migrates the mail server settings fine but when it gets to the conversion of the message store to V3 the database version the server config manager becomes "Not Responding" and i have to use task manager to kill it. This happens every single time and does not seem to get past that point without killing it. The second issue is outbound emails which is the major issue for us right now because it make it that only half of our process is working. Our inbound process for our account and triggers which includes checking emails, parsing them and performing the trigger events seems to be working ok it's the portion of the outbound part which includes customized emails to our clients and potential clients that is killing us right now. We have the email2db mail server installed we use our own dedicated server for all outbound emails only and do not use the built in mail server at all. We had no issues without bound emails and now we get the foillowing message everytime no matter what account is sending which we have about 5 accounts and each account only has one trigger. Our email2db server and our dedicated mail server are both on the same VLAN behind our firewalls. and before the upgrade we had all the settings set for the email2db application to connect via IP address and never had issues. Now as you see we tried with the IP address and also the actual domain and get the same thing no matter what. For security i have xxxx'd out our domain and partial of the ip address of the network but you should get the idea. Also the confusing thing is that i see below that the email address being used to send is email2dbserver@ourdomain.com but i can not find anywhere to change the password or settings for this account and also depending on the account and trigger one trys using our sales@ email and the other seems to try using the email2db@ email. That email2dbserver@ account will never be able to send thru our server if i can't change it's password and create a account on our email server. The sales@ account passes the send test option inside the Program options of email2db but as you see it won't send out thru the same account via the trigger settings for outbound emails. 4/23/2012 9:07:11 PM 19x.xxx.xxx.210 message for <sales@ourdomain.com> from <email2dbserver@ourdomain.com> failed with error Destination SMTP server replied invalid to HELO command. (30012) will retry in 5 attempt 1 (1 Relays) 4/24/2012 12:01:31 PM mail.ourdomain.com mail server relay To <abxxxxxir@xxxxxx.com> from <sales@ourdomain.com> error Destination SMTP server replied invalid to HELO command. (30012) I can deal with the message store not converting for now but the outbund email issues i have got to get resolved fast, i figured i'd post in here first before opening a ticket with support since we have a lifetime subscription.

Stephen Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List Admin Group Joined: 21 Oct 2005 Location: Stoke on Trent Posts: 1389	Post Options Post Reply Quote Stephen Report Post Quote Reply Posted: 24 Apr 2012 at 7:40pm
	Hi, Firstly how big is your V2 Message Store (Email2Db.Vdb file). There should be no issue migrating the message store to V3 unless the V2 is corrupt - or you have not left the migrate long enough (it can take several hours if its large). Email2DB doesn't use an email address to send - it uses the from address of the message. The email2dbserver address is the bounce address (ie the from address it gives bounce messages). We are looking into the invalid HELO command response and should have a resolve shortly. Steve