Chris Means wrote:
> I've not seen this problem mentioned before.
Which tells us that AUTH PLAIN isn't in wide use.
> I keep getting a SMTP Authentication Failed (535).
It appears that our AUTH PLAIN implementation is wrong. Outlook works
because it uses AUTH LOGIN, which we do have implemente
> I can't currently send an email to [EMAIL PROTECTED]
> is there any reason ??
Not without seeing an appropriate extract from your logs. As a best guess,
I would assume that the element isn't configured properly,
since that is the typical reason.
--- Noel
Late in December I got james 2.2.0a15 up and running.
I needed this pre-release version because it writes to
the unix mailspool. This makes it compatible with my
imap software while the james imap package is under
development. Apparently, it doesn't write a compliant
date in the unix mail spool.
I had this problem (or at least something similar) a while ago, I think
the answer made it on to the wiki although I can't remember exactly what
the solution turned out to be.
-J
James wrote:
Hello,
I can't currently send an email to [EMAIL PROTECTED]
is there any reason ??
because using the
OK my spoolmanager block is as below; presumably the "ToRepository"
mailet puts it back on to the spool at the root again if it goes to the
error processor? Basically what happens is the message throws a wobbly
then is processed again and throws another wobbly with a new tacked on
message ID,
> Errors should go to the error processor, not re-start the ROOT processor.
I've seen this sort of loop. My recollection is that if you have a forward
type mailet in your ERROR processor, the result go to the root, which can
cause this sort of loop if the error is hit again when trying to send th
> Any ideas why it would do what it does?
Tell us what it does!
Errors should go to the error processor, not re-start the ROOT processor.
Take great care if you're trying to mail errors anywhere... obviously.
Take care to position your mailet sensibly in the pipeline, and make sure
that it ca
Thanks however in this case I do actually want the mails to go on to the
RemoteDelivery processor irrespective of whether or not my loggin Mailet
throws a wobbly or not. Any ideas why it would do what it does?
Pete
"Jason Webb" <[EMAIL PROTECTED]>
06/01/2004 15:20
Please respond to "James Use
You might want to set the mail state to GHOST in the exception handler
in your code (if you have one)
That way the message will get no further in the processing chain (I
think)
-- Jason
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 06 January 2004 14
Hi
I have a problem where when I have a bug in a mailet, creates an error in
the spool. What appears to happen is the message will then reenter the
spool at the root with some kind of "error" tagging, which is then
processed again by the mailet which errors again and so on, eventually
causing
Hello,
I can't currently send an email to [EMAIL PROTECTED]
is there any reason ??
because using the command line (telnet on port 25 from mx2.hotmail.com),
my email arrives...
I received the following error from James :
Hi. This is the James mail server at news.utopix.ch.
I'm afraid I wasn't ab
I neglected to mention that I can get (POP3) email, just not send (SMTP) it.
> -Original Message-
> From: Chris Means [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 06, 2004 7:31 AM
> To: 'James Users List'
> Subject: Problem w/Clie Mail, SMTP AUTH & James
>
> Hi,
>
> I know I'm run
Hi,
I know I'm running an older version of James (james-2.2.0a4), but I've not
seen this problem mentioned before.
I've got a Clie PEG-UX50 connecting to my WiFi network.
I'm trying to send email from it via Clie Mail.
I have configured it correctly as far as I can tell (there really isn't much
> When it comes to B encoding the subject
> line do you really use =?iso-8859-1?B and do you have an example that
would
> show a compelling reason?
Short answer: No I don't
Slightly longer answer... I believe it would be a mistake to take a
shortcut which would effectively block a legitimate
Danny
> I'm a massive fan of Base64 because it lets you safely transfer any
payload through
> every torture known to mail, and would hate for it to become blackballed
just
> because, through lazyness, it allows spammers to obfuscate content.
I can understand B encoding on binary attachements of e
15 matches
Mail list logo