I could, but those lines have been that way forever. Why a problem now? I guess the first question is whether this is a SM problem or a problem with Declude's hand-off to SM? I don't know how Declude directs SM to put the message into the Junk E-mail mailbox.
And, following up on your suggestion, will Declude accept putting quotes around Junk E-mail? Thanks, Ben ----- Original Message ----- From: John Tolmachoff To: [email protected] Sent: Wednesday, October 29, 2014 12:30 PM Subject: [MBF] Re: delivery failure for junk mailbox Try putting quotes around Junk E-mail? John T eServices For You -----Original Message----- From: "SM Admin" <[email protected]> Sent: Wednesday, October 29, 2014 11:08am To: [email protected] Subject: [MBF] delivery failure for junk mailbox Hi, I had an email that failed to be delivered to me with this error: Could not deliver message to the following recipient(s): Failed Recipient: [email protected] Reason: The recipient does not exist The way I read this is that it tried to deliver the message to a folder named “junk” in my account. Like everyone else, I have a “Junk E-mail” folder but not one just named “Junk”, so I’m assuming that that’s the reason for the error. However, I can’t find anywhere that calls for mail to be routed to Junk instead of Junk E-mail. I use SmarterMail and the is a filter setup in that to send messages weighted over 9 to the “Junk E-mail” folder. And in Declude I have these lines: WEIGHT10r MAILBOX Junk E-mail WEIGHT15r MAILBOX Junk E-mail WEIGHT20 DELETE Those are the only folder redirects that I can find. So how did this message get directly to a Junk folder instead of Junk E-mail? Anyone seen this before? Any ideas? Thanks, Ben ############################################################# This message is sent to you because you are subscribed to the mailing list <[email protected]>. To unsubscribe, E-mail to: <[email protected]> To switch to the DIGEST mode, E-mail to <[email protected]> To switch to the INDEX mode, E-mail to <[email protected]> Send administrative queries to <[email protected]>
