From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Firewall: Add Services SSMTP and submission
Date: Wed, 27 Jul 2016 14:59:05 -0500 [thread overview]
Message-ID: <57991289.8070004@dailydata.net> (raw)
In-Reply-To: <1469534780.2710.288.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I determined it used udp by grep'ing "submission" from /etc/services.
Granted, I have absolutely NO idea why submission would ever use udp
but, at least on my Debian Wheezy workstation, it shows up as 587 for
both tcp and udp. That is why I included it in the original request.
I did not look up the rfc (RFC4409,
http://www.ietf.org/rfc/rfc4409.txt) or maybe RCH6409
(https://tools.ietf.org/html/rfc6409). My bad. Going to those I see it
has absolutely no mention of udp in them. However, I did a quick
search and found it mentioned other places for tcp and udp.
I did find mention of udp at stackoverflow, saying "In theory SMTP can
be handled by either TCP, UDP, or some 3rd party protocol."
(http://stackoverflow.com/questions/16809214/is-smtp-based-on-tcp-or-udp
)
and linking to various RFC's.
However, I know of no servers currently that use anything other than
tcp for submission. I may be wrong.
I think we'd be safe to include or not include udp. It is "Legally"
viable, but I'm not aware of any actual use.
Rod
On 07/26/2016 07:06 AM, Michael Tremer wrote:
> Hi,
>
> since when is Submission using UDP (and spelled all in capitals)?
>
> I guess it is intentional that existing systems are not updated?
>
> Best, -Michael
>
> On Mon, 2016-07-25 at 14:14 +0200, Alexander Marx wrote:
>> Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org> ---
>> config/fwhosts/customservices | 3 +++ 1 file changed, 3
>> insertions(+)
>>
>> diff --git a/config/fwhosts/customservices
>> b/config/fwhosts/customservices index 9b25a72..bf3a690 100644 ---
>> a/config/fwhosts/customservices +++
>> b/config/fwhosts/customservices @@ -32,3 +32,6 @@ 34,DNS
>> (TCP),53,TCP,,0 19,FTPS data,989,TCP,BLANK,0
>> 5,SMTP,25,TCP,BLANK,0 +35,SUBMISSION (TCP),587,TCP,BLANK,0
>> +36,SUBMISSION (UDP),587,UDP,BLANK,0 +37,SSMTP,465,TCP,BLANK,0
- --
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAleZEokACgkQuVY3UpYMlTT8pQCeNkb++FXhUhVfrqp/+KI5RwGm
52UAnRkSdVrBYzZMiJkm0VOtclKwmcwy
=345V
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-07-27 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 12:14 Alexander Marx
2016-07-26 12:06 ` Michael Tremer
2016-07-26 12:36 ` Alexander Marx
2016-07-27 19:59 ` R. W. Rodolico [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57991289.8070004@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox