SMTP Server Issue in intersystem cache - email

I am facing an issue when I am sending Email from intersystems cache. I am able to send the mail, with out any problem the first time. But the second time when I am trying to send the smtp server is not responding properly. The first Helo command is sent. I recieve the confirmation 220 from the server. But I do not recieve the Message 250. So the next command is giving me the error 503, 5.5.2 "Send helo first" message.
I am unable to find out why the server is not responding the second time.

Related

Differences in mailing from different servers

I have a java application installed on unix server using a tomcat instance.
it has a feature which allows to send email to external user and get reply from their Outlook.
The sending and receiving process works well but when trying to reply on their reply from the application i'm getting an error:
There was an error sending a message.
If the problem persists, please contact your system administrator.
Error: No recipient addresses
When sending the first e-mail from the application, the "To" address is:
name.surname#domain.com
But when receiving the reply from the recipient it will turn to:
Surname, Name < name.surname#domain.com >;
From trying it from different server it will work and the only different is that the "To:" address looks like this:
"Surname, Name" < name.surname#domain.com >
Application on both servers using same outgoing/incoming mail servers.
What else can effect it and cause the above error?
Thanks.

Send Email - ESMTP Remote Server - Access Denied, but works for coworker

I'm trying to send an email to a client, with an address #comcast.com
Within 4 seconds I get an email in my Inbox saying the message failed delivery.
A coworker sitting 10 feet away from me can send emails to this address successfully. We are on the same domain and network.
Delivery has failed to these recipients or groups:
xxxxx-xxxx#comcast.com (yes, the name has a hyphen in it)
A problem occurred while delivering this message to this email address. Try sending this message again. If the problem continues, please contact your helpdesk.
The following organization rejected your message: ESMTP.
xxxxx-xxxx#comcast.com
ESMTP
Remote Server returned '<ESMTP #5.0.0 smtp;550 Mailbox unavailable or access denied - <xxxxx-xxxxx#comcast.com>>'
If any further information is needed please let me know.
Does this seem like a problem at the clients end or on our side?
Any ideas as to the cause? I don't see any detail about my access was denied... no space, spam, blacklist, etc.?

Database mail messages are being queued but they are never delivered

I have database mail configured properly, it has been working all along but then suddenly iam getting the error below in the description column of the sysmail_event_log view database msdb.
Any idea why i could be getting this error message?
Bellow is the error.
"The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2014-02-25T08:29:30). Exception Message: Cannot send mails to mail server. (Mailbox unavailable. The server response was: Unable to complete command, no storage available)"
This is issue was caused by the server admins had dis-commissioning the SMTP server with out notice and i was referring to a non existent SMTP server IP address.

SMTP Mail Failures to a certain domain

Do the SMTP logs on a server (Windows 2003) only show logs of mail that were sent successfully?
We are getting bounce backs when sending mail to a particular domain:
The connection was dropped by the remote host.
It looks like a problem on the receiving server, but we dont have much information to provide them. We can send to hotmail, gmail, yahoo etc OK.
Any ideas?
Most likely, there is a spam filter in front of the receiving mail server for this domain, and this spam filter thinks your mail server is sending spam, so it's closing the connection from your mail server. One way to test this is to simulate sending a message to this mail server by opening a command prompt on your mail server, and use telnet to connect to the receiving mail server on port 25, and proceed with the process of sending a message just as a mail server would. This way, you'll be able to see how the receiving mail server responds after each step. Follow the instructions in http://support.microsoft.com/kb/153119 to see how this is done.
It turned out the sending server was blacklisted by McAfee, that was running on the receiving servers firewall.
For those that may have the problem in the future you can check if your server is blacklisted with McAfee here:
http://www.mcafee.com/threat-intelligence/ip/spam-senders.aspx
After entering your server IP, you should see a link Threat Feedback. Use this to email McAfee.
I was able to send McAfee an email with an explanation, they then removed our server from the blacklist.

SMTP outbound emails stuck in Queue folder : Windows XP SP3, IIS 5.1

I am using a PHP script for sending emails by IIS 5.1 SMTP.
The emails, go to outbound folder. really path is C:\Inetpub\mailroot\Queue.
after a seconds, it start to send emails properly, but after sending 5 or 6 emails, it stops to send the other ones. SMTP service is still start and it seems there is no problem to SMTP service.
but,If i restart the service, it sends 1 or 2 other emails and then, it stops again.
I mean sending emails stop but service is start.
by the way, emails are stucked in Queue folder.
Also i checked Badmail folder. it is empty
Thanks
are all the emails to the same network? I have seen behaviour like this when the recipient server bans you, yahoo's (xtra) used to do it sometimes to our server in particular. You can check the logs in event viewer for something from the smtp server, you'll find a message from the other server saying something to the effect that you have been temporarily banned, possibly with more detail about why. Trying to connect via telnet also gives you the same message.
When this happens windows will try and send them again later. Restarting the server starts to try sending again and if the ban condition has been lifted messages will flow for a while again until you are rebanned.