CyberFerret
2006-03-04, 12:43 AM
Hi all,
Just thought we would share an experience we had here with our first email campaign out of Sugar.
We run our Sugar CRM server in house, but our mail etc. is run via our ISP's email server, which we had Sugar pointed to for all SMTP traffic.
When we set up our campaign, we sent a couple of single test emails, which went through perfectly. But then when we went to send our campaign (which was only about 50 messages), they stayed in the Outbound Message Queue, and nothing would budge them. We then deleted the queue, and tried resending the single test, but it would not go either!
Further investigation revealed that our ISP had detected a mass of outgoing emails from our server, and blocked us as a possible spam relay site!!
Unfortunately, when specifying monitored mailboxes in Sugar, you cannot specify a different outgoing mail server from where the POP box is stored, so I assume that Sugar was using our ISP's SMTP server to transmit.
How did we get around this? We went to the Sugar default system settings, and changed the outgoing mail server in there from our ISP's SMTP server, to plain 'sendmail'. This I assume forced sugar to use the Linux sendmail service on its own box, thus alleviating our ISP's restriction.
Oh, BTW - We had to contact our ISP and get them to manually remove the 'block' from our Sugar server IP address!
Hope this helps anyone else who experiences the same (or similar) issues...
Cheers,
Devan
Just thought we would share an experience we had here with our first email campaign out of Sugar.
We run our Sugar CRM server in house, but our mail etc. is run via our ISP's email server, which we had Sugar pointed to for all SMTP traffic.
When we set up our campaign, we sent a couple of single test emails, which went through perfectly. But then when we went to send our campaign (which was only about 50 messages), they stayed in the Outbound Message Queue, and nothing would budge them. We then deleted the queue, and tried resending the single test, but it would not go either!
Further investigation revealed that our ISP had detected a mass of outgoing emails from our server, and blocked us as a possible spam relay site!!
Unfortunately, when specifying monitored mailboxes in Sugar, you cannot specify a different outgoing mail server from where the POP box is stored, so I assume that Sugar was using our ISP's SMTP server to transmit.
How did we get around this? We went to the Sugar default system settings, and changed the outgoing mail server in there from our ISP's SMTP server, to plain 'sendmail'. This I assume forced sugar to use the Linux sendmail service on its own box, thus alleviating our ISP's restriction.
Oh, BTW - We had to contact our ISP and get them to manually remove the 'block' from our Sugar server IP address!
Hope this helps anyone else who experiences the same (or similar) issues...
Cheers,
Devan