But when exactly was that? The Pigtail and Overcoat Theory This is another neat idea that unfortunately falls down both through lack of evidence, and given the fact that the most complex of these scribal abbreviations had long since fallen out of use before the phrase p’s and q’s first appeared in the language. Anyone reading these texts would have to be careful to interpret these symbols correctly, or else risk misreading or mistranslating-and because p and q were among the most commonly embellished letters of all, that would naturally involve minding your p’s and q’s. In the interests of keeping their texts brief and compact, an elaborate system of scribal abbreviations was employed that saw various combinations of dots, dashes, bars, hooks, tails, stars, and other flourishes and embellishments attached to letters as abbreviations of lengthier words. Latin is a tough enough language to get your head around at the best of times, but in the Medieval period, scholars and scribes were seemingly determined to make things even harder. (250 2.0.0 OK 1502179523 b127si743181wmc.127 - gsmtp)īasically, SMTP server developers usually put text in that last response that will help that server's administrator locate/track the message.Could p's and q's have something to do with scribal abbreviations? / Print Collector/GettyImagesĪ much less well-known explanation suggests that your p’s and q’s might actually have their origins way back when handwritten Latin documents were still being widely compiled and interpreted. Gmail return the following for instance, which appears to be their timestamp (handy if someone complains about a message at 10:45:23, but after scouring logs you discover the sender's time is 3 hours out), and an ID. Having this in the log is often useful for debugging because it usually contains the message ID the recipient server assigned the message (If the recipient's mail admin can't find the message you can give them the log entry / id). (Most mail servers have processes that handle accepting inbound mail, placing it in a inbound-delivery queue, and separate processes that actually deliver the message to mailboxes.) In this case that looks like the normal response from an Exchange server (IIRC), and basically says thanks, I've put the message in my queue ready to deliver. This starts with the status code (success in this case), but the rest of it is just whatever the server wanted to send. The text in brackets in the log is the entire line returned by the recipient's server when your system finished giving it the message. There's also usually a second code after this, but the rest of the line can generally be whatever the server wants to send. When an SMTP client connects to a mail server, it sends a sequence of commands, like the following example ( C = Client, S = Server) C> MAIL FROM: Įach command sent by the client gets a response from the server which starts with a status code, 2xx codes being success. From that point on your server has done its job and it's up to the recipient's server to continue delivery.Ībout this message on the end - (250 2.6.0 Queued mail for delivery) Those two fields basically confirm that your server connected to in order to deliver the email, and that server accepted the message. The important things for you are relay= and status=sent. I noticed that there is an extra info Queued mail for deliveryĪnd says that she doesn't see that email in her mailbox.Ĭould you please explain what does that ( Queued mail for delivery) mean? And did email server at received that email?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |