Aborting delivery for this mailbox

[Phil]

I'm trying out the free version of popgrabber.  It was working OK, but then the other day I noticed I hadn't received anythign through these accounts for a while.  The below is the output (with personal details removed).  Any ideas what the problem might be as the log doesn't seem to give much away.

2009-03-31T18:51:31: Starting POP3 Download for 2 accounts.
2009-03-31T18:51:31: Processing account xxx@xxx.net on server mail.xxx.net
2009-03-31T18:51:33: 545 message(s) on server
2009-03-31T18:51:33: Aborting delivery for this mailbox
2009-03-31T18:51:33: Processing account xxx@xxx.co.uk on server pop.xxx.co.uk
2009-03-31T18:51:34: 8 message(s) on server
2009-03-31T18:51:34: Aborting delivery for this mailbox
2009-03-31T18:51:34: Finished Processing 2 accounts.

Thanks
Phil

[Eclarsys Support]

Hello,

Please change the report level to debug and restart the PopGrabber Service to get a more detailed description of the error.

Regards,

Eclarsys Support

[jpawlicki2]

I'm having the same issue
On the free version where is the Debug mode switch?
Thanks

[Eclarsys Support]

Hello,

please click on the Settings button in the PopGrabber console, then go to the "General Settings" tab and under Report Level set the option to "Debug".

The most common reason for this problem is if the server is rejecting the message and PopGrabber is set to abort the connection (this option is under the advanced tag in PopGrabber Free). Changing the report level to debug will help you identify if the server is rejecting the message and let you see the error code it is reporting.

[seren2]

Hi all.

i got a exchange 2007 run on my whs under vmware.
All the configuration are double checked with my collegues configuration.
i also set the SendConnector -PermissionGroups "AnonymousUsers"
I still get te failure "Aborting delivery for this mailbox"

Could someone help me.

thx in advance

[Eclarsys Support]

Hi,

Please set the report level in PopGrabber to "Debug" to see what is causing the error. It can be for a different number of reasons.

For Exchange 2007, the most common reason is the message size limit, which is set to 10MB by default.

More information here: http://forum.eclarsys.com/index.php/topic,121.0.html

[seren2]

(Please set the report level in PopGrabber to "Debug" to see what is causing the error. It can be for a different number of reasons.)

I did already but there is mentioned always the same failure as described.


(For Exchange 2007, the most common reason is the message size limit, which is set to 10MB by default.)
sorry but I'm newbee
my server is named "exchange"
how should I type in exchange shell

Set-ReceiveConnector -identity "Default [SERVERNAME]" -maxmessagesize 30MB

with the [] or without.  [exchange] or what?

[seren2]

a copy of my exchange shell
and popgrabber

[Eclarsys Support]

The log file of PopGrabber does not seem to be in Debug mode. Please click on Settings, then "General Settings" and set the Report Level to "Debug".

After changing this setting restart the service and try again to see a more descriptive error.

[seren2]

is that ok now ?

i did what did you suggested

[Eclarsys Support]

Hello,

we will contact you directly to troubleshoot this, there seems to be a problem with the Exchange configuration.

[bedrock]

Is there any resolution for this problem yet?

I have installed Windows Server 2008 and Exchange 2007 SP2 in a Virtual Box VM, I have enabled Anonymous smtp authentication, and increased PopGrabber logging level to DEBUG, but I get exactly the same error messages

[Eclarsys Support]

Hi, this was not a problem on the PopGrabber side, but a configuration problem with the Exchange 2007 server.

If you have enabled anonymous connections on the Receive Connector and increased the message size limit and Exchange still rejects the messages from PopGrabber, make sure you have the email addresses and domains correctly configured in the Exchange server.

You can find more information regarding accepted domains and receive connector configuration here:

http://msexchangeteam.com/archive/2006/11/17/431555.aspx
http://technet.microsoft.com/en-us/library/bb124423(EXCHG.80).aspx

Regards,

Eclarsys Support