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,
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, Russ
Urquhart wrote:
> 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 wro
equire this.
* On 17 Sep 2014, Russell Urquhart wrote:
> 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, 2
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 err
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
50
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
fai
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 sc
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 p
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 Ur
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 neve
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.''
Di
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
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
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 th
* Russell Urquhart [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 everyone!
>
>
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 wrote
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
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
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,
>
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.
Yo
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
Hello,
13.09.2014, 18:11, "Russell Urquhart" :
> 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 run with `-a' or `-A'
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
Hi Ralf,
> +USE_POP +USE_IMAP +USE_SMTP -USE_GSS -USE_SSL_OPENSSL +USE_SSL_GNUTLS
> +USE_SASL +HAVE_GETADDRINFO
Does your client try to establish an encrypted connection to your
SMTP-server? As I sad above I had problems with encrypted connections and
gnutls. Is your mutt self compiled?
On 29-07-07, Alexander Dahl wrote:
>
> Oh I remember I had problems with SMTP-Auth and mutt compiled against
> GnuTLS. I now have mut compiled against OpenSSL and it works.
>
> Perhaps you could show us the output of `mutt -v`?
>
Of course!
kind regards
Ralf
$>mutt -v
Mutt 1.5.16 (2007-06-
Hi Ralf,
> I've updated mutt to 1.5.16 (etch backport) to checkout the new smtp transport
> feature. (Thanks for that!)
>
> The only problem I ran into is when remote smtp smarthosts do not support
> authentication at all (in intranets for example).
Is your mutt compiled against SASL?
> I ge
On 27-07-07, [EMAIL PROTECTED] wrote:
> On Fri, Jul 27, 2007 at 08:41:07AM +0200, Ralf Schmitt wrote:
> > "SMTP Server unterstützt keine Authentifizierung"
> [...]
> > but the problem remains. Any help on this?
>
> try 'set erromsg-lang=english' ;)
SMTP server does not support authentication
BTW
On Fri, Jul 27, 2007 at 08:41:07AM +0200, Ralf Schmitt wrote:
> "SMTP Server unterstützt keine Authentifizierung"
[...]
> but the problem remains. Any help on this?
try 'set erromsg-lang=english' ;)
Hi list,
I've updated mutt to 1.5.16 (etch backport) to checkout the new smtp transport
feature. (Thanks for that!)
The only problem I ran into is when remote smtp smarthosts do not support
authentication at all (in intranets for example).
I get this german error
"SMTP Server unterstützt kei
On 2002-01-16 14:56:45 -0800, Will Yardley wrote:
>postfix doesn't attempt this by default, even if built with SASL,
>but i don't think it would be terribly difficult to get this setup
>with postfix either.
It's easy: Install a sufficiently recent version of postfix on your
computer. Add th
I'll give it a shot, but as I understand it, according to RFC 2554, any
MTA that receives an authenticated email will forward that authentication. So,
is there a way to get Mutt to send an authenticated email to my local server?
I found a page on doing this with Exim as well, but I'm won
Michael P. Soulier wrote:
>
> I know Mutt does not deliver mail, but Rogers just switched to
> requiring smtp authentication and I'd prefer to smarthost through
> them. Is anyone aware of an smtp server that does authentication?
sendmail, i'm pretty sure does (i know
Hey people.
I know Mutt does not deliver mail, but Rogers just switched to requiring
smtp authentication and I'd prefer to smarthost through them. Is anyone aware
of an smtp server that does authentication?
Thanks,
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>
34 matches
Mail list logo
