I should clarify, the woodpeckering didn't 'go away', but it got tons better. 
Much less of it.



From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Friday, June 05, 2009 2:42 PM
To: MS-Exchange Admin Issues
Subject: RE: Problem Receiving Lyris Email

Debatable I think. I don't have any facts or figures but from here when we used 
to 4xx/5xx them during connection we got tons of woodpeckers, they kept 
retrying. Once we went to after RCPT TO the woodpeckering went away.

Which raises the question; Does the extra time in the connection waiting for 
RCPT TO add up to more load than the woodpeckering. Don't have the answer but 
my gut tells me we are better off waiting for RCPT TO.

But do watch the 4xx's on connection, those are usually interpreted as a 
temporary failure and invite a retry.

From: Don Andrews [mailto:don.andr...@safeway.com]
Sent: Friday, June 05, 2009 1:02 PM
To: MS-Exchange Admin Issues
Subject: RE: Problem Receiving Lyris Email

I'd agree about the usefulness of Mail From: and Rcpt to: for troubleshooting 
at times but from a load perspective, refusing the connection before starting 
the SMTP conversation makes sense too.  Depending on the particular DNSBL the 
IP is on, we might give a 4xx or 5xx along with some (admittedly cryptic) DNSBL 
info.

________________________________
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Friday, June 05, 2009 9:38 AM
To: MS-Exchange Admin Issues
Subject: RE: Problem Receiving Lyris Email

The Cuda is different, if you set the option to do it differently. You can 
reject on connection if you want or set it to wait until after RCPT TO and then 
it replies with a 5xx. That also gives you sending and to email addresses. 
Sometimes useful info for troubleshooting. Waiting until after RCPT TO is 
probably the better way. More email servers will honor that as a fatal and not 
retry. If you do it during the connection cycle many will keep retrying for 48 
hours.



From: Don Andrews [mailto:don.andr...@safeway.com]
Sent: Friday, June 05, 2009 11:57 AM
To: MS-Exchange Admin Issues
Subject: RE: Problem Receiving Lyris Email

In our system the connection is rejected due to DNSBL - It never gets far 
enough to start attempting to send a message - therefore we'd never see an 
email rejection - this is just fyi as the barracuda may be different.

________________________________
From: Carol Fee [mailto:c...@massbar.org]
Sent: Friday, June 05, 2009 7:37 AM
To: MS-Exchange Admin Issues
Subject: RE: Problem Receiving Lyris Email

Thanks.  I don't think this is even a black listing issue.  If it was, I would 
see the emails being rejected by the cuda.  It shows every email that arrives 
at the gate, and it's disposition.  Since 5/28, one OOO has appeared which came 
from exchange.lyris.sunbelt-software.com.  That was a reply to my post on 
Wednesday.  The few others I've received have come, like yours, from outside 
sunbelt.  A few people sent me an address at Sunbelt which was posted to one of 
the other lists in response to folks not receiving list email back in March.  
I'll let everyone know how this works out.

CFee


________________________________
From: Micheal Espinola Jr [mailto:michealespin...@gmail.com]
Sent: Friday, June 05, 2009 10:23 AM
To: MS-Exchange Admin Issues
Cc: Carol Fee
Subject: Re: Problem Receiving Lyris Email
I sent my email to you directly, to let you know that your messages were at 
leasy reaching the lyris server.  Your issue appears to be with receiving 
messages distributed by lyris back to you.

This is very commonly a mail/spam filtering issue.  In situations where no 
changes were made on your end, its probably attributed to Sunbelt being listed 
on an DNSBL again.

--
ME2
On Fri, Jun 5, 2009 at 9:59 AM, Carol Fee 
<c...@massbar.org<mailto:c...@massbar.org>> wrote:
I stopped receiving email from this list and the NTSysAdmin list on 5/28.  
Although I have had two reports that my Barracuda is rejecting list email, I do 
not believe that is true overall.  The two emails that I am aware of were not 
sent through the lyris.sunbelt-software email system.  They came from other 
ISP's. One of these was a reply from Michael Espinola, but it came from Google, 
not lyris.  Aside from one OOO reply to my post to the NTSysAdmin list on 
Wednesday, which I received, there are no entries in my Barracuda logs for 
email from either list since 5/28.

Yesterday, I unsubscribed from the NTSysAdmin list, and then subscribed this 
morning.  I have not received the email from Sunbelt requiring me to confirm my 
subscription, and there is no trace of any email from Sunbelt in my Barracuda 
log.

I'm looking for some help from you folks in the way of a reply to this post 
which would also include cc:cfee1...@gmail.com<mailto:cc%3acfee1...@gmail.com>.

I'm also looking for some help from someone at Sunbelt ?

Thanks in advance.

Carol Fee
Network Administrator
Massachusetts Bar Association
20 West St.
Boston, MA  02111
617-338-0623
c...@massbar.org<mailto:c...@massbar.org>
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~












~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to