|
Florin Dragomir
   
(
October 19, 2012
)
Beware!
Issues with basic stuff like dealing with greylisting (e.g. recognizing the destination server request to send again the message after let's say 3 minutes). Coupled with a massive IP frequent changing, you get yourself in trouble if your counterparts use domain+IP identification. One of my customer manually inserted over 200 IP addresses in order to receive my messages. However, as Romarg server does not recognize the request of sending again the messages so that it is recognized as not spam, I still don't know how many messages get through even they still help by introducing manually the new IPs as Romarg is changing them. And your support tickets take like ages for not even fixing them! Beware!
|