We have an email endpoint configured pointing to an IMAP mailbox on the Exchange server. Yet when messages arrive at the mailbox, the process isn't started. Things we checked:
I have tested the mailbox on the server by logging in manually from telnet. As you can see from the trace below, there are messages present in the INBOX on the server:
* OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (server.company) ready.
a001 LOGIN username password
a001 OK LOGIN completed.
a002 SELECT INBOX
* 7 EXISTS
* 5 RECENT
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
* OK [UNSEEN 1] Is the first unseen message
* OK [UIDVALIDITY 61844] UIDVALIDITY value
a002 OK [READ-WRITE] SELECT completed.
a004 LOGOUT
* BYE Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 signing off.
a004 OK LOGOUT completed.
The endpoint configuration as exported from my browser:
Id | Name | Type | Value | Label |
---|---|---|---|---|
endpoint_name | endpoint_name | text | receiveMailExtern | Name: |
endpoint_description | endpoint_description | textarea | Description: | |
cronExpression | cronExpression | text | 0 0/1 * * * ? | Cron Expession: |
endpoint_id | endpoint_id | hidden | 202 | |
page | page | hidden | 0 | |
serviceId | serviceId | hidden | receiveMailExtern | |
majorVersion | majorVersion | hidden | 1 | |
minorVersion | minorVersion | hidden | 0 | |
repeatCount | repeatCount | text | -1 | Repeat Count: |
repeatInterval | repeatInterval | text | 10 | Repeat Interval: |
startDelay | startDelay | text | 0 | Delay when job starts: |
batchSize | batchSize | text | 2 | Batch Size: |
userName | userName | text | SuperAdmin | User Name: |
domainName | domainName | text | DefaultDom | Domain Name: |
domainPattern | domainPattern | text | * | Domain Pattern: |
filePattern | filePattern | text | * | File Pattern: |
recipientSuccessfulJob | recipientSuccessfulJob | text | Successful Job's Recipients: | |
recipientFailedJob | recipientFailedJob | text | Failed Job's Recipients: | |
inboxHost | inboxHost | text | server.domain | Inbox Host: |
inboxPort | inboxPort | text | 143 | Inbox Port: |
inboxProtocol | inboxProtocol | select | Inbox Protocol: | |
inboxTimeOut | inboxTimeOut | text | 60 | Inbox Time out: |
inboxUser | inboxUser | text | username | Inbox User: |
inboxPassword | inboxPassword | password | password | Inbox Password: |
inboxSSLEnabled | inboxSSLEnabled | checkbox | false | POP3/IMAP SSL Enabled |
smtpHost | smtpHost | text | server.domain | SMTP Host: |
smtpPort | smtpPort | text | 25 | SMTP Port: |
smtpUser | smtpUser | text | username | SMTP User: |
smtpPassword | smtpPassword | password | password | SMTP Password: |
sendFrom | sendFrom | text | Send From: | |
charSet | charSet | select | Character Set Encoding: | |
smtpSSLEnabled | smtpSSLEnabled | checkbox | false | SMTP SSL Enabled |
failedJobFolder | failedJobFolder | text | Failed Email Sent Folder: | |
asynchronous | asynchronous | checkbox | true | asynchronous |
operationName | operationName | select | Operation Name: | |
type-invoke-0 | type-invoke-0 | select | ||
constant-invoke-0 | constant-invoke-0 | text | ||
variable-invoke-0 | variable-invoke-0 | text | * | |
type-invoke-1 | type-invoke-1 | select | ||
constant-invoke-1 | constant-invoke-1 | text | ||
variable-invoke-1 | variable-invoke-1 | text | %SENDER% |
Views
Replies
Total Likes
The issue was resolved by a restart. The current theory is that due to some DNS caching the endpoint was checking the empty mailbox on the old mailserver instead of the the full mailbox on the new server.
Views
Replies
Total Likes