Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Quando invii email utilizzando l'API Mail, esistono alcune limitazioni per quanto riguarda le intestazioni che puoi utilizzare e i tipi di file che puoi allegare.
Intestazioni facoltative
Un'email in uscita contiene intestazioni che forniscono dettagli sul messaggio, ad esempio il mittente, il destinatario, la data e l'oggetto. Ogni intestazione ha un nome e un valore.
Puoi anche includere le seguenti intestazioni in un'email in uscita. Per motivi di sicurezza, non sono consentite altre intestazioni:
In-Reply-To
List-Id
List-Unsubscribe
Per conto di
Riferimenti
Resent-Date
Resent-From
Resent-To
Posta con allegati
Un messaggio email in uscita può avere allegati di file. Ogni allegato ha un nome file e dati del file. I dati del file possono provenire da qualsiasi origine, ad esempio un
file di dati dell'applicazione o il data store.
Estensioni di nomi file vietate
Come misura di sicurezza per proteggerti dai virus, gli allegati email non possono utilizzare le seguenti estensioni dei file e i file ZIP non possono contenere file con le seguenti estensioni:
ade
adp
pipistrello
chm
cmd
com
cpl
exe
hta
ins
isp
jse
lib
mde
msc
msp
mst
pif
scr
sct
shb
sys
vb
vbe
vbs
vxd
wsc
wsf
wsh
Allegati e tipi MIME (Multipurpose Internet Mail Extensions)
Il tipo MIME di un allegato viene determinato dall'estensione del file. Il tipo MIME identifica il tipo di contenuti inviati e può determinare il modo in cui vengono trasferiti i dati.
Di seguito è riportato un elenco dei tipi MIME e delle relative estensioni dei nomi file. Non sei limitato a queste estensioni, ma se utilizzi un'estensione sconosciuta, App Engine le assegnerà il tipo MIME application/octet-stream.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eThe Mail API allows sending emails with certain restrictions on allowed headers, including \u003ccode\u003eIn-Reply-To\u003c/code\u003e, \u003ccode\u003eList-Id\u003c/code\u003e, \u003ccode\u003eList-Unsubscribe\u003c/code\u003e, \u003ccode\u003eOn-Behalf-Of\u003c/code\u003e, \u003ccode\u003eReferences\u003c/code\u003e, \u003ccode\u003eResent-Date\u003c/code\u003e, \u003ccode\u003eResent-From\u003c/code\u003e, and \u003ccode\u003eResent-To\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eOutgoing emails can have file attachments, but certain filename extensions like \u003ccode\u003e.exe\u003c/code\u003e, \u003ccode\u003e.bat\u003c/code\u003e, and \u003ccode\u003e.vbs\u003c/code\u003e are prohibited for security reasons.\u003c/p\u003e\n"],["\u003cp\u003eThe MIME type of an attachment, which determines how the content is handled, is automatically inferred from the file extension, and if the extension is unknown, it will default to \u003ccode\u003eapplication/octet-stream\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eA wide range of MIME types and their corresponding file extensions are supported, covering various document, audio, image, and video formats.\u003c/p\u003e\n"],["\u003cp\u003eThis API is supported for first generation runtimes, and information on upgrading to second generation runtimes is provided.\u003c/p\u003e\n"]]],[],null,["# Mail with headers or attachments\n\nGo Java PHP Python\n\nWhen you send mail using the [Mail API](/appengine/docs/standard/services/mail),\nthere are some restrictions on the headers that you can use and the types of\nfiles you can attach.\n| This API is supported for first-generation runtimes and can be used when [upgrading to corresponding second-generation runtimes](/appengine/docs/standard/\n|\n| /services/access). If you are updating to the App Engine runtime, refer to the [Upgrade to second-generation runtimes]() page to learn about your migration options for legacy bundled services.\n\nOptional headers\n----------------\n\nAn outgoing email has headers that provide details about the message, such as\nthe sender, recipient, date, and subject. Each header has a name and a value.\nYou can also include the following headers in an outgoing email; for security\npurposes, other headers are not allowed:\n\n- In-Reply-To\n- List-Id\n- List-Unsubscribe\n- On-Behalf-Of\n- References\n- Resent-Date\n- Resent-From\n- Resent-To\n\nMail with attachments\n---------------------\n\nAn outgoing email message can have file attachments. Each attachment has a\nfilename and file data. The file data can come from any source, such as an\napplication data file or the datastore.\n\n### Filename extensions that are prohibited\n\nAs a security measure to protect against viruses, email attachments cannot use\nthe following filename extensions, and ZIP files cannot contain files with the\nfollowing filename extensions:\n\n- ade\n- adp\n- bat\n- chm\n- cmd\n- com\n- cpl\n- exe\n- hta\n- ins\n- isp\n- jse\n- lib\n- mde\n- msc\n- msp\n- mst\n- pif\n- scr\n- sct\n- shb\n- sys\n- vb\n- vbe\n- vbs\n- vxd\n- wsc\n- wsf\n- wsh\n\n### Attachments and Multipurpose Internet Mail Extensions (MIME) types\n\nThe MIME type of an attachment is determined from the file's extension. The MIME\ntype identifies the type of content that is being sent, and can determine how\nthat data is transferred.\n\nThe following is a list of MIME types and their corresponding filename\nextensions. You are not limited to these extensions, but if you use an unknown\nextension, App Engine will assign it the MIME type `application/octet-stream`."]]