-----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@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