Re: [Dovecot] change smtp port
On 1/23/2012 8:38 AM, Amira Othman wrote:
And there is no way to receive incoming emails not on port 25 ?
You can't randomly change the port you receive mail on because external MTAs have no way to find what port you're using. They will *always* use port 25 and nothing else.
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out.
If you can't get help from the ISP, you need a remailer service -- some outside proxy that accepts the mail for you and forwards connections to some different port on your computer. I don't know of any free services that do this; dyndns and others offer this for a fee, sometimes combined with spam/virus filtering.
-- Noel Jones
On 2012-01-23 11:14 AM, Noel noeldude@gmail.com wrote:
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out.
The OP specifically said that *he* had changed the port from 25 to 587... obviously he doesn't understand how smtp works...
--
Best regards,
Charles
On Tue, 24 Jan 2012, Charles Marcus wrote:
On 2012-01-23 11:14 AM, Noel noeldude@gmail.com wrote:
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out. The OP specifically said that *he* had changed the port from 25 to 587... obviously he doesn't understand how smtp works...
Most probably he wanted to enable his users to send emails via his mail server using port 587, because some may have blocked access to port 25.
Proper solution is to open additionally port 587 and require users to authenticate in order to send mails through the server. If it is too complicated in postfix, admin can simply map port 587 to 25 - most probably that would work well.
Best regards,
Jacek Osiecki joshua@ceti.pl GG:3828944 I don't want something I need. I want something I want.
On 2012-01-24 6:51 AM, Jacek Osiecki joshua@hybrid.pl wrote:
On Tue, 24 Jan 2012, Charles Marcus wrote:
On 2012-01-23 11:14 AM, Noel noeldude@gmail.com wrote:
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out.
The OP specifically said that *he* had changed the port from 25 to 587... obviously he doesn't understand how smtp works...
Most probably he wanted to enable his users to send emails via his mail server using port 587, because some may have blocked access to port 25.
Which obviously means he has not even a basic understanding of how smtp works.
Proper solution is to open additionally port 587 and require users to authenticate in order to send mails through the server. If it is too complicated in postfix,
Which is precisely why I (and a few others) gave him those instructions...
admin can simply map port 587 to 25 - most probably that would work well.
Of course it will work... but it is most definitely *not* recommended, and not only that, will totally defeat achieving the goal of using the submission port (because *all* port 587 traffic would be routed to port 25)... I only mentioned that this could be done in answer to someone who said it couldn't...
--
Best regards,
Charles
Thanks for reply
The problem that ISP for some reason port 25 is not stable and refuse connection for several times so I tried to change port to 587 instead of 25 to keep sending emails. And I though that I can stop using port 25 as it's not always working from ISP
-----Original Message----- From: dovecot-bounces@dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Charles Marcus Sent: Tuesday, January 24, 2012 2:19 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] change smtp port
On 2012-01-24 6:51 AM, Jacek Osiecki joshua@hybrid.pl wrote:
On Tue, 24 Jan 2012, Charles Marcus wrote:
On 2012-01-23 11:14 AM, Noel noeldude@gmail.com wrote:
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out.
The OP specifically said that *he* had changed the port from 25 to 587... obviously he doesn't understand how smtp works...
Most probably he wanted to enable his users to send emails via his mail server using port 587, because some may have blocked access to port 25.
Which obviously means he has not even a basic understanding of how smtp works.
Proper solution is to open additionally port 587 and require users to authenticate in order to send mails through the server. If it is too complicated in postfix,
Which is precisely why I (and a few others) gave him those instructions...
admin can simply map port 587 to 25 - most probably that would work well.
Of course it will work... but it is most definitely *not* recommended, and not only that, will totally defeat achieving the goal of using the submission port (because *all* port 587 traffic would be routed to port 25)... I only mentioned that this could be done in answer to someone who said it couldn't...
--
Best regards,
Charles
On 1/24/2012 5:23 AM, Charles Marcus wrote:
On 2012-01-23 11:14 AM, Noel noeldude@gmail.com wrote:
If your problem is that your Internet Service Provider is blocking port 25, you can contact them. Some ISPs will unblock port 25 on request, or might even have an online form you can fill out.
The OP specifically said that *he* had changed the port from 25 to 587...
... because port 25 didn't work.
obviously he doesn't understand how smtp works...
and we can assume he's here to learn, not to get flamed.
Anyway, this is OT for dovecot. Over and out.
-- Noel Jones
On 2012-01-24 8:39 AM, Noel noeldude@gmail.com wrote:
On 1/24/2012 5:23 AM, Charles Marcus wrote:
The OP specifically said that *he* had changed the port from 25 to 587...
... because port 25 didn't work.
For *sending*...
And his complaint was that changing the port for the main smtpd process caused him to not be able to *receive* email...
obviously he doesn't understand how smtp works...
and we can assume he's here to learn, not to get flamed.
What!? Please point out how simply pointing out the obvious - that someone doesn't understand something - is the same as *flaming* them...
Please...
Anyway, this is OT for dovecot. Over and out.
Agreed on that one... nip/tuck
participants (4)
-
Amira Othman
-
Charles Marcus
-
Jacek Osiecki
-
Noel