Forwarding not working

squiffy

Verified User
Joined
Jul 8, 2008
Messages
5
Hi,
my emails don't seem to be forwarded as per my set up.
Reading other posts, here's my log entry for a controlled test :

2008-07-08 11:24:29 1KGAN3-0003WL-8u <= [email protected] H=ik-out-1112.google.com [66.249.90.176] P=esmtp S=3137 [email protected] T="test forwarder to me" from <[email protected]> for [email protected]
2008-07-08 11:24:29 1KGAN3-0003WL-8u => testemail <[email protected]> F=<[email protected]> R=virtual_user T=virtual_localdelivery S=3261
2008-07-08 11:24:41 1KGAN3-0003WL-8u => [email protected] <[email protected]> F=<[email protected]> R=lookuphost T=remote_smtp S=3206 H=mx01.1and1.co.uk [212.227.15.134] C="250 Message 0ML4cO-1KGAN40FvS-0000q4 accepted by mxeu23.kundenserver.de"
2008-07-08 11:24:41 1KGAN3-0003WL-8u Completed

It looks like it was accepted but didn't get sent on to me.
I've tried this test with many forwarding addresses, not just the 1and1 one above.

This is my first time with this - be gentle :)

Squiffy.
 
It's only failing (silently as far as I can tell) when I try to forward to an external address. To an address hosted by me (on any of my domains to any other domain) it's all fine.

Let me try explaining again.
Inbound mail :
to: [email protected],
from: [email protected]

[email protected] is set to forward to [email protected]

Ok, mail arrives in [email protected] mailbox just fine.
Nothing gets to my telemix.co.uk
the /var/log/exim/mainlog the thing I notice is that the destination address for the forwarding has two different addresses in - the forward address and <the original recipient address>. Nothing is being reported back to me as having failed, but could this be it? I've tried many forwarding addresses, all the same.

Is there another way to do this?

Thanks,

2008-07-08 11:24:41 1KGAN3-0003WL-8u => [email protected] <[email protected]> F=<[email protected]> R=lookuphost T=remote_smtp S=3206 H=mx01.1and1.co.uk [212.227.15.134] C="250 Message 0ML4cO-1KGAN40FvS-0000q4 accepted by ...
 
I've discovered the tactic of this board - leave it long enough and they'll probably sort it out themselves :)

Problem sorted itself out. It appeared to just start working, though I must have done something.

If anyone has come across this before I'd be keen to know.

Squiffy.
 
Same problem

I am having the same problem here with my forwarders Squiffy. Did you ever find any reason it didn't work?
 
forwarders not working

Maybe someone in Admin could tell us the top 3 reasons forwarders may not be working at any given time and a protocol for what to do (besides the obvious...)?

Thanks
 
squiffy,

This forum is for volunteer self-help. If anyone knows the answer they'll likely respond. If no one does, or if the answer seems obvious, or if you don't give enough information, then it's unlikely you'll get a response.

There are many of us here who offer commercial support, and of course if it's really a DirectAdmin problem, then DirectAdmin staff can be contacted if your DirectAdmin purchase includes support.

However in this case it's fairly obvious that you recipient server IS accepting the mail, then refusing to deliver it. So to get a definitive response you'd have to ask them.

loamette,

There are so many reasons why mail you forward to another server may not be delivered, but the top ones are probably:

1) You're a spammer. You're in one or more blocklists, including perhaps proprietary blocklists, because your server has been reported by recipients as a sender of spam. While such email SHOULD be refused so the sender would get an error message, many misconfigured servers do something else with the mail, such as putting it into a spam folder (which may never get read) or just dropping it. In fact many DirectAdmin users configure their systems to drop spam silently (something we do NOT recommend).

2) You're perceived to be a spammer even though you're not. This can occur because one or more of your users has emails forwarded to another server, and upon reading it there, reports it as spam. Usually because it is spam, innocently forwarded, but the other server only knows your server sends it; it cannot rely on paths in the headers because they can be forged.

3) You do not have proper reverse DNS set up for your server.

You didn't give us any information about your domain so I'll continue with information about squiffy's domain. Squiffy's IP# is NOT listed on any of the public blocklists tracked here, but that doesn't mean it isn't on private blocklists, and of course if the IP# is not the main server IP#, it doesn't really prove anything at all.

However, squiffy's IP# does NOT have reverse DNS set for it, and that's a good reason for many recipient MTAs to refuse to deliver email.

Jeff
 
Back
Top