I get the following from very simple outgoing emails: an address, a
subject, and (in the body) a link.
FAILED TO SEND
Unexpected return code 564 (expected 250):
“ : We were unable to deliver your message. Please try resending
your message by adding some text.”.
Why the error, and why would
On 21 Mar 2014, at 22:10, Joshua Kehn wrote:
In case anyone else is looking for FogBugz / MailMate customization
here's what I'm using:
Thanks for the example. Long-term I would like to allow custom
specifiers to be part of bundles. This way you could have a FogBugz
bundle which could also i
On 22 Mar 2014, at 20:38, Harvey Leff wrote:
Using Command-b and Command-i surrounds the selection with double
asterisks or underscores. If there is no selection, it simply prints
the asterisks or underscores and places the cursor in the middle.
Just for the record, this is naturally somethin
On 24 Mar 2014, at 2:29, Andrew Homzy wrote:
I simply want to filter in-coming mail to appropriate mailboxes and,
Rules are an experimental 2.0 feature (they do work though). You need to
first enable 2.0 features in the General preferences pane. After that
you can add rules to any mailbox, b
On 24 Mar 2014, at 3:50, m...@assai.com.au wrote:
Yep: me too. I could do with a primer on how to automatically route
mail, and STILL have it available near the Inbox.
You cannot have IMAP mailboxes in the MAILBOXES part of the mailbox
outline if that is what you mean. As a workaround you can
On 24 Mar 2014, at 13:17, m...@assai.com.au wrote:
I get the following from very simple outgoing emails: an address, a
subject, and (in the body) a link.
FAILED TO SEND
Unexpected return code 564 (expected 250):
“ : We were unable to deliver your message. Please try resending
your message b
On 24 Mar 2014, at 14:51, Benny Kjær Nielsen wrote:
On 24 Mar 2014, at 13:17, m...@assai.com.au wrote:
I get the following from very simple outgoing emails: an address, a
subject, and (in the body) a link.
FAILED TO SEND
Unexpected return code 564 (expected 250):
“ : We were unable to deli
Hi Benny
The 564 was copy-pasted, not typed. If you google:
"We were unable to deliver your message. Please try resending your
message by adding some text"
you'll see some other people have received the same response, with the
same error code. But seems very rare.
The SMTP server is smtp.m
This looks like the kind message sent back from a listserv when it
thinks the message is almost exactly the same as a prior one.
Very strange
Google:
"Unexpected return code 564 (expected 250)"
gives nothing found at all.
The emails were being sent to individuals, not lists.
On 25 Mar 2014
On 24 Mar 2014, at 21:07, m...@assai.com.au wrote:
The 564 was copy-pasted, not typed. If you google:
"We were unable to deliver your message. Please try resending your
message by adding some text"
Yes, I found that too just a few minutes ago (thought it might be you
asking the question).
On 24 Mar 2014, at 21:19, Benny Kjær Nielsen wrote:
I do have a Yahoo test account and I could try to find out exactly
what makes the server return this error (using telnet/openssl),
A quick test with MailMate shows that:
* Sending a message with no subject and no content is not a problem.
*
I've been thinking of moving my historical yahoo accounts to google.
This will accelerate the process!
D.
On 25 Mar 2014, at 7:23, Benny Kjær Nielsen wrote:
On 24 Mar 2014, at 21:19, Benny Kjær Nielsen wrote:
I do have a Yahoo test account and I could try to find out exactly
what makes the
What I plan to do is:
Where an email is from a certain source (e.g. a list) I will first flag
it, the have it moved to a separate server-side folder (e.g. "Lists"). I
will then set near the top of my menu a Smart Mailbox which will filter
that account for flagged messages in the folder Lists.
13 matches
Mail list logo
