Claude Sutton | 19 Sep 2010 16:13
Picon

Fwd: SMTP Authorization



---------- Forwarded message ----------
From: Claude Sutton <cssutton45 <at> gmail.com>
Date: Tue, Sep 14, 2010 at 8:00 AM
Subject: SMTP Authorization
To: msmtp-users <at> lists.sourceforge.net


Within the past week, authorization has been refused.

I am running mutt on a ubuntu 10.4, a Cradlepoint MBR1000 router with a Hauwei EC168 air card sold to me by Alltel which is now Verizon.  Dynamic DNS.

My msmtprc is:

defaults

logfile ~/.msmtp.log

account suttonmachine
host smtp.suttonmachine.com
from claudesutton <at> suttonmachine.com
auth on
user claudesutton <at> suttonmachine.com
password xxxxxxxx

account default : suttonmachine


This has worked perfectly for years until last week.

suttonmachine.com is my domain name at icondesign.com

Typical error message in an attempt to send to my ISP:

msmtp: recipient address matt <at> icomdesign.com not accepted by the server
msmtp: server message: 554 Service unavailable; Client host [98.104.218.192] blocked using
zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=98.104.218.192
msmtp: could not send mail (account suttonmachine from /home/claude69694/.msmtprc)


msmtp --version:

claude69694 <at> claude69694-laptop:~$ msmtp --version
msmtp version 1.4.19
TLS/SSL library: GnuTLS
Authentication library: GNU SASL
Supported authentication methods:
plain cram-md5 digest-md5 gssapi external login ntlm
IDN support: enabled
NLS: enabled, LOCALEDIR is /usr/share/locale
Keyring support: none
System configuration file name: /etc/msmtprc
User configuration file name: /home/claude69694/.msmtprc

Help would be appreciated.  As you see, I am forced to gmail to work through this.

CSSJR


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
Martin Lambers | 19 Sep 2010 17:55
Picon

Re: Fwd: SMTP Authorization

Hi Claude!

This does not seem to be related to msmtp.

On 19/09/10 16:13, Claude Sutton wrote:
> msmtp: server message: 554 Service unavailable; Client host
> [98.104.218.192] blocked using
> zen.spamhaus.org <http://zen.spamhaus.org>;
> http://www.spamhaus.org/query/bl?ip=98.104.218.192

Somehow your IP address was added to a blocklist that the SMTP server
uses. You can find out more at the supplied URL:
http://www.spamhaus.org/query/bl?ip=98.104.218.192

If your IP address is dynamic, then either the problem is solved by
getting a new IP address, or the IP address is blocked precisely because
it is dynamic. In the latter case, you probably have to ask your SMTP
server admins not to block dynamic addresses.

Martin

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
Kim C. Callis | 27 Sep 2010 08:05
Picon

msmtp queueing

I just ran across an email posting dated 15 Mar 2008 from Chris
Gianniotis giving the script for msmtpq and msmtpQ. After a little
cleaning of the script (insofar as adding #. etc), I have found that
is something that I have been looking to do for a long time. I have
finally motivated myself to get away from gui based mailers and have
returned back to mutt after a long hiatus.

The script is working nearly flawlessly, but I just needed a little
clarification on the execution. Assume that I have mail that is
queued, and I finally get back on-line. Do I need to manually start
/usr/local/bin/msmtpq -r or is there some easy way to let mutt
automatically send out the message?

I am using a combination of mutt, offlineimap and of course, msmtp. I
suppose that I could create a macro under mutt, but I was just
checking to see if that was already in place, and then I could just
cron it.
--

-- 
Kim C. Callis
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
cg | 27 Sep 2010 10:50
Picon

Re: msmtp queueing

Hello Kim,

There is a new version of msmtpq/msmtpQ - quite a bit more recent than
15 Mar 2008 - I trust you're using that one. The newest version deals
with some timing issues - the inherent delay of sending out a long
mail (or one with a big attachment) and better locking of the queue.

As you're using mutt, it seems to me that creating macros to run
msmtpq is the most direct approach. No need, I think, to set up a cron
job. The latest versions of the scripts will run/flush the queue after
sending out a message, but it's easy enough to trigger a run with
these macros :

macro index,pager "\eg" \
  "<shell-escape>/usr/local/bin/msmtpq -d<enter>"\
  "display msmtp queue"
macro index,pager  "\eG" \
  "<shell-escape>/usr/local/bin/msmtpq -r<enter>"\
  "run msmtp queue"

I've bound them to <esc>g and <esc>G respectively, but, obviously, you
can use what suits ...

The new script has combined the previous two scripts and uses separate
entry points (a symlink).

Let us know how it goes.

Best wishes,

Chris

On Sun 26.Sep'10 at 23:05:43 -0700, Kim C. Callis wrote:
> I just ran across an email posting dated 15 Mar 2008 from Chris
> Gianniotis giving the script for msmtpq and msmtpQ. After a little
> cleaning of the script (insofar as adding #. etc), I have found that
> is something that I have been looking to do for a long time. I have
> finally motivated myself to get away from gui based mailers and have
> returned back to mutt after a long hiatus.
> 
> The script is working nearly flawlessly, but I just needed a little
> clarification on the execution. Assume that I have mail that is
> queued, and I finally get back on-line. Do I need to manually start
> /usr/local/bin/msmtpq -r or is there some easy way to let mutt
> automatically send out the message?
> 
> I am using a combination of mutt, offlineimap and of course, msmtp. I
> suppose that I could create a macro under mutt, but I was just
> checking to see if that was already in place, and then I could just
> cron it.

> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev

> _______________________________________________
> msmtp-users mailing list
> msmtp-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/msmtp-users

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

Gmane