Niels Rasmussen wrote:
>> niels@debian:~$ dig asmtp.mail.dk
>> asmtp.mail.dk. 672 IN A 195.41.46.252
> 2007-01-07 21:24:41 1H3eZN-0001Sl-I8 <= <> R=1H3eZL-0001Si-71
> U=Debian-exim P=local S=1492 2007-01-07 21:24:41 1H3eZL-0001Si-71
> Completed 2007-01-07 21:24:43 1H3eZN-0001Sl-I8 ** niels@???
> R=smarthost T=remote_smtp_smarthost: SMTP error from remote mail server
> after MAIL FROM:<> SIZE=2558: host asmtp.mail.dk [195.41.46.252]: 553
> <> is not allowed to use this service 2007-01-07 21:24:43
> 1H3eZN-0001Sl-I8 Frozen (delivery error message) 2007-01-07 21:33:04
> 1H3ehU-0001WU-MA <= niels@??? U=niels P=local S=2822
> id=20070107203304.GA5834@??? 2007-01-07 21:33:09
> 1H3ehU-0001WU-MA ** nielsrasmus@??? R=smarthost
> T=remote_smtp_smarthost: SMTP error from remote mail server after MAIL
> FROM:<niels@???> SIZE=3923: host asmtp.mail.dk [195.41.46.252]:
> 553 <niels@???> is not allowed to use this service 2007-01-07
> 21:33:09 1H3ehZ-0001WZ-1E <= <> R=1H3ehU-0001WU-MA U=Debian-exim
> P=local S=3775 2007-01-07 21:33:09 1H3ehU-0001WU-MA Completed
> 2007-01-07 21:33:11 1H3ehZ-0001WZ-1E ** niels@??? R=smarthost
> T=remote_smtp_smarthost: SMTP error from remote mail server after MAIL
> FROM:<> SIZE=4899: host asmtp.mail.dk [195.41.46.252]: 553 <> is not
> allowed to use this service 2007-01-07 21:33:11 1H3ehZ-0001WZ-1E Frozen
> (delivery error message) niels@debian:~$ dig asmtp.mail.dk
>
This does not look like the same error message as the one you got in the
first place. But now your host seems to be able to solve asmtp.mail.dk.
The name asmtp.mail.dk seems singular to me because of the A in
Asmtp.mail.dk.
After a telnet to know you smarthost capabilities:
telnet asmtp.mail.dk 25
Trying 195.41.46.252...
Connected to asmtp.mail.dk.
Escape character is '^]'.
220 asmtp.mail.dk ESMTP server (InterMail vG.2.02.00.00
201-2161-120-101-20051020) ready Sun, 7 Jan 2007 22:38:24 +0100
ehlo mail.eriador.org
250-asmtp.mail.dk
250-HELP
250-XREMOTEQUEUE
250-AUTH=LOGIN PLAIN
250-AUTH LOGIN PLAIN
250-PIPELINING
250-DSN
250-8BITMIME
250 SIZE 10240000
It seems your smarthost supports AUTH, and more than probably requires
it to be able to send outgoing mail.
Now, maybe your smarthost supports SMTP after POP AUTH or something like
that. This may explain why sylpheed works while mutt does not.
I think you should look at providing authentication for outgoing SMTP
transactions in your client. Since mutt just relies on the MTA of the
computer running the MUA and you run exim on this computer, you should
have a look in how to configure exim to provide SMTP authentication as a
client like described here:
http://www.exim.org/exim-html-4.63/doc/html/spec_html/ch33.html#id2662980
