Solved

Mail Server throws the below Error Please Check with IT Department.

Posted on 2008-06-15
11
537 Views
Last Modified: 2008-08-05
Hi all,

For some mail users getting below error message when they trying to send messages to outside domain
I tried with adding queing to registry and restarting the SMTP services, But no use. Pls help me out to resolve the issue.

Bounced Back Mail:

com.sun.mail.smtp.SMTPAddressFailedException: 451 4.7.1 Greylisting in action, please come back in 00:04:14

        at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:1061)
        at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:584)
        at com.simatech.feeder.core.utility.MailUtility.sendMail(MailUtility.java:76)
        at com.simatech.feeder.service.finance.invoice.InvoiceService.mailSend(InvoiceService.java:1764)
        at com.simatech.feeder.web.finance.invoice.InvoiceAction.sendmailInvoice(InvoiceAction.java:1773)
        at sun.reflect.GeneratedMethodAccessor3199.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
        at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
        at com.simatech.feeder.web.common.SimatechDispatchAction.execute(SimatechDispatchAction.java:56)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
        at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)

        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
        at java.lang.Thread.run(Thread.java:534)
------
0
Comment
Question by:osigrp
  • 6
  • 2
11 Comments
 
LVL 31

Expert Comment

by:moorhouselondon
ID: 21788037
This would appear to be a bug in Exchange.

Greylisting is active at the recipient's mail server.  What is happening is that their mail server is sending your mail server a message which says "Sorry, can't accept your message right now as you may be a spammer, however, if you email me the same message again in 4 minutes, then there's a pretty good chance that you are not a spammer, and I will accept your message then."

Exchange doesn't seem to understand this response.  I have done a search on this topic, and there seem to be a lot of other people with this problem, but no apparent solution.  If anyone knows how to resolve this, it will be Sembee.
0
 

Author Comment

by:osigrp
ID: 22108997
no solution
0
 
LVL 31

Expert Comment

by:moorhouselondon
ID: 22109057
"no solution" is a strange response to collaborate with people that are trying to assist in resolving your problem.  
0
 

Author Comment

by:osigrp
ID: 22109070
no solution found
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 31

Expert Comment

by:moorhouselondon
ID: 22113639
Have you looked in your Mail Server logs to verify what I am saying.  Can you post some anonymised examples?
0
 
LVL 31

Accepted Solution

by:
moorhouselondon earned 250 total points
ID: 22114260
To elaborate on my last post, what happens if you send the message five minutes later (from the same domain, the same email address, the same IP address)?  Does it then go through?  (The mail logs will tell you that).  If it does go through, then the solution is as follows:-

(1) Get users to send two identical messages to recipients that are known to have persistent grey-listing enabled (I tend to configure mail-servers to remember senders that pass the grey-listing test for a very long period after a successful send).  In the second message, delay the sending by an arbitrary number of minutes.  See this:-

http://msmvps.com/blogs/erikr/archive/2008/04/18/delaying-outgoing-messages-in-outlook.aspx

This is, of course, a workaround, so there's a (2):-

(2) Send the mail server logs, both of them - the one showing grey-listing, and the other showing success - to Microsoft, asking if there is a bug-fix.

(3) If there is no satisfactory outcome from Microsoft and your are not prepared to accept any workaround, then perhaps it is time to look at other products on the market.  My own experiences with grey-listing is that it is very effective, if other mail server administrators achieve the same findings then this problem will get worse for administrators of systems that do not recognise the grey-list response.

0
 
LVL 31

Expert Comment

by:moorhouselondon
ID: 22114302
I tend to configure...

Sorry, didn't hammer the point home: By mail-servers remembering bona fide senders for long periods, you will only have to very infrequently need to send two messages to unblock successful receipt.  But some admins may choose to remember bona fide senders for this session only, which is counter-productive.
0
 
LVL 31

Expert Comment

by:moorhouselondon
ID: 22162697
osigrp

Please refer to vee_mod's comment
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now