I don't really know how to troubleshoot this as I have no apparent
error, any help appreciated.
Thanks
mr
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
You should start by looking at the log, generally at
/var/log/exim4/main.log .
--
MERYL STREEP is my obstetrician!
Eduardo M KALINOWSKI
edu...@kalinowski.com.br
Matteo Riva wrote:
> On Sat, May 23, 2009 at 10:02 PM, Eduardo M KALINOWSKI
> <edu...@kalinowski.com.br> wrote:
>
>
>> You should start by looking at the log, generally at
>> /var/log/exim4/main.log .
>>
>
> Yes, that's the first thing I did, and there is nothing relevant there,
> just the local message entering the queue, the message leaving it for
> the relay host and a "completed" message.
>
That means the message was delivered and accepted by your relay host.
Exim's work is done. As to why it was not received, you'd have to ask
the persons responsible for the relay host.
--
Some settling may occur.
> You should start by looking at the log, generally at
> /var/log/exim4/main.log .
Yes, that's the first thing I did, and there is nothing relevant there,
just the local message entering the queue, the message leaving it for
the relay host and a "completed" message.
> Please reply to the list (and only the list).
Yes, sorry for the mistake, I figured that too late.
> That means the message was delivered and accepted by your relay host.
> Exim's work is done. As to why it was not received, you'd have to ask
> the persons responsible for the relay host.
Well, that is weird then since I tested the same SMTP server with
Icedove and the message was properly delivered, so I thought it could be
something with exim's configuration that I missed.
Sounds like the relayhost is accepting the message but then not delivering
it. Normally that would violate SMTP protocols, but it is possible that it
tries to send a MDN somewhere that delivery fails for that and MDNs are
never sent regarding other MDNs. Also, it may be violating SMTP protocols
in a misguided attempt to reduce spam.
Probably there is some difference between your IceDove setup (that you
mention in a later message) and your exim4 setup. Perhaps IceDove is always
doing SMTP-auth, and exim4 only tries SMTP-auth if it believes it is
required and the SMTP server you are connecting to does not make this clear.
But, that's very much a guess -- turning up logging, or manually tracing the
SMTP session to get more information is probably the next step.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
b...@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
One difference that might matter is that 'mail' will use
username@hostname as Envelope-From. I don't know exim, but postfix will
not rewrite this unless specifically told to (which is needed for all my
relayhosts).
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
> On Sat,23.May.09, 22:32:20, Boyd Stephen Smith Jr. wrote:
>
> > Probably there is some difference between your IceDove setup (that you
> > mention in a later message) and your exim4 setup. Perhaps IceDove is always
> > doing SMTP-auth, and exim4 only tries SMTP-auth if it believes it is
> > required and the SMTP server you are connecting to does not make this clear.
> > But, that's very much a guess -- turning up logging, or manually tracing the
> > SMTP session to get more information is probably the next step.
>
> One difference that might matter is that 'mail' will use
> username@hostname as Envelope-From. I don't know exim, but postfix will
> not rewrite this unless specifically told to (which is needed for all my
> relayhosts).
Good point. On the other hand, while I'm no mail expert, IIRC, the
relay hosts that I've used will throw a 5xx SMTP error when they don't
like the envelope-from.
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator