Sending error: 354 Enter message, ending with "."

[dbowen1]

I've been getting this (Sending error: 354 Enter message, ending with ".") error like a lot of others and I just wanted to post a solution that worked for me.

I tried everything I could think of and the problem was with a mismatch between my "authorize by checking email" login id setting under "configuration" and my "send as email" under "list settings".

So the solution (for me anyway) was to make sure my "authorize by checking email" login id was exactly the same as my "send as email" for the list I was sending to.

This does however make it very inconvenient to have a different "send as email" for each list. Dean, any possible workaround for this?

-Dan

[DW]

Hi Dan,

It seems ListMail is erroring after a RCPT TO command.  I think this may be due to the smtp_timeout variable/feature introduced in v1.87.  Try setting a line as follows in config.php to increase the timeout.

Code: [Select]

$smtp_timeout = 20;
Regards

[dbowen1]

Dean,

I changed my "send as email" in order to try and re-create the problem. Then I added that line and sent an email. I got the same error. No emails were sent and they just stayed stuck in the queue.

Here is the full error for reference.

Code: [Select]

Sending error. Check your mail settings.

Server said:
354 Enter message, ending with "." on a line by itself
550 Administrative prohibition

and the smtp logfile...

Code: [Select]

> EHLO localhost
250-host1.driveninteractive.com Hello localhost [216.22.25.249]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
LM: SMTP Pipelining Detected
> NOOP
250 OK
> MAIL FROM: <xxxxxx@tropicalsmoothietakeout.com>
> RCPT TO: <xxxxxx@driveninteractive.com>
250 OK
250 Accepted
> DATA
354 Enter message, ending with "." on a line by itself
> SENT DATA
550 Administrative prohibition

For some reason when my "authorize by checking email" in config matches my "send as email" in list settings then everything works fine.

Any other ideas? Thanks in advance.

-Dan

[DW]

Dan,

While rare, it -is- possible for your host to restrict your messages based on the "Send From Email" needing to exist as a mailbox or forwarder.  Even more rare, the "Send From Email" must match the email account used for authorization.  Further restrictions might be in place on the "Return-path" (bounce to) address.

Have you tried without authorization?  A hostname of "localhost" with no authorization could work.

The error message "Administrative Prohibition" could also be due to other reasons such as per-connection, hourly or daily limits on email.  I recommend asking your host about the possibility of such limits.

Regards

[dbowen1]

Dean,

Thanks for the quick followup. The problem was when I tried to use a "send as email" that didn't exist. When I created the account then it worked fine.

Thanks again!

-Dan