![]() ONDR.Subject = "** FAILED DELIVERY ** " & oMessage. ONDR.HeaderValue("To") = oMessage.HeaderValue("To") ' MAKE POSTMASTER BCC! ONDR.AddRecipient "VOID", YOUR DOMAIN #" ' <= CHANGE TO MATCH YOUR SERVER! ONDR.AddRecipient "VOID", oMessage.FromAddress Set oNDR = CreateObject("hMailServer.Message")įso.CopyFile oMessage.Filename, oNDR.Filename, True ' CLONE ORIGINAL MESSAGE AS NEW! If fso.FileExists(oMessage.Filename) Then Set oMatchCollection = oLookup(strRegEx, sErrorMessage, False) ' NDR - "Non Delivery Report" - Remote server replied. ![]() Sub OnDeliveryFailed(oMessage, sRecipient, sErrorMessage)ĭim fso : Set fso = CreateObject("Scripting.FileSystemObject")ĭim oNDR, oMatch, oMatchCollection, strRegEx, strFilename If Err.number 0 Then EventLog.Write( "RC = " & Err.number & " - Function oLookup(" & strRegEx & ", " & strMatch & ", " & bGlobal & ")" ) Isn't there an option to use a bounce email address as sender? Like Then the headers wouldn't matter.Ĭode: Select all Function oLookup(strRegEx, strMatch, bGlobal) Those are stripped from the bounce e-mail message by hMailserver. While this has the subject of the original message, listmonk adds several headers to the source message which it wants to use to cross reference the bounce. ![]() Remote server replied: 550 5.5.0 Requested action not taken: mailbox unavailable (S2017062302). The following recipient(s) could not be Type: SMTP ![]() Your message did not reach some or all of the intended recipients. Note that it is not hMailServer which needs to be re-configured but the SMTP server which delivers messages to the POP3 account hMailServer is downloading from.Content-Type: text/plain charset="utf-8"įrom: Message undeliverable: Test CampaignĬontent-Transfer-Encoding: quoted-printable The only workaround to this problem is to reconfigure the SMTP server not to store multiple copies of the same message. Some SMTP servers may deliver multiple copies of the same message to the same account, if a catch-all account is used and the message is being sent to several persons on the same server. If several copies of the same message are stored in the external account, hMailServer will deliver multiple copies of these messages. hMailServer will not deliver messages to recipients not listed in the To, CC, X-RCPT-TO, X-Envelope-To or Received headers. ![]() It's also possible to put recipients of an email in the BCC header (which is not included in the email message). If hMailServer reads the recipients from the MIME headers in this case, the email will be delivered to the wrong recipient (the recipient in the header). For example, it is possible to send an email to one address but still put another email address in the MIME headers. When delivering email to recipients in MIME headers, there is a risk that email won't be delivered to the correct recipients or that some will receive duplicates. If you have selected to deliver messages to recipients in MIME headers, and no recipients have been found, hMailServer will put the email message in the account in which the external account was created.When you configure to deliver messages to recipients in MIME headers, hMailServer checks the following headers.To prevent this in future, from version 4.2 onwards, hMailServer will not download email from external accounts if the parent account or domain is disabled. However, if the message is deleted from the remote server, and the local account/domain had been disabled, the message will be lost. hMailServer 4.0 and 4.1 will download email from external accounts, even if the parent account/domain is disabled. If youre only using the hmailserver as a glorified POP connector you could have sufficed with a dummy domain to collect the external pop accounts, that way theres no collision with the domain on the Exchange server.You must have SMTP enabled in hMailServer, for the external accounts feature to work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |