Chris B wrote:
> Greg Hackney wrote:
>
>> Chris B wrote:
>>
>>
>>> The following setting in my main.conf is wrong:
>>> relayhost = SMTP:[mail.asciiking.com]:2025
>>
>>
>>
>> The correct syntax is:
>>
>> relayhost = mail.asciiking.com:2025 (if you want to use MX and "A"
>> DNS records for mail.asciiking.com)
>>
>> relayhost = [mail.asciiking.com]:2025 (if you want to use only "A"
>> DNS records for mail.asciiking.com)
>
>
> One of the books I read said that using the square brackets was
> important with a "We'll explain why later in the book," for my
> information at that point. I think that was "Postfix : the definitive
> guide." If the book had been a chewed up and spit out version of "man
> postfix" or "postfix.org" that would have been an improvement. It was
> more like a "printed in Taiwan" software manual than anything else.
>
>> In modern versions of Postfix, you can leave the relayhost unset, and
>> specify
>> the default relayhost at the very end of your "transport" file, such as:
>>
>> * smtp:[mail.asciiking.com]:2025
>>
>>
>> Note: Case is significant. It must be "smtp" and not "SMTP".
>
>
> Thank you. That did it, clearing up the other list of warnings, etc.
> that I had as well.
>
> I'm finally getting through to the server, but I'm getting a "550
> Administrative prohibition (in reply to end of data command)", so it's
> pretty clear that I don't have my authentication ducks in a row. I've
> already had issues with the host about a similar issue from my mail
> client. Their docs read:
>
> Manual Settings
> Mail Server Username: cbabcock+asciiking.com
> Incoming Mail Server: mail.asciiking.com
> Outgoing Mail Server: mail.asciiking.com (server requires authentication)
> Supported Incoming Mail Protocols: POP3, POP3S (SSL/TLS), IMAP, IMAPS
> (SSL/TLS)
> Supported Outgoing Mail Protocols: SMTP, SMTPS (SSL/TLS)
>
> According to a telnet session with the port, only plain and login
> authorization are supported.
>
> When outgoing mail for my desktop client, Thunderbird, stopped one day,
> the reply to my support ticket was, "Turn off authentication and switch
> ports." Their idea of spam control is to turn off smtp for the day after
> 400 messages.
>
> Well, enough venting... this is the bigger part of my main.conf:
>
> # User configurable parameters
>
> inet_interfaces = localhost
> mynetworks_style = host
> delay_warning_time = 4h
> smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) (Mandriva
> Linux)
> unknown_local_recipient_reject_code = 450
> smtp-filter_destination_concurrency_limit = 2
> lmtp-filter_destination_concurrency_limit = 2
> smtpd_sasl_path = /etc/postfix/sasl:/usr/lib64/sasl2
> recipient_delimiter = +
> owner_request_special = no
> alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
> mydomain = asciiking.com
> myorigin = $mydomain
> relayhost = [mail.asciiking.com]:2025
> smtp_sasl_auth_enable = yes
> smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
> smtp_generic_maps = hash:/etc/postfix/generic
>
> I've checked the server, username and password combo in sasl_passwd and
> stored the map values in a hash file. The username has a "+", but that
> could be changed to @ or % if needed. Specify the port number as part of
> the server address doesn't seem to change the results. The contents
> "mail.asciiking.com:2025 user+asciiking.com:password" produce the 550
> error just as well as "mail.asciiking.com user+asciiking.com:password".
>
> Chris

You might try adding another line in sasl_passwd for serv01.siteground125.com,
which is the real name of the mail server (mail.asciiking.com).

Also, are there any clues in the Postfix log files (normally in /var/log/maillog on Linux).
--
Greg

P.S. I have that book "Postfix - The Definitive Guide". There is a one-liner on page 107 that
says "The hostname in brackets is to prevent Postfix from looking up MX records. Instead,
it looks up the A record and delivers to the IP address that the hostname resolves to."