Home » forums » Imported debian.org Mailing Lists » Debian User

smtp to bytemark.co.uk smarthost (was: using a remote IMAP server and smarthost)

Tags:

On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> [ I have changed the subject to get the attention of other bytemark
> users who might be able to help us with this problem: Richard has an
> account on a bytemark VM and he wants to send emails via the their
> smarthost. At the moment we are trying to configure msmtp properly on
> the VM for this task; suggestions for a better tool for this job are
> welcome. The goal is to have a sendmail-equivalent command working on
> the VM so that it can be used with mutt, executed remotely via ssh or
> by using port forwarding. ]

Smart move -- thanks Florian.

> On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
>> How do I get to see the
>> envelope msmtp is trying to send?
>
> Adding "logfile ~/.msmtp.log" to .msmtprc should give you more
> information.

Here is the log that resulted:

Aug 27 15:18:11 host=smtp.bytemark.co.uk tls=off auth=off
from=richard@the-place.net recipients=richard_lyons2000@yahoo.com
errormsg='the server does not support DSN' exitcode=EX_UNAVAILABLE

> These first two requirements are very basic; essentially
> they are just saying that sender and recipient addresses cannot be
> completely bogus. (The "from" line in the config file should take care
> of MAIL_FROM and mutt should specify the recipient's email address as
> the argument when it invokes msmtp.)

Ah, do I need to add parameters to the command in .muttrc? at present
it says
set sendmail="/usr/bin/msmtp"
set sendmail_wait=0
[...]

> dig MX the-place.net

That looks okay, points to the right IP.
[...]
>
> It might be time to contact bytemark's technical support.

You are probably right. I'll give them a call.

--
richard

--

Bookmark/Search this post with:
  • Delicious
  • Digg
  • StumbleUpon
  • Propeller
  • Reddit
  • Magnoliacom
  • Newsvine
  • Furl
  • Google
  • Yahoo
  • Technorati
0
‹ Running swatch dependably gpg in KDE, passphrase window, passphrase timeout ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

smtp to bytemark.co.uk smarthost (was: using a remote IMAP serve

Submitted by Steve Kemp on Mon, 2007-08-27 16:00.

On Mon Aug 27, 2007 at 15:27:55 +0100, Richard Lyons wrote:

> > It might be time to contact bytemark's technical support.
>
> You are probably right. I'll give them a call.

Agreed. Call us, or drop us a mail (!)

This page on our website has some hints, but it looks like you're
aware of them. I'll just add the link for the benefit of other
users/google:

http://bytemark.co.uk/page/Live/support/tech/mail/smarthost

Steve
--

--

»

smtp to bytemark.co.uk smarthost (was: using a remote IMAP

Submitted by richard@the-pla... on Tue, 2007-08-28 07:00.

On Mon, August 27, 2007 21:12, Steve Kemp wrote:
> On Mon Aug 27, 2007 at 15:27:55 +0100, Richard Lyons wrote:
>
>> > It might be time to contact bytemark's technical support.
>>
>> You are probably right. I'll give them a call.
>
> Agreed. Call us, or drop us a mail (!)

I did that, and here is their very reasonable reply:
| Hi Richard, I've currently no opinion on whether our servers
| should support the DSN extension or not. Currently they
| don't, and this is upsetting your chosen MTA which seems like
| odd / picky behaviour to me. I'd suggest swapping it for
| exim4 configured in forward-only mode which will do just as
| good a job.

It does, however, put me back where I started: trying to configure
exim4...

Hey ho.

--
richard

--

»

smtp to bytemark.co.uk smarthost (was: using a remote IMAP

Submitted by richard@the-pla... on Tue, 2007-08-28 08:00.

On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
>> On Sun, August 26, 2007 22:53, Florian Kulzer wrote:
>>
[...]
>> > #-------------------------
>> > tls off
>> > host FULLY_QUALIFIED_DOMAIN_NAME_OR_IP_OF_SMARTHOST
>> > from YOUR_EMAIL_ADDRESS
>> > auth plain
>> > user YOUR_USERNAME
>> > password YOUR_PASSWORD
>> > #-------------------------
>>
>> Done that. Sending from the VM, now I get
>>
>> msmtp: the server does not support DSN
>> msmtp: could not send mail (account default from /home/richard/.msmtprc)
[...]
> Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sure
> if this is really the reason for the failure or just a warning message.

Update:

These dsn settings do not help. It seems clear that msmtp expects a
DSN compliant server. Bytemark, the ISP, suggested configuring exim4
in forward-only mode, but I am not confident of my ability to get that
right, any more than I did with my previous attempt to configure exim4.
I decided to seek an alternative. esmtp and ssmtp seemed candidates,
but neither can be installed because

- ssmtp conflicts with exim4-config
- esmtp conflicts with exim4-daemon-light.

Can anybody suggest an alternative approach?

The only alternative I can see is to simply remove exim4 and install
several smaller packages that may be easier to configure, or to try with
the courier MTA in place of exim4 -- I already have courier IMAP. I
have no idea whether either of these will make anything easier.

--
richard

--

»

smtp to bytemark.co.uk smarthost (was: using a remote IMAP serve

Submitted by Owen Heisler on Tue, 2007-08-28 12:00.

On Tue, 2007.08.28 13:41, Richard Lyons wrote:
> On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> > On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
> >> Done that. Sending from the VM, now I get
> >>
> >> msmtp: the server does not support DSN
> >> msmtp: could not send mail (account default from /home/richard/.msmtprc)
> [...]
> > Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sure
> > if this is really the reason for the failure or just a warning message.
>
> Update:
>
> These dsn settings do not help. It seems clear that msmtp expects a
> DSN compliant server. Bytemark, the ISP, suggested configuring exim4
> in forward-only mode, but I am not confident of my ability to get that
> right, any more than I did with my previous attempt to configure exim4.
> I decided to seek an alternative. esmtp and ssmtp seemed candidates,
> but neither can be installed because
>
> - ssmtp conflicts with exim4-config
> - esmtp conflicts with exim4-daemon-light.

I haven't followed this thread at all so may be way off, but I just set up
msmtp with Mutt to forward to Gmail, and had some slight difficulty with DSN.
Gmail doesn't seem to support customization of DSN settings, so when I set
"dsn_notify failure,delay" and "dsn_return headers" Gmail complained. Then I
set them both to "off" which should work for a server that doesn't support DSN.
Gmail still complained. Then I realized that I had them set in Mutt as well.
After disabling them there, Gmail accepted mail.

So make sure that the DSN headers aren't getting added to mail somewhere along
the line.

»

SOLVED: smtp to bytemark.co.uk smarthost (was: using a remote I

Submitted by richard@the-pla... on Tue, 2007-08-28 12:00.

On Tue, Aug 28, 2007 at 10:03:36AM -0500, Owen Heisler wrote:

> On Tue, 2007.08.28 13:41, Richard Lyons wrote:
> > On Mon, August 27, 2007 10:44, Florian Kulzer wrote:
> > > On Mon, Aug 27, 2007 at 08:41:36 +0100, Richard Lyons wrote:
> > >> Done that. Sending from the VM, now I get
> > >>
> > >> msmtp: the server does not support DSN
> > >> msmtp: could not send mail (account default from /home/richard/.msmtprc)
> > [...]
> > > Maybe you need "dsn_notify never" and/or "dsn_return off". I am not sure
> > > if this is really the reason for the failure or just a warning message.
> >
> > Update:
> >
> > These dsn settings do not help. It seems clear that msmtp expects a
> > DSN compliant server. Bytemark, the ISP, suggested configuring exim4
> > in forward-only mode, but I am not confident of my ability to get that
> > right, any more than I did with my previous attempt to configure exim4.
> > I decided to seek an alternative. esmtp and ssmtp seemed candidates,
> > but neither can be installed because
> >
> > - ssmtp conflicts with exim4-config
> > - esmtp conflicts with exim4-daemon-light.
>
> I haven't followed this thread at all so may be way off, but I just set up
> msmtp with Mutt to forward to Gmail, and had some slight difficulty with DSN.
> Gmail doesn't seem to support customization of DSN settings, so when I set
> "dsn_notify failure,delay" and "dsn_return headers" Gmail complained. Then I
> set them both to "off" which should work for a server that doesn't support DSN.
> Gmail still complained. Then I realized that I had them set in Mutt as well.
> After disabling them there, Gmail accepted mail.

Wow! You are so right! I have commented them out there and -- hey
presto, this reply is from mutt over the tunnel!

Assuming it gets there...

Thanks to everybody.

--
richard

--

»
Syndicate content