Community Discussions and Support
Maximum length of the local part of an e-mail address

[quote user="GordonM"]A message was recently generated/received that had 80 characters in the local part, which is longer than the RFC seems to suggest.[/quote]

Well that's fine.  Although it says the local part should not exceed 64 characters, it also says  [quote]Every implementation MUST be able to receive objects of at least these sizes.[/quote]

It seems to me that Mercury is adhering to the standards.

<P>[quote user="GordonM"]A message was recently generated/received that had 80 characters in the local part, which is longer than the RFC seems to suggest.[/quote]</P> <P>Well that's fine.  Although it says the local part should not exceed 64 characters, it also says  [quote]<FONT face="Courier New">Every implementation MUST be able to receive objects of at least these sizes.[/quote]</FONT></P> <P>It seems to me that Mercury is adhering to the standards.</P>

Can somebody confirm whether Mercury is adhering to the SMTP standard (RFC2821) with respect to the maximum allowable length of the local part of an e-mail address.  RFC2821 allows 64 characters, but an error message that was received by Postmaster showed a local part that had been truncated to 50.  Maybe it is just the error message report and not the acceptance of a longer local part by Mercury that is the limitation.

Thank you

Gordon

<P>Can somebody confirm whether Mercury is adhering to the SMTP standard (RFC2821) with respect to the maximum allowable length of the local part of an e-mail address.  RFC2821 allows 64 characters, but an error message that was received by Postmaster showed a local part that had been truncated to 50.  Maybe it is just the error message report and not the acceptance of a longer local part by Mercury that is the limitation.</P> <P>Thank you</P> <P>Gordon</P>

Where is this message being delivered? Have you tried an alias with 64 characters?

Where is this message being delivered? Have you tried an alias with 64 characters?

Paul - This is a message, being sent within my local network.  I don't mind if the limit is only 50 characters, for the local part, but I would just like to know what the maximum is.  I am using the local part to send a small amount of information, as I don't want to use the message body for this.

Thank you

Gordon

<P>Paul - This is a message, being sent within my local network.  I don't mind if the limit is only 50 characters, for the local part, but I would just like to know what the maximum is.  I am using the local part to send a small amount of information, as I don't want to use the message body for this.</P> <P>Thank you</P> <P>Gordon</P>

I don't know what the maximum is, and I don't know why you can't test it on your installation.  Are you using the '+' format - you haven't given much information about the format or the reason for rejection.

I can use more than 50 here.

 

<P>I don't know what the maximum is, and I don't know why you can't test it on your installation.  Are you using the '+' format - you haven't given much information about the format or the reason for rejection.</P> <P>I can use more than 50 here.</P> <P mce_keep="true"> </P>

Sorry, Paul. I should have been more explicit.  I received the following message in my Postmaster account, while I was doing some testing:

The attached message has failed delivery and has been referred

to you as postmaster. The following error report or reports

were given to explain the problem:

*** Luxury hotels_AT_res.luxury.com-Luxury_Hotels_Confirmation@mysite.com

User luxuryhotels_AT_res.luxury.com-Luxury_Hotels_Confi not known at this site.

This was an arbitrary test message ... the issue is nothing to do with "Luxury" Hotels!  As you can see, the information about the user has been truncated and I wondered whether this was a result of a limitation 
in the length of the local name that Mercury can handle, or whether the error message is limited in length.
 
I am not concerned about the "not known" failure, because I've already fixed that.
 
Gordon
 

 

<P>Sorry, Paul. I should have been more explicit.  I received the following message in my Postmaster account, while I was doing some testing:</P><PRE style="FONT-FAMILY: -moz-fixed; FONT-SIZE: 13px" lang=x-western class=moz-text-plain wrap="true" graphical-quote="true"><PRE wrap="">The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem: *** <A class=moz-txt-link-abbreviated href="mailto:uryhotels_AT_res.hilton.com-Hilton_Hotels_Confirmation@gordonmarwood.com" mce_href="mailto:hiltonhotels_AT_res.hilton.com+Hilton_Hotels_Confirmation@gordonmarwood.com">Luxury hotels_AT_res.luxury.com-Luxury_Hotels_Confirmation@mysite.com</A> User luxuryhotels_AT_res.luxury.com-Luxury_Hotels_Confi not known at this site. </PRE><PRE wrap="">This was an arbitrary test message ... the issue is nothing to do with "Luxury" Hotels!  As you can see, the information about the user has been truncated and I wondered whether this was a result of a limitation </PRE><PRE wrap="">in the length of the local name that Mercury can handle, or whether the error message is limited in length.</PRE><PRE wrap=""> </PRE><PRE wrap="">I am not concerned about the "not known" failure, because I've already fixed that.</PRE><PRE wrap=""> </PRE><PRE wrap="">Gordon</PRE><PRE wrap=""> </PRE></PRE> <P mce_keep="true"> </P>

The [Mercury] section of mercury.ini contains the line

 

logwidth:      50    # Width of address fields in logfile

 

I think I adjusted this up from 30 but not sure now.

I know it affects the system log file, not sure about where else.

<p>The [Mercury] section of mercury.ini contains the line</p><p> </p><p>logwidth:      50    # Width of address fields in logfile</p><p> </p><p>I think I adjusted this up from 30 but not sure now.</p><p>I know it affects the system log file, not sure about where else. </p>

Thank you, DLN.  I had not seen that.  However, I don't know what logwidth is controlling.  Maybe it's only the system logfile.  If I look in the MercuryS log, for example, there are addresses longer that 30 characters (which is what my logwith is set to).

Gordon

 

<P>Thank you, DLN.  I had not seen that.  However, I don't know what logwidth is controlling.  Maybe it's only the system logfile.  If I look in the MercuryS log, for example, there are addresses longer that 30 characters (which is what my logwith is set to).</P> <P>Gordon</P> <P mce_keep="true"> </P>

[quote user="GordonM"]I am not concerned about the "not known" failure, because I've already fixed that.[/quote]

Presumably you've got your answer then?

<P>[quote user="GordonM"]I am not concerned about the "not known" failure, because I've already fixed that.[/quote]</P> <P>Presumably you've got your answer then?</P>

Not really.  logwidth doesn't seem to be the thing that is controlling this.  A message was recently generated/received that had 80 characters in the local part, which is longer than the RFC seems to suggest.  My logwidth is still set at the default 30.

Gordon

<P>Not really.  logwidth doesn't seem to be the thing that is controlling this.  A message was recently generated/received that had 80 characters in the local part, which is longer than the RFC seems to suggest.  My logwidth is still set at the default 30.</P> <P>Gordon</P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft