Re: [mailop] New server email being treated as spam by Google

[Christian de Larrinaga via mailop]

Hi Paul, I've migrated a couple of mail servers over to hosts on mythic
beasts in the last few months. Both have been working fine with gmail
address delivery.

I have been using the Sympl software scripts and Mailman on v4 an
v6. I've used existing domains that have been registered and used for
email over several years and used these as hostnames as well, rather
than the default mythic beasts vs
hostnames. 

One other thing is to make sure you setup the reverse DNS - that is
available as an option using the mythic beasts hosting panel.


best 

Christian




Paul Waring via mailop writes:

> In the last week or so, I migrated my xk7.net email from one self-hosted
> server to another. Both servers were setup in a similar way and adhered
> to all the email best practice guidelines I could find (DKIM, SPF and
> DMARC all pass, the server isn't on any public blocklists, and there are
> no mailing lists on the server which might result in emails getting
> marked as spam).
>
> Since the migration, any email sent to any domain hosted by Google
> (gmail.com, G Suite customers etc.) has gone straight into the
> recipient's spam folder. This happens regardless of whether I initiate
> the conversation or am replying to an existing email, whether I'm in the
> recipient's address book or not, and how many emails we've exchanged in
> the past.
>
> Email to all the other major providers (Yahoo, Microsoft etc.) is
> delivered to the recipient's inbox, and I've also tested against
> sysadmin friends who have super-strict RFC conformity servers without
> any problems.
>
> Before I change any more settings, I was wondering if there was a time
> period during which Google treats a new server that it hasn't seen
> before as a spam source? If this is something that will go away after a
> few more days then there's not much point in me tweaking further.
>
> Thanks
>
> Paul


-- 
Christian de Larrinaga 
https://firsthand.net
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Suddenlink Contact

[Anne P. Mitchell, Esq. via mailop]

> Is there anyone with Suddenlink on this list, or does anyone have any 
> contacts with them, if so please contact me off list.  It seems that emails 
> sent to their postmaster account bounce.

Having *just* gone 'round with them on this for a client, and (after many 
emails and phone calls) getting a response, what we have learned is that you 
actually need to speak with Synchronoss - Synchronoss is their inbound border 
patrol, so to speak, and it is Synchronoss who is blocking any email access to 
Suddenlink accounts.

Unfortunately I don't have a Synchronoss contact for you - in fact if anybody 
here does, please let me know!

Anne

--
Anne P. Mitchell,  Attorney at Law
CEO, SuretyMail Email Reputation Certification
Dean of Cyberlaw & Cybersecurity, Lincoln Law School
Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law)
Legislative and Legal Consultant
Board of Directors, Denver Internet Exchange
Chair Emeritus, Asilomar Microcomputer Workshop
Former Counsel: Mail Abuse Prevention System (MAPS)
Location: Boulder, Colorado

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Phil Pennock via mailop]

On 2020-11-20 at 10:18 +, Tim Bray via mailop wrote:
> On 20/11/2020 08:01, Andrew C Aitchison via mailop wrote:
> > The developers would like to use a "standard" schema;
> > does anyone use or know of a JSON schema for mail servers logs ?
> 
> Tricky - a streaming file format is not going to be a valid JSON document?

There are three different specifications for documents where one line is
one JSON object and you stream that way.  They're all pretty much the
same thing.  Oh, one of them is now under W3C aegis:
  

> Unless you do 1 JSON document per line, then but then line breaks are in
> valid inside the json.

JSON strings for these things use the two character sequence `\n` to
handle line-breaks inside the content.


FWIW, my preference is to leave Exim's logs alone.  _IF_ there were a
standard schema, we could look at adopting it, as long as it has escape
hatches for per-MTA extensions.  But I'd rather see transformations
happen afterwards so that we never get into a situation where volunteer
maintainers are dealing with self-righteous people declaring that we're
morally wrong for going ahead and doing X without waiting for the
imprimatur of others.

-Phil
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] New server email being treated as spam by Google

[Paul Waring via mailop]

On Thu, Nov 19, 2020 at 01:58:38PM +, Stuart Henderson via mailop wrote:
> If you're sending into them over v6 I would disable that too,
> most of the common open source MTAs have a feature to prevent sending
> over v6 exactly because of gmail.

That is my final option if all else fails. I don't really want to
disable IPv6 but if it's a trade-off between v6 and Google the latter
will win.

Fortunately mail acceptance does seem to be picking up now. I think for
the next migration I'll disable v6 first and only enable it after a
couple of weeks.

-- 
Paul Waring
Freelance PHP developer
https://www.phpdeveloper.org.uk
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Suddenlink Contact

[Mike McTee via mailop]

Is there anyone with Suddenlink on this list, or does anyone have any contacts 
with them, if so please contact me off list.  It seems that emails sent to 
their postmaster account bounce.







Thanks in advance

Mike


___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[André Peters via mailop]

Hm. Where do you need to stich them together when they have unique queue IDs? 
That's pretty straight forward with almost every logging stack available and a 
hundred of different patterns plus a rock solid MTA. :) And: every single 
component is free. 

> Am 20.11.2020 um 16:45 schrieb Maarten Oelering via mailop 
> :
> 
> 
> We have built integrations with many MTA’s and SMTP services. I would rather 
> see all information available in the logs of the Exim, than a common scheme 
> provided by all MTAs.
> It would also be helpful is the logs report on “transaction” level (deferral, 
> bounce, delivery) and not on process level like Postfix where you need to 
> stitch log lines together to get the full context.
> An example of an MTA with JSON logs (in NDJSON format) is PowerMTA: 
> https://www.sparkpost.com/docs/tech-resources/pmta-50-features/
> 
> Maarten
> 
>> On 20 Nov 2020, at 09:01, Andrew C Aitchison via mailop  
>> wrote:
>> 
>> 
>> The has been a request for Exim to have the ability to save the
>> server mainlog in json format 'to make it easier to "consume" it'
>>https://bugs.exim.org/show_bug.cgi?id=2610
>> 
>> The developers would like to use a "standard" schema;
>> does anyone use or know of a JSON schema for mail servers logs ?
>> 
>> Thanks,
>> 
>> -- 
>> Andrew C. Aitchison  Kendal, UK
>>  and...@aitchison.me.uk
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://list.mailop.org/listinfo/mailop
> 
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Maarten Oelering via mailop]

We have built integrations with many MTA’s and SMTP services. I would rather 
see all information available in the logs of the Exim, than a common scheme 
provided by all MTAs.
It would also be helpful is the logs report on “transaction” level (deferral, 
bounce, delivery) and not on process level like Postfix where you need to 
stitch log lines together to get the full context.
An example of an MTA with JSON logs (in NDJSON format) is PowerMTA: 
https://www.sparkpost.com/docs/tech-resources/pmta-50-features/ 


Maarten

> On 20 Nov 2020, at 09:01, Andrew C Aitchison via mailop  
> wrote:
> 
> 
> The has been a request for Exim to have the ability to save the
> server mainlog in json format 'to make it easier to "consume" it'
>https://bugs.exim.org/show_bug.cgi?id=2610
> 
> The developers would like to use a "standard" schema;
> does anyone use or know of a JSON schema for mail servers logs ?
> 
> Thanks,
> 
> -- 
> Andrew C. Aitchison   Kendal, UK
>   and...@aitchison.me.uk
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Graeme Fowler via mailop]

On 20 Nov 2020, at 09:27, Peter N. M. Hansteen via mailop  
wrote:
> I would suggest looking at what happens in elasticsearch-land for this.

On 20 Nov 2020, at 10:31, Suresh Ramasubramanian via mailop  
wrote:
> Been around for at least 4 years now.
> https://blog.cadena-it.com/monitor-backup/exim-logstash-elasticsearch-kibana/

Crikey. It's an awful long time since I wrote the underlying links in that 
article.

Yes, I wrote the pattern matches for what became the Exim bits in logstash way 
back in 2014 and it got pulled into logstash-patterns-core in 2015.

As we moved away from ELK to Splunk some time later I haven't done any further 
enhancements.

Graeme
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Suresh Ramasubramanian via mailop]

Been around for at least 4 years now.

https://blog.cadena-it.com/monitor-backup/exim-logstash-elasticsearch-kibana/

On 20/11/20, 3:44 PM, "mailop on behalf of Peter N. M. Hansteen via mailop" 
 wrote:

On Fri, Nov 20, 2020 at 08:01:36AM +, Andrew C Aitchison via mailop 
wrote:
> 
> The has been a request for Exim to have the ability to save the
> server mainlog in json format 'to make it easier to "consume" it'
> https://bugs.exim.org/show_bug.cgi?id=2610
> 
> The developers would like to use a "standard" schema;
> does anyone use or know of a JSON schema for mail servers logs ?

I would suggest looking at what happens in elasticsearch-land for this.

The more useful approach in my opinion is to not mess with the log format
at the source -- operators there will likely have scriptery to extract 
useful
data from the existing format -- but rather parse at ingest to your 
logstash/
elastic/whatever-that-does-JSON

I would not be terribly surprised to find that somebody has already found a 
way
to ingest exim logs into elastic.

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Tim Bray via mailop]

On 20/11/2020 08:01, Andrew C Aitchison via mailop wrote:

The developers would like to use a "standard" schema;
does anyone use or know of a JSON schema for mail servers logs ?


Tricky - a streaming file format is not going to be a valid JSON document?


Unless you do 1 JSON document per line, then but then line breaks are in 
valid inside the json.


--
Tim Bray
Huddersfield, GB
t...@kooky.org
+44 7966479015

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Peter N. M. Hansteen via mailop]

On Fri, Nov 20, 2020 at 08:01:36AM +, Andrew C Aitchison via mailop wrote:
> 
> The has been a request for Exim to have the ability to save the
> server mainlog in json format 'to make it easier to "consume" it'
> https://bugs.exim.org/show_bug.cgi?id=2610
> 
> The developers would like to use a "standard" schema;
> does anyone use or know of a JSON schema for mail servers logs ?

I would suggest looking at what happens in elasticsearch-land for this.

The more useful approach in my opinion is to not mess with the log format
at the source -- operators there will likely have scriptery to extract useful
data from the existing format -- but rather parse at ingest to your logstash/
elastic/whatever-that-does-JSON

I would not be terribly surprised to find that somebody has already found a way
to ingest exim logs into elastic.

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[André Peters via mailop]

I don't think that's up to the software to provide that. That should 
happen in the logging daemon imo.


You can use syslog-ng for example and convert the output to json like 
this:



destination d_json {
   file("/var/log/messages.json" template("$(format-json --scope 
selected_macros --scope nv_pairs)\n"));

};
log {
   source(s_src); destination(d_json);
};


(see 
https://dustinoprea.com/2014/09/16/convert-syslog-events-to-a-json-stream/)


It is also possible to stream the logs from journal as json btw. => 
journalctl -u postfix -o json


André

-- Originalnachricht --
Von: "Andrew C Aitchison via mailop" 
An: mailop@mailop.org
Gesendet: 20.11.2020 09:01:36
Betreff: [mailop] JSON mail server logs ?



The has been a request for Exim to have the ability to save the
server mainlog in json format 'to make it easier to "consume" it'
https://bugs.exim.org/show_bug.cgi?id=2610

The developers would like to use a "standard" schema;
does anyone use or know of a JSON schema for mail servers logs ?

Thanks,

-- Andrew C. Aitchison  Kendal, UK
and...@aitchison.me.uk
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] JSON mail server logs ?

[Suresh Ramasubramanian via mailop]

I've seen stuff like this that converts postfix logs into json and exports them 
to elasticsearch

https://nxlog.co/documentation/nxlog-user-guide/postfix.html

On 20/11/20, 1:46 PM, "mailop on behalf of Andrew C Aitchison via mailop" 
 wrote:


The has been a request for Exim to have the ability to save the
server mainlog in json format 'to make it easier to "consume" it'
 https://bugs.exim.org/show_bug.cgi?id=2610

The developers would like to use a "standard" schema;
does anyone use or know of a JSON schema for mail servers logs ?

Thanks,

-- 
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] JSON mail server logs ?

[Andrew C Aitchison via mailop]

The has been a request for Exim to have the ability to save the
server mainlog in json format 'to make it easier to "consume" it'
https://bugs.exim.org/show_bug.cgi?id=2610

The developers would like to use a "standard" schema;
does anyone use or know of a JSON schema for mail servers logs ?

Thanks,

--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop