Hello,
unfortunately, it looks like there's no way to
distinguish between the unsupported DIGEST-MD5 and
wrond password for CRAM-MD5 -- the server's reply
is the same:
5 500 5.7.0 Unknown AUTH error -1 (Internal authentication error).
1. (digest)
On Wed, Sep 17, 2014 at 06:46:48AM -0500,
Nope, just tried it. It didn't work!
Thanks,
Russ
On Thu, Sep 18, 2014 at 04:15:22PM +0300, Alexander Gattin wrote:
Hello,
If you set correct password for the 2nd auth
method (CRAM-MD5), it works OK?
Hello Russel and mutt friends,
If ``touch .muttdebug0'' did not create the .muttdebug0 file then I guess
that you are missing the user right to create a file. The touch command is
so basic. If this does not work then that needs attention first.
On Tue, Sep 16, 2014 at 05:49:04PM -0500, Russell
On 16.09.14 17:49, Russell Urquhart wrote:
When i went to my ~ directory, and did the touch command, nothing happened.
Please do _all_ of the following: (Here, $ is the shell prompt)
$ cd# Let's just be sure we are in ~
$ touch .muttdebug0
$ ls -a | more # Did you
Hello,
On Tue, Sep 16, 2014 at 05:49:04PM -0500, Russell
Urquhart wrote:
I got the +DEBUG when i ran that command.
So you get +DEBUG in the `mutt -v|grep BUG'
output, not -DEBUG?
If you cannot find ~/.muttdebug0 (in your home
directory), then maybe installation paths for the
build have been
Hi All,
After doing the touch command, and not seeing any results, i look this morning
and there appears to be SEVERAL .muttdebug files.
I wouldn't have thought a touch could have caused that, but there they are.
I've attached a text file with what i think is the relevant text for the smtp
Hello,
On Wed, Sep 17, 2014 at 06:46:48AM -0500, Russell
Urquhart wrote:
I've attached a text file with what i think is
the relevant text for the smtp failure.
5 500 5.7.0 Unknown AUTH error -1 (Internal
authentication error).
As I can see, verison's SMTP server fails with a
500
Hi,
I set a wrong password and set the smtp authentication to cram-md5.
Here is, what i think, is the relevant part of the muttdebug file, attached.
Thanks,
Russ
On Wed, Sep 17, 2014 at 05:03:35AM -0700, Alexander Gattin wrote:
Hello,
5 500 5.7.0 Unknown AUTH error -1 (Internal
I'm not certain from your debug log, but it looks like you may
be setting your SMTP username to russurquhart1. Try using
russurquha...@verizon.net -- your full email address -- as the
username. Larger services (that support multiple virtual or real
domains) often require this.
* On 17 Sep 2014,
I've never had a problem with my SMTP username before. That and my password
have always been the same and always worked. (And still do when i specify SMTP
authentications explicitly.)
I dunno!
Thanks,
Russ
On 09/17/14, David Championd...@bikeshed.us wrote:
I'm not certain from
Hi again,
I got the lock off my mail, so i am back up and running.
I still cannot generate a muttdebug file. I have checked and recompiled my
versions of mutt. I have started mutt with the -d4 parameter, but still nothing.
Thanks again to everyone!
Russ
On Mon, Sep 15, 2014 at 11:08:43PM
Hello Russ,
Just to be clear, the following.
What does ``mutt -v | grep DEBUG'' give?
If the answer is +DEBUG, then ...
From man mutt:
``If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0. Level
can range from 1-5 and effects verbosity. A value of 2 is recommended.''
Hi Willy,
I got the +DEBUG when i ran that command.
When i went to my ~ directory, and did the touch command, nothing happened.
I too thought i might not have permission, but i have written things to this
directory.
Does mutt have to be chmod ed to do this? I execute the program, but have
Hi Tom and all,
I tried using the -d option, (i used -d4) when i started mutt, but i STILL
didn't get a .muttdebug file. I tried the locate command as was also suggested
and it returned nothing.
So i'm still trying.
Thanks everyone!
Russ
On Sun, Sep 14, 2014 at 08:52:39PM -0700, Tom Fowle
Hello Russel,
From ``man mutt'':
-- If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0.
Level can range from 1-5 and effects verbosity. A value of 2 is recommended.
Maybe mutt was not compiled with +DEBUG.
On Mon, Sep 15, 2014 at 08:05:07AM -0500, Russell Urquhart
* Russell Urquhart russurquha...@verizon.net [01-01-70 12:34]:
Hi Tom and all,
I tried using the -d option, (i used -d4) when i started mutt, but i
STILL didn't get a .muttdebug file. I tried the locate command as was
also suggested and it returned nothing.
So i'm still trying.
Thanks
On 15.09.14 15:49, Willy Offermans wrote:
From ``man mutt'':
-- If mutt was complied with +DEBUG log debugging output to
~/.muttdebug0. Level can range from 1-5 and effects verbosity. A
value of 2 is recommended.
Maybe mutt was not compiled with +DEBUG.
And Russel, to check that:
$
To all thank you. I discovered that I had not compiled with debug. I thought I
had. Now that I recompiled try and run I keep getting an error couldn't lock
and then my mail file. I saw this previously but I can't find how I did that
again? Can someone please tell me how to set that so I can get
Hello,
13.09.2014, 18:11, Russell Urquhart russurquha...@verizon.net:
Can someone tell me where these log files are/what their names are?
I can't seem to find them readily.
The last log file is in your home directory and it's named `.muttdebug0'.
It's a dotfile, so `ls' will show it only when
Hi,
On Sun, Sep 14, 2014 at 06:06:26PM +0400, Alexander Gattin wrote:
Hello,
The last log file is in your home directory and it's named `.muttdebug0'.
It's a dotfile, so `ls' will show it only when run with `-a' or `-A' option.
I have looked all over my drive but i can't find this file. I
What operating system are you using? If it is a Linux system, you would use ls
-alt .muttdebug* to list the mutt debug files from the command line. And need
to do it from the command line, a file viewer will not detect the files, unless
you possibly symlink to them with non-dot.file names.
On Sun, Sep 14, 2014 at 10:42:19AM -0700, Eliana wrote:
What operating system are you using? If it is a Linux system, you would use
ls -alt .muttdebug* to list the mutt debug files from the command line. And
need to do it from the command line, a file viewer will not detect the files,
Just to be sure you created the .debug files, don't forget the
-d#
command line option when envoking mutt to debug. Try to keep the
session as
-short as possible just enough work to show the problem. This keeps the
log
-files more manageable.
The # in the -d option defines the debug level, 0-4
I can confirm that i am still having the SMTP Authentication error with version
1.5.23 of Mutt when trying to send mail on a Verizon network.
I get around it, like I described earlier by explicitly naming all Authications
to use.
I compiled my version of Mutt 1.5.23 with the debug option in
24 matches
Mail list logo
