Hi

On Thursday 2 June 2016 at 2:14:22 PM, in
<mid:loom.20160602t151105-...@post.gmane.org>, Thomas Fernandez wrote:



> I usually send to the list from this account without
> problems, so this

> does look like a problem at GMX/1&1 to me.  

I tried posting to the list from my GMX account yesterday. It got out 
OK, I received the copy I had BCC'd to one of my other addresses, and 
it reached the TBUDL server (which sent a reply "not allowed to post 
to this mailing list" because that is not the address I have 
registered here).


 02/06/2016, 14:25:46: SEND  - sending mail message(s) - 1 message(s) in queue
 02/06/2016, 14:25:46: SEND  - Connecting to SMTP server mail.gmx.com on port 
465
 02/06/2016, 14:25:46: SEND  - Initiating TLS handshake
>02/06/2016, 14:25:47: SEND  - Certificate S/N: 
>4E83B2C4C4A0C345A22A13A30268822E, algorithm: RSA (2048 bits), issued from 
>9/15/2015 to 10/2/2017 11:59:59 PM, for 1 host(s): mail.gmx.com.
>02/06/2016, 14:25:47: SEND  - Owner: "US", "Pennsylvania", "Chesterbrook", 
>"1&1 Mail & Media Inc.", "mail.gmx.com".
>02/06/2016, 14:25:47: SEND  - Root: "generated by avast! antivirus for SSL/TLS 
>scanning", "avast! Web/Mail Shield", "avast! Web/Mail Shield Root". Valid from 
>1/1/2010 12:00:00 PM to 1/1/2040 12:00:00 PM.
 02/06/2016, 14:25:47: SEND  - TLS handshake complete
 02/06/2016, 14:25:47: SEND  - connected to SMTP server
 02/06/2016, 14:25:47: SEND  - authenticating (login)...
 02/06/2016, 14:25:47: SEND  - sending message to TBUDL@thebat.dutaint.com and 
others
<02/06/2016, 14:25:48: SEND  - message to TBUDL@thebat.dutaint.com and others 
sent (1803 bytes)
 02/06/2016, 14:25:49: SEND  - connection finished - 1 message(s) sent



-- 
Best regards

MFPA                  <mailto:2014-667rhzu3dc-lists-gro...@riseup.net>

You're only young once; you can be immature forever

Using The Bat! v7.1.18 on Windows 10.0 Build 10586  


________________________________________________
Current version is 7.1 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to