On 02/12/2019 17:24, Ken O'Driscoll via mailop wrote:
> On Mon, 2019-12-02 at 17:08 +, Ryan Prihoda via mailop wrote:
>> defer (-53): retry time not reached for any host for 'comcast.net'
>
> That looks like an MTA (Exim?) error, and not a SMTP 4xx type message.
Correct. It means you've
On 24/10/2019 14:12, Benoit Panizzon via mailop wrote:
> And I must admit, I have no real solution if you use some out of the
> stock MTA like postfix or sendmail which work on store and forward
> basis.
Exim can operate in cutthrough mode.
--
Cheers,
Jeremy
On 24/10/2019 13:19, Stefan Bauer via mailop wrote:
> We are doing MX-spamfilter service for some customers and forward "clean"
> mails to customer mailservers.
>
> We are doing recipient-checks before accepting mails.
>
>
>
> Sometimes, customers feel clever and have another local mailfilter
On 14/10/2019 22:59, Luis E. Muñoz via mailop wrote:
> Protocol-wise, what is a sender supposed to do with a post-DATA
> rejection? Is that rejection associated to one of the RFC-5321 RCPT TOs?
> All of them? None, because it's actually a content issue? What if the
> policies for each recipient
On 12/10/2019 02:35, Aaron C. de Bruyn via mailop wrote:
> By the way...any pointers for watching packets after STARTTLS has been
> issued? Wireshark doesn't appear to support decrypting SMTP packets.
This depends on your TLS library. With either GnuTLS, or enough
application-programming and
On 11/07/2019 16:58, Ross Tajvar via mailop wrote:
> do any major mail services actually validate these records when receiving
> mail? Do any major mail clients?
DANE is relevant to sending mail, not receiving.
That doesn't answer your question, though.
--
Cheers,
Jeremy
Anyone else seeing a freshly-downloaded policy file
with an already-past expiry date?
--
Cheers,
Jeremy
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
On 13/12/2018 13:04, Benoit Panizzon wrote:
> So our best idea was to tempfail the subsequent recipients whose
> settings which contradict the ones from the first recipient.
If both MTAs support PRDR you can selectively reject after DATA.
Few do.
Otherwise, you're doing the best you can. Train
On 25/05/18 11:49, Paul Smith wrote:
> Disk encryption is great on a laptop. Not sure it is anywhere else.
It does mean you don't have to secure-destroy that sour disk you
swapped out from the raid set.
--
Jeremy
___
mailop mailing list
On 19/04/18 00:03, Erwin wrote:
> RFC 5821 seems rather elusive. Where can one not in the know find a copy?
Sorry, typo. 5321.
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
On 18/04/18 23:03, Michael Wise via mailop wrote:
> Sorry, what section of 2821?
5821 has
4.4. Trace Information
"MUST insert trace ("time stamp" or "Received")"
"The FROM clause, which MUST be supplied in an SMTP environment,
SHOULD contain both (1) the name of the source host as
On 16/04/18 06:28, Brandon Long via mailop wrote:
> I always thought of SNI has the equivalent of the Host HTTP header, so it
> should be the hostname you're connecting to.
>
> That's my reading of rfc 6066 at least, and what Gmail expects.
3. Server Name Indication
[...]
clients MAY include an
On 09/04/18 11:22, Annalivia Ford wrote:
> I've been tasked with finding out what the general consensus is on the
> support in email headers for International characters such as UTF-8
> Charcacters and including things like accented characters like é and å and
> can also include Asian and
On 16/02/18 15:50, Alexander Burch wrote:
> Essentially, Yahoo just quits the connection after EHLO.
I don't think so:
> 2018-02-16 09:45:22 starting
> 2018-02-16 09:45:22 connecting from s1.asa1.acemsd4.com (192.92.97.137) to
> mta6.am0.yahoodns.net (98.136.101.117)
> 2018-02-16 09:45:22
On 14/11/17 13:16, Vladimir Dubrovin via mailop wrote:
>
> Timeout after "." on smaller messages and in the middle of transmission
> on large-size messages usually mean TCP connection issues, most common
> reason is PMTUD blackhole router problem.
On any size message they can be due to a
On 09/09/17 23:34, John Levine wrote:
>> https://tools.ietf.org/html/draft-srose-dkim-ecc-00
>
> I would suggest reading the dcrup working group's mailing list before
> implementing anything from abandoned drafts.
How would I know it's been abandoned?
On 09/09/17 13:38, Bressier Simon wrote:
> sha512 is not yet on the current dkim specification base, is that just a
> test you are doing ?
This is forward-looking development in view of this draft:
https://tools.ietf.org/html/draft-srose-dkim-ecc-00
--
Cheers,
Jeremy
Does anyone have an MTA running with DKIM rsa-sha512 support?
I need a test target for Exim development,
and Mail::DKIM::Signer isn't there yet.
--
Thanks,
Jeremy
___
mailop mailing list
mailop@mailop.org
On 25/05/16 21:08, Keenan Tims wrote:
> I'm seeing 90+% of our connection attempts to the MXes for 'hotmail.com'
> and other Hotmail domains (mx[1-4].hotmail.com) are either timing out
> (30s) or getting connection refused since ~11:00am PDT. Anyone else
> seeing this?
Yup.
--
Jeremy
On 17/05/16 00:07, Brandon Long via mailop wrote:
> As an FYI, this seems unlikely to affect most of you as the number of
> services we see using these is pretty small:
>
> http://googleappsupdates.blogspot.com/2016/05/disabling-support-for-sslv3-and-rc4-for.html
Specifically for SMTP, what SNI
20 matches
Mail list logo
