• February 24, 2025, 01:13:58 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: send email from blackberry > maildelevery fail  (Read 7252 times)

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
send email from blackberry > maildelevery fail
« on: May 20, 2010, 01:24:46 AM »

dear all,
i new set dfl 210,
almost all working.
i set a sat/nat rule to mapping incoming smtp to new destination myemailserverip.
sending from outlook or gmail to my email are succes.
but if i try to send from blackbery its fail.

i already setting in ip rule :

 SAT  any/allnet to wan/wanip smtp (sat new destination myemailgatewayip)
 NAT any/allnet to wan/wanip

 SAT  any/allnet to any/wanip smtp (sat new destination myemailgatewayip, newport : 26 )
 NAT any/allnet to any/wanip

the eror in my mail gateway : reject RCPT from <dlink dfl_210_ip> : 450
<myemail@mydomain.com> : recepient adrres rejected : servisce is unavailable
from proto esmtp <smtp01.bis.ap.blackberry.com>

i use proxmox mail gateway

thaks... realy need your help
Logged

danilovav

  • Level 4 Member
  • ****
  • Posts: 424
  • Alexandr Danilov
Re: send email from blackberry > maildelevery fail
« Reply #1 on: May 20, 2010, 11:39:18 AM »

1) Why you have two pairs of rules? Second will never works

2) Does your email gateway has DFL as default gateway? If yes, try to change action NAT to allow
« Last Edit: May 20, 2010, 11:41:58 AM by danilovav »
Logged
BR, Alexandr Danilov

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
Re: send email from blackberry > maildelevery fail
« Reply #2 on: May 20, 2010, 09:40:32 PM »

1) Why you have two pairs of rules? Second will never works
---------------------------------------------------------
my mail gateway acept port 26, so i need the second rule...

2) Does your email gateway has DFL as default gateway? If yes, try to change action NAT to allow
-----------------------------------------------------------------------------------------------
a already try, but not sucess yet.
but now there are no low massage in server.
Logged

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
Re: send email from blackberry > maildelevery fail
« Reply #3 on: May 23, 2010, 08:50:26 PM »

if i set the rule NAT,
te log view this massage :
saverety : info
category : conn 600005
conn=close connewscrip=192.168.xx.xx<dlink ip> connewsr port=44644 connewdestip=192.168.xx.xx <mail gateway> connewdestpoert=26 origsent=409 termset 438.

any sugestion?
Logged

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
Re: send email from blackberry > maildelevery fail
« Reply #4 on: May 24, 2010, 05:46:33 PM »

2) Does your email gateway has DFL as default gateway? If yes, try to change action NAT to allow
-----------------------------------------------------------------------------------------------
a already try, but not sucess yet.
but now there are no low massage in server.
--> i means no log massage in server.
Logged

danilovav

  • Level 4 Member
  • ****
  • Posts: 424
  • Alexandr Danilov
Re: send email from blackberry > maildelevery fail
« Reply #5 on: May 25, 2010, 11:39:51 AM »

Add into Objects > Services new service smtp-26 like smtp, but with destination port 26 and change your rule with port 26 service to smtp-26
Logged
BR, Alexandr Danilov

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
Re: send email from blackberry > maildelevery fail
« Reply #6 on: May 25, 2010, 06:55:34 PM »

Add into Objects > Services new service smtp-26 like smtp, but with destination port 26 and change your rule with port 26 service to smtp-26

if i change this servis, how to port mapping sat from port 25 to 26?
Logged

dama_ps

  • Level 1 Member
  • *
  • Posts: 9
Re: send email from blackberry > maildelevery fail
« Reply #7 on: May 25, 2010, 10:39:18 PM »

thanks for all help,
i reset the firewall, than set from beginning again with same rule.
know it's working.
maybe there are some rule before reset not set properly.
 ;)
Logged